[AIX Solaris HP-UX Linux Windows]

Installing the product on distributed operating systems using the command line

You can install WebSphere® Application Server Version 8.5 using the Installation Manager command line.

Before you begin

Important: Before installing the product, you must read the license agreement that you can find with the product files. Signify your acceptance of the license agreement by specifying -acceptLicense in the command as described below.

Prepare the system onto which you want to install the product as described in Installing Installation Manager and preparing to install the product.

Procedure

  1. Optional: If the repository requires a username and password, create a keyring file to access this repository.

    For more information on creating a keyring file for Installation Manager, read the IBM® Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

    Tip: When creating a keyring file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL that is specified.
    Note: Starting in Installation Manager Version 1.6.2, the -keyring and -password options that have been used to access credentials in a keyring file are deprecated. When you use Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file. There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file. For more information on using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 Information Center.
  2. Log on to your system.
  3. Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager.
  4. Verify that the product repository is available.
    [Windows]
    imcl.exe listAvailablePackages -repositories source_repository
    [AIX][HP-UX][Linux][Solaris]
    ./imcl listAvailablePackages -repositories source_repository
    You should see one or more levels of the offering.
  5. Use the imcl command to install the product.
    [Windows]
    imcl.exe install com.ibm.websphere.ND.v85_offering_version,optional_feature_ID
      -repositories source_repository 
      -installationDirectory installation_directory 
      -sharedResourcesDirectory shared_directory
      -accessRights access_mode
      -preferences preference_key=value
      -properties property_key=value
      -keyring keyring_file -password password
      -acceptLicense
    [AIX][HP-UX][Linux][Solaris]
    ./imcl install com.ibm.websphere.ND.v85_offering_version,optional_feature_ID
      -repositories source_repository 
      -installationDirectory installation_directory 
      -sharedResourcesDirectory shared_directory
      -accessRights access_mode
      -preferences preference_key=value
      -properties property_key=value
      -keyring keyring_file -password password
      -acceptLicense
    Tips:
    • 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.
    • The offering_version, which optionally can be attached to the offering ID with an underscore, is a specific version of the offering to install (8.5.0.20110503_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
    • You can also specify none, recommended or all with the -installFixes argument to indicate which interim fixes you want installed with the offering.
      • 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.
    • You can add a list of features that are separated by commas:
      • core.feature indicates the full WebSphere Application Server profile
        • samples indicates the sample applications feature
        • thinclient indicates the standalone thin clients and resource adapters
        • embeddablecontainer indicates the embeddable EJB container
        • ejbdeploy indicates the EJBDeploy tool for pre-EJB 3.0 modules
      • liberty indicates the Liberty profile
      • [AIX][Linux][Solaris][Windows] com.ibm.sdk.6_32bit allows you to choose a 32-bit Software Development Kit if you are installing on a 64-bit system
      • [AIX][Linux][Solaris][Windows] com.ibm.sdk.6_64bit allows you to choose a 64-bit Software Development Kit if you are installing on a 64-bit system
      Notes:
      • The features samples, thinclient, embeddablecontainer, and ejbdeploy are subfeatures of core.feature.
      • If no features are specified, the default features (core.feature, ejbdeploy, thinclient, and embeddablecontainer) are installed. To install only the features that you want, specify the list of features explicitly.
      • You must install core.feature, liberty (Liberty profile), or both.
      • You cannot use the Installation Manager to modify, update, or rollback functions to modify this installation later and add or remove core.feature (full WebSphere Application Server profile) or liberty (Liberty profile). You can use these functions to add or remove the ejbdeploy, thinclient, embeddablecontainer, or samples subfeature of core.feature later.
      • You cannot upgrade from a trial or Express edition and add or remove core.feature (full WebSphere Application Server profile) or liberty (Liberty profile).
    • The -accessRights parameter is not required if you previously specified the mode in which to install Installation Manager.
    • 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
      to this:

      For more information on setting your Installation Manager preferences, see the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

      Tip: Even if you choose not to preserve files locally for rollback, you can still roll back to any previously installed level by accessing the appropriate product repository.
    • The program might write important post-installation instructions to standard output.

    For more information on using the imcl command to install the product, see the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

What to do next

You can create a standalone application server profile, management profile, managed (custom) profile, cell profile, or secure proxy profile using the Profile Management Tool or the manageprofiles command.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 09:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=tins_installation_dist_cl
File name: tins_installation_dist_cl.html