Before using this information, be sure to read the general information under Notices.
Your feedback is important in helping to provide the most accurate and highest quality information.
Be sure to include the document name and number, the WebSphere Application Server version you are using, and, if applicable, the specific page, table, or figure number on which you are commenting.
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
This document is about installing and starting IBM HTTP Server. The information in this book is also available online, which is the most current version.
This information unit is compiled from information center articles that are available at Web address: http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
The information center has many intertopic links that this book is not able to replicate in its subset of information. Although some effort was made to remove such links and replace them with links to external information center articles, it is possible that some links were missed.
Intertopic links to articles that are not in this information and that we did not change to point to the external information center do not function properly. Such links were overlooked during the production of this document. We apologize for any inconvenience that a broken link causes and ask you to look for the information in the information center.
Link to external articles on the Web and in the external information center work correctly.
Links to articles that are within this document work correctly.
To view an article in the information center, go to the Web address and search for the title of the document.
The online information in the information center is always the most current, and the only official documentation for IBM HTTP Server.
Install the IBM HTTP Server Version 6.1 product and its plug-in.
What's new in this release of IBM HTTP Server
See the Information center for IBM HTTP Server Version 6.1 for more information.
Steps for this task
When using the launchpad, launch the Installation wizard for IBM HTTP Server.
After launching the Installation wizard from the launchpad or from the command line, the InstallShield for MultiPlatforms (ISMP) wizard initializes and then displays the Welcome panel.
Separate installation procedures for the WebSphere Application Server product, the IBM HTTP Server product, and the Web server plug-ins let you install only what you need on a particular machine. Installation of the product code is simplified and faster than in Version 5. The installation program installs the system files (shared binary files), which you do not update until you install a service fix. Creation and configuration of application servers do not change the system files.
If the installation directory already contains an existing IBM HTTP Server installation, the wizard prompts you with an Update installation panel. To install into a different directory, click Back to return to the installation directory panel.
If you update the existing installation, verify that the server is stopped.
Note: The Installation wizard does not let you update IBM HTTP Server 1.3.x versions.
Use the panel to bypass features selection by accepting typical features. Select Custom to select features in the Features selection panel. Selecting a custom installation enables you to modify the IBM HTTP Server port configurations. The default port values are 80 for IBM HTTP Server and 8008 for the IBM HTTP administration module. If the default ports are already in use by another application on the IBM HTTP Server installation, use the Port panel to adjust the port settings.
This panel gives the option
to create a Windows service for IBM HTTP Server and the IBM HTTP
administration server. Create a Windows service for IBM HTTP Server and the IBM HTTP administration
server. Configure the services to run as
LocalSystem or as a user ID that you specify. The user ID requires the
following advanced user rights, Act as part of the operating system and Log on as a service.
After displaying installation status, the wizard displays the Completion status panel that indicates a successful installation.
See Installing Web server plug-ins for WebSphere Application Server to continue the installation.
A silent installation uses the Installation wizard to install the product in silent mode, without the graphical user interface. Instead of displaying a wizard interface, the silent installation enables the installation program to read all of your responses from a file that you provide.
Steps for this task
You can find the sample options response file in the /IHS directory on the product CD.
This section contains procedures for uninstalling the IBM HTTP Server. The uninstaller program is customized for each product installation, with specific disk locations and routines for removing installed features. The uninstaller program does not remove configuration and log files.
Steps for this task
Result
The IBM HTTP Server uninstallation is now complete. The removal is logged in the ihs_install_directory/ihsv6_uninstall.log file.
You can use the WebSphere administrative console to start and stop IBM HTTP Server. You can also use commands. See the following topics for more information:
Use the WebSphere Application Server administrative console to start and stop IBM HTTP Server.
You can stop IBM HTTP Server by clicking Stop.
This section provides information on getting started with IBM HTTP Server on Linux and UNIX platforms.
The apachectl command is used to start and stop IBM HTTP Server. The apachectl command is located in the bin subdirectory within the IBM HTTP Server installation directory. If that directory is not in your PATH, the full path should be given on the command line.
Starting IBM HTTP Server. To start IBM HTTP Server using the default httpd.conf configuration file, run the apachectl start command.
Stopping IBM HTTP Server. To stop IBM HTTP Server using the default httpd.conf configuration file, run the apachectl stop command.
Issue the commands from the default directories, based on your operating system:
To start IBM HTTP Server using an alternate configuration file, run the apachectl -k start -f path_to_configuration_file command. To stop IBM HTTP Server using an alternate configuration file, run the apachectl -k stop -f path_to_configuration_file command.
Example
apachectl/usr/IBMIHS# /usr/IBMIHS/bin/apachectl start # /usr/IBMIHS/bin/apachectl stop
The apachectl command is not in your PATH, the IBM HTTP Server installation directory is /opt/IBMIHS, and an alternate configuration file, /opt/IBMIHS/conf/nodeb.conf, is used as follows:
# /opt/IBMIHS/bin/apachectl -k start -f /opt/IBMIHS/conf/nodeb.conf # /opt/IBMIHS/bin/apachectl -k stop -f /opt/IBMIHS/conf/nodeb.conf
To confirm that IBM HTTP Server started successfully, open a browser and type in your server name in the URL box.
If the IBM HTTP Server started successfully, you can configure your server for SSL, LDAP and FRCA.
This section provides information on getting started with IBM HTTP Server on Windows operating systems.
To start IBM HTTP Server as a Windows service:
If you use the developer installation option, then the IBM HTTP Server does not install as a service. Run the apache.exe command from a command line, instead.
If IBM HTTP Server does not start:
If IBM HTTP Server started successfully, you can configure your server for SSL, LDAP and FRCA.
The following sections describe how to mount the CD-ROM on Linux and UNIX operating systems.
Before you begin
After inserting a CD-ROM into a drive, some Linux and UNIX operating systems require you to mount the drive.
Why and when to perform this task
Use these procedures to mount the product discs.
Steps for this task
Your CD-ROM file system is now mounted. To view the contents of the CD-ROM, place the disk in the drive and enter the cd /cdrom command where cdrom is the CD-ROM mount point directory.
/dev/dsk/c0t2d0 mount_point pfs-rrip ro,hard
where mount_point represents the mount point of the
CD-ROM./usr/sbin/pfs_mountd & /usr/sbin/pfsd 4 &
mkdir /cdrom
/usr/sbin/pfs_mount /cdrom
The /cdrom variable represents the mount point of the CD-ROM.
mount -t iso9660 -o ro /dev/cdrom /cdrom
The /cdrom variable represents the mount point of the CD-ROM.
mkdir -p /cdrom/unnamed_cdrom
mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom/unnamed_cdrom
The
/cdrom/unnamed_cdrom variable represents the CD-ROM
mount directory and the /dev/dsk/c0t6d0s2 represents the CD-ROM drive
device.
If you are mounting the CD-ROM drive from a remote system using NFS, the CD-ROM file system on the remote machine must be exported with root access. You must also mount that file system with root access on the local machine.
If the Volume Manager (vold) is running on your system, the CD-ROM is automatically mounted as:
/cdrom/unnamed_cdrom
The common way to install IBM HTTP Server is to run the installation program using an administrator user ID. However, it is sometimes necessary to install IBM HTTP Server using a non-administrator (non-root) user ID.
Launching the IBM HTTP Server installation program is done the same way for a non-root installation as it is for a root installation, but there are several installation steps that require root privileges that cannot be completed or must be completed separately. The installation steps are as follows:
Register the installed
program with the operating system. This cannot be done for
a non-root installation. The non-root IBM HTTP Server installation
is not listed when using operating system facilities to display
installed programs.
On Linux and UNIX platforms: GSKit/gskit.sh
On Windows operating systems: GSKit\setup.exe "IHS6.1"
If GSKit is not installed, the following configurations will not work:
SSL between client (browser) and IBM HTTP Server.
SSL between the WebSphere Application Server plug-in that is running in IBM HTTP Server and WebSphere Application Server.
SSL between IBM HTTP Server and LDAP server.
Create the Windows service
entries for IBM HTTP Server and IBM HTTP Administration Server. This
cannot be done for a non-root installation. Neither of these service
entries are created and IBM HTTP Server cannot start as a service.
Start IBM HTTP Server as follows:
<ihs_install_directory>/bin/apache.exe
Start the IBM HTTP administration server as follows:
<ihs_install_directory>/bin/apache.exe -f <ihs_install_directory>/conf/admin.conf
Stop IBM HTTP server as follows:
Press Control+C in the IBM HTTP Server window, or
End the Apache.exe processes using the Windows Task Manager
Create an entry in Start > Programs. This cannot be done
for a non-root installation. No entries are created..
Create an entry in Add/Remove programs. This cannot be done
for a non-root installation. No entry is created.
Install AFPA. This cannot be done for a non-root
installation. Do not enable AFPA for the non-administrator IBM HTTP
Server installation, even if AFPA is already installed from a
previous administrator installation. Only enable AFPA for one
instance of IBM HTTP Server.
Silent installations. To enable a non-root
installation, add the following option to the silent installation
response file:
-OPT allowNonRootSilentInstall=”true”
Uninstall a non-root installation of IBM HTTP as follows:
<ihs_install_directory>/uninstall/uninstall
<ihs_install_directory>\uninstall\uninstall.exe
References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
LINUX is a trademark of Linus Torvalds in the U.S., other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.
Other company, product and service names may be trademarks or service marks of others.