You can install IBM® HTTP Server by using the
Installation Manager imcl install command.
Before you begin
Prepare the system where you want to install the product as described in Preparing the operating system for product installation.
Install IBM Installation Manager and verify that you can access the product repositories. See
Installing Installation Manager and Configuring the product repositories in Installation
Manager.
IBM Installation
Manager Version 1.8.5 or later is required to install the product.
Important: Before installing the product, you must read the license agreement that you
can find with the product files. The relevant terms and conditions, notices, and other information
are provided in the license-agreement files in the lafiles or
product_name/lafiles subdirectory of the installation image
or repository for this product. Signify your acceptance of the license agreement by specifying
-acceptLicense in the command.
About this task
For transitioning users: IBM SDK, Java™ Technology Edition, Version 8 is the Java SDK version for WebSphere® Application Server
Version 9.0.
IBM SDK, Java Technology Edition is no longer embedded with IBM HTTP Server for WebSphere Application Server. The Java SDK is available as a separate offering that must be
installed when you use IBM Installation Manager to install IBM HTTP Server.
For information about using the imcl command, see the IBM
Installation Manager documentation.
Procedure
-
Log on to your system.
-
Choose a separate directory location for the product binaries. If you are installing from this
instance of Installation Manager for the first time, also choose a shared data location.
-
Start the command line.
-
Verify that you have the necessary permissions to install the product in your chosen
directories.
-
Change to the eclipse/tools subdirectory in the directory where you
installed Installation Manager.
-
Verify that the product repository is available.
- Optional:
If the repository requires a username and password, create a master password file and a
credential storage file to access this repository.
- Optional:
Create the master password file.
The master password file is a text file that contains a passphrase such as This text is the
master password.
This file is used to secure your authentication credentials.
If you create a master password file and use it when you create credentials, you must always
specify the master password file.
Tip: To secure this file, set permissions to restrict access to this file as appropriate
for your operating system.
-
Create a credential storage file by running the imutilsc saveCredential
command.
-
Run the imcl command to install the product offering.
- Specify an offering version.
The offering_version, which optionally can be attached to the offering ID with
an underscore, is a specific version of the offering to install
(9.0.0.x_0200 for example).
- If offering_version is not specified, the latest version of the
offering and all interim fixes for that version are installed.
- If offering_version is specified, the specified version of the offering and
no interim fixes for that version are installed.
The offering version can be found attached to the end of the offering ID with an underscore when
you run the following command against the
repository:
imcl listAvailablePackages -repositories source_repository
- Set the user_data_root.
Best practice: For initial installations, specify the
user_data_root; otherwise, the default value for the
user_data_root is /QIBM/UserData/WebSphere/AppServer/V9/.
To specify the user_data_root, run the imcl command with
the user_data_root file path specified on the
was.install.os400.profile.location property. For example: -properties
was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppServer/V9/.
- Install interim fixes.
To indicate which interim fixes you want installed with the offering, specify none, recommended or all with the -installFixes argument.
- If the offering version is not specified, the
-installFixes option defaults to all.
- If the offering version is specified, the
-installFixes option defaults to none.
- Specify access rights.
The -accessRights parameter is not required if you previously specified the
mode in which to install Installation Manager.
- Choose whether to save package versions for rolling back.
Installation Manager can save earlier versions of a package to roll back to if you experience
issues later. When Installation Manager rolls back a package to a previous version, the current
version of the files are uninstalled and the earlier versions are reinstalled.
If you choose not to save the files for rollback, you can prevent the files from being saved by
using the following preference in your command
specification:
-preference com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts=False
Tip: Even if you choose not to preserve files locally for rollback with this option, you
can still roll back to any previously installed level by accessing the appropriate product
repository.
For more information on setting your Installation Manager preferences, see the IBM
Installation Manager documentation.
Examples
![[Windows]](../images/ngwin.svg)
The following example illustrates how to install the latest version of IBM HTTP Server on the Windows operating system:
imcl install com.ibm.websphere.IHS.v90 com.ibm.java.jdk.8
-installationDirectory "C:\Program Files\IBM\WebSphere\HTTPServer"
-sharedResourcesDirectory "C:\Program Files\IBM\IMShared"
-repositories C:\IBM\REP\SUPPLEMENTS
-acceptLicense
-showProgress
-log installv9.xml
-preferences com.ibm.cic.common.core.preferences.keepFetchedFiles=false,com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts=false
What to do next
When the installation completes, the program might write important post-installation instructions
to standard output.