This article describes installing IBM HTTP Server using
the launchpad.
Before you begin
If you are installing IBM HTTP Server
V6.0.1 on HP-UX IA-64 you need the
BUNDLE11i B.11.23.0409.3 required
patch bundle for HP-UX 11i level of HP-UX or greater. This is the
September 2004 update of 11i V2 for IA-64.
Note: Installing maintenance
packages has changed from IBM HTTP Server version 2.0.47. See the
Installing maintenance packages topic.
Set
the umask value to 022. To verify that the
umask value is set to 022, run the umask command.
Before
you can successfully install IBM HTTP Server, ensure that your environment
meets the prerequisites for the application server. For more information,
see the Preparing the operating system for product installation topic.
- Prepare your operating platform for installing IBM HTTP
Server as you would for installing any of the installable components
on the product disc. Refer to the Information center topic
"Preparing the operating system for product installation" that is
specific for your WebSphere Application Server product.
- Insert the product disc and mount the disc if necessary.
See Mounting CD-ROMS on AIX, HP-UX, Linux and Solaris systems for
information about mounting the product disc.
- Start the installation with the launchpad
command:
launchpad.sh
launchpad.bat
You can also start the installation from the
IHS directory,
where
IHS is the installable component directory on the product
disc. Launch the following command from the product disc:
When
using the launchpad, launch the Installation wizard for IBM HTTP Server.
Refer to the Information center topic "Using the launchpad to start
the installation" that is specific for your WebSphere Application
Server product.
After launching the Installation wizard from
the launchpad or from the command line, the ISMP wizard initializes
and then presents the Welcome panel.
Separate
installation procedures for the WebSphere Application Server product,
the IBM HTTP Server product, and the Web server plug-ins enable you
to install only what you need on a particular machine. 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.
- Click Next to display the License agreement panel.
- Accept the license agreement and
click Next to display the installation root directory panel.
- Click Next to begin installing IBM HTTP Server.
- Specify the root directory information
and click Next to display the feature type selection panel.
The panel lets you bypass features selection by accepting
typical features. Selecting Custom lets you select features in the
Features selection panel. If the installation directory already contains
an existing IBM HTTP Server installation you will be prompted with
an update install panel. If you proceed with updating the existing
installation, ensure that the server is stopped. If you choose to
install to a different directory, select
Back and you will
return to the installation directory panel.
Note: The installer will
not update IBM HTTP Server V1.3.x versions.
- Click Custom to select features
and click Next to display 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, the Port panel should be visited.
- Select features to install and click Next to
display the Windows service authorization panel, when installing IBM
HTTP Server on a Windows platform. This panel gives the
option to create a Windows service for IBM HTTP Server and the IBM
HTTP Server administration server. You can configure the services
to run as Local System account or 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.
- On a Windows platform, if you are
planning to administer IBM HTTP Server using the WebSphere Application
Server administrative console, select Run IBM HTTP Server Administration
Server as a Windows Service with Log on as Local System account.
A user name and password is not required for this selection.
Click Next . If you will not administer IBM HTTP Server using
the WebSphere Application Server administrative console, select Run
IBM HTTP Server Administration Server as a Windows Service with Log
on as a specified user account. Specify your user ID and password
information and click Next .
- Review the confirmation panel to
verify your selections. Click Back to change any of your specifications.
Click Next to begin installing IBM HTTP Server.
After
displaying installation status, the wizard displays the completion
status panel that indicates a successful installation.
- Click Next to display the
Web server plug-ins prompt panel.
- Click Next to launch the
Plug-ins installation wizard.
If the plugin directory
does not exist at the same level as the IHS directory, the
prompt panel for selecting the plug-ins installer does not display
and the installation is finished. In that case, launch the Plug-ins
installation wizard using the launchpad.
If you are installing
Version 6.0.2 IBM HTTP Server for Sun Solaris x64 and you intend to
configure the Web server plug-in for Secure Sockets Layer, an additional
step is necessary to enable the plug-in to load the correct libraries
for SSL. Open a command prompt and issue the following
command:
ln -s /opt/ibm/gsk7_64/lib64/libgsk7ssl_64.so ihs_install_root/lib/libgsk7ssl.so
where
ihs_install_root is the directory in which
IBM HTTP Server is installed.
If this command is not run,
the plug-in will fail to use SSL even when configured and error messages
similar to the following will result in the
http_plugin.log file
at
plugin_install_root/logs/webserver_name/:
[Mon Nov 13 14:47:01 2006] 00001cda 00000001 - ERROR: lib_security: loadSecurityLibrary: Failed to load gsk library
[Mon Nov 13 14:47:01 2006] 00001cda 00000001 - ERROR: ws_transport: transportInitializeSecurity: Unable to load security library
[Mon Nov 13 14:47:01 2006] 00001cda 00000001 - ERROR: ws_server: serverAddTransport: Failed to initialize security
[Mon Nov 13 14:47:01 2006] 00001cda 00000001 - ERROR: ws_server: serverAddTransport: HTTPS Transport is skipped
You can view the Web server plug-in for Secure
Sockets Layer topic in the documentation for the WebSphere Application
Server Information center.