Installing the product offerings by using the command line

You can install any product offering by using the Installation Manager imcl install command.

1. Log on to your system.

   Make sure that you log on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.

2. 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.
3. Start the command line.

   On a CL command line, run the STRQSH command to start the Qshell command shell.

4. Verify that you have the necessary permissions to install the product in your chosen directories.
5. Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager.
6. Verify that the product repository is available.

   The listAvailablePackages command lists one or more levels of the offering.

   

   imcl.exe listAvailablePackages -repositories source_repository

   

   ./imcl listAvailablePackages -repositories source_repository

7. Optional: If the repository requires a username and password, create a master password file and a credential storage file to access this repository.
   1. 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.
   2. Create a credential storage file by running the imutilsc saveCredential command.
      

      imutilsc.exe saveCredential 
        -secureStorageFile storage_file
        -userName user_ID -userPassword user_password
        -url source_repository 

      

      ./imutilsc saveCredential 
        -secureStorageFile storage_file
        -userName user_ID -userPassword user_password
        -url source_repository 

      Tip: If the imutilsc command is unable to find the URL that is specified when you create the credential storage file, append /repository.config at the end of the repository URL location.

   For more information, see the IBM Installation Manager documentation.

8. Run the imcl command to install the product offering.

   The imcl command has the format and options shown in the following examples.

   Important: Because IBM SDK Java Technology Edition is no longer embedded with the product, you must specify both the product offering ID and the IBM Java SDK offering ID (com.ibm.java.jdk.v8). The product offerings cannot be installed without the Java SDK.

   

   imcl.exe install offering_ID_offering_version,optional_feature_ID com.ibm.java.jdk.v8
     -repositories source_repository 
     -installationDirectory installation_directory 
     -sharedResourcesDirectory shared_directory
     -accessRights access_mode
     -preferences preference_key=value
     -properties property_key=value
     -secureStorageFile storage_file -masterPasswordFile master_password_file
     -acceptLicense
   

   

   ./imcl install offering_ID_offering_version,optional_feature_ID com.ibm.java.jdk.v8
     -repositories source_repository 
     -installationDirectory installation_directory 
     -sharedResourcesDirectory shared_directory
     -accessRights access_mode
     -preferences preference_key=value
     -properties property_key=value
     -secureStorageFile storage_file -masterPasswordFile master_password_file
     -acceptLicense
   

   

   Important: All applications on IBM i use the Java SDK that is included with operating system, so IBM SDK, Java Technology Edition cannot be installed with any product offering on IBM i.

   ./imcl install offering_ID_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
     -secureStorageFile storage_file -masterPasswordFile master_password_file
     -acceptLicense
   

   1. Install offerings and optional features.

      For some offerings, you can add a comma-separated list of optional features to install. If you do not specify optional features, a default set of features is installed. To install only the features that you want, specify the list of features explicitly.

      The offering IDs, optional features for each offering, and default features are shown in the following table:

      Table 1. Offering IDs and optional features

      Offering ID	Optional feature IDs	Default features
      WebSphere Application Server Network Deployment com.ibm.websphere.ND.v90	core.feature: WebSphere Application Server This feature must be specified to specify the following optional subfeatures: samples: Sample applications thinclient: Standalone thin clients and resource adapters embeddablecontainer: Embeddable EJB container ejbdeploy: EJBDeploy tool for pre-EJB 3.0 modules Note: You cannot use Installation Manager to modify, update, or rollback functions to later add or remove core.feature. Only the subfeatures can be added or removed.	core.feature thinclient embeddablecontainer ejbdeploy
      Application Client for WebSphere Application Server com.ibm.websphere.APPCLIENT.v90	samples: Samples standalonethinclient.resourceadapter.runtime: Standalone Thin Clients Runtime standalonethinclient.resourceadapter.samples: Standalone Thin Clients Samples embeddablecontainer: Embeddable EJB Container	embeddablecontainer
      DMZ Secure Proxy Server for IBM WebSphere Application Server com.ibm.websphere.NDDMZ.v90	core.feature: DMZ Secure Proxy Server for IBM WebSphere Application Server This feature must be specified to specify the following optional subfeature: thinclient: Standalone thin clients and resource adapters	No default features
      Web Server Plug-ins com.ibm.websphere.PLG.v90	No optional features	N/A
      WebSphere Customization Toolbox com.ibm.websphere.WCT.v90	zpmt: Profile Management Tool (z/OS only) zmmt: z/OS Migration Management Tool pct: Web Server Plug-ins Configuration Tool	All optional features are installed by default

   2. 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

   3. 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/ND.

      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/ND.

   4. 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.
   5. Specify access rights.

      The -accessRights parameter is not required if you previously specified the mode in which to install Installation Manager.

   6. 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

The following example illustrates how to install the latest version of WebSphere Application Server on the Windows operating system:

imcl install com.ibm.websphere.ND.v90 com.ibm.java.jdk.8
 -installationDirectory "C:\Program Files\IBM\WebSphere\AppServer"
 -sharedResourcesDirectory "C:\Program Files\IBM\IMShared" 
 -repositories C:\IBM\REP\WSAS9ENT 
 -acceptLicense 
 -showProgress 
 -log installv9.xml
 -preferences com.ibm.cic.common.core.preferences.keepFetchedFiles=false,com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts=false

The following example illustrates how to install the latest version of WebSphere Application Serveron the IBM i operating system:

./imcl install com.ibm.websphere.ND.v90
  -repositories https://downloads.mycorp.com:8080/WAS_90_repository
  -installationDirectory /QIBM/ProdData/WebSphere/AppServer/V9/ND
  -properties was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppServer/V9/ND
  -sharedResourcesDirectory /QIBM/UserData/InstallationManager/IMShared
  -secureStorageFile $HOME/WASFiles/temp/credential.store
  -acceptLicense