Installing the Application Client on IBM i operating systems using the command line

You can install the Application Client using the Installation Manager command line.

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

   Starting in Installation Manager Version 1.6.2, the -keyring and -password options that were used to access credentials in a key ring file are deprecated. For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

   In Version 1.7, the format of the secure storage file is revised, and is no longer compatible with versions of Installation Manager before version 1.7. Update Installation Manager to version 1.7 or higher and then re-create and replace any secure storage files that you created with earlier versions.

   There is no migration path from key ring files to storage files because of the differences in the file structures. You must create a storage file to replace a key ring file. For more information about using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the IBM Installation Manager documentation.

2. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
3. On a CL command line, run the STRQSH command to start the Qshell command shell.
4. Make sure that the umask is set to 022.
   To verify the umask setting, issue the following command:

   umask

   To set the umask setting to 022, issue the following command:

   umask 022

5. Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager.
6. Use the imcl command to install the product.

   ./imcl install com.ibm.websphere.APPCLIENT.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
   

   Notes:

   • 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.
     In the following list, the optional feature IDs are enclosed in parentheses:

     • Standalone Thin Clients, Resource Adapters, and Embeddable Containers

       IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, you can use the embeddable EJB container to run enterprise beans outside the application server.

       • Standalone Thin Clients Runtime (standalonethinclient.resourceadapter.runtime)

         This option installs the runtime for standalone thin clients.

       • Embeddable EJB Container (embeddablecontainer)

         This option installs the embeddable EJB container.

         The embeddable EJB container is a Java Archive (JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition environment. You can run enterprise beans using this embeddable container outside the application server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used for unit testing enterprise beans business logic.

     Tip: If no features are specified, the required features and the optional feature selected by default (embeddablecontainer) are installed. To install only the features that you want, specify the list of features explicitly.
   • For initial installations, it is a good practice to specify the app_client_user_data_root; otherwise, the default value for the app_client_user_data_root, /QIBM/UserData/WebSphere/AppClient/V85/client, is used. Use the was.install.os400.profile.location property to specify the app_client_user_data_root. If the app_client_user_data_root is to be /QIBM/UserData/WebSphere/AppClient/V85/client, for example, specify -properties was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppClient/V85/client on the imcl installation command.
   • 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 documentation.

manageprofiles -create
  -templatePath /QIBM/ProdData/WebSphere/AppClient/V85/client/profileTemplates/client 
  -serverHostname myhost.abc.com 
  -serverPort 2809 
  -profileName client