+

Search Tips   |   Advanced Search

Install Liberty on IBM i operating systems using the command line

We can WAS Liberty Core on IBM i operating systems using the Installation Manager command line.

Prepare for the installation before using this procedure.

Important: Before installing WebSphere Application Server Liberty Core, read the license agreement found with the product files. Signify the acceptance of the license agreement by specifying -acceptLicense in the command as described in this topic.

Install Installation Manager on the system onto which to install the product.

To install v8.5.5.4 and later of the Liberty profile requires IBM Installation Manager v1.6.2 or later.

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

    When creating a credential-storage file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL specified.

    When we use Installation Manager v1.6.2 and later, we should use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. In versions of Installation Manager earlier than v1.6.2, the -keyring and -password options were used to access credentials in a keyring file. These options were deprecated in v1.6.2. There is no migration path from keyring files to storage files because of the differences in the file structures. 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. For more information on using the -keyring and -password options to store credentials in a keyring file, see the Installation Manager Version 1.5 Information Center.

  2. Choose three separate locations for the product's binaries, runtime data (agent data), and shared data locations.

  3. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.

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

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

  6. Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager.

  7. Use the imcl command to install the product. 
    ./imcl install com.ibm.websphere.liberty.v85_offering_version,optional_feature_ID
  -repositories source_repository 
  -installationDirectory installation_directory 
  -sharedResourcesDirectory shared_directory
  -preferences preference_key=value
  -properties property_key=value
  -secureStorageFile storage_file -masterPasswordFile master_password_file
  -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 offering.

    • We can install a list of features that are separated by commas.

      • Embeddable EJB container and JPA client (embeddablecontainer)

        This option installs the embeddable EJB container and JPA client.

        The embeddable EJB container is a Java Archive (JAR) file for running enterprise beans in a standalone Java Platform, Standard Edition (SE) environment. We 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.

        The JPA client can be used with the embeddable EJB container to provide Java Persistence API capability in a Java SE environment.

      • If no features are specified, the default feature (embeddablecontainer) is installed.

    • We can specify additional assets to install from the Liberty Repository.

      To install Liberty Repository assets, have access to the internet, and we must have IBM Installation Manager v1.6.2 or later.

      For a list of Liberty features, see Liberty features. We can also install the following additional features:

      Liberty Repository features that we can install using IBM Installation
      Feature Symbolic name and short name Description
      Portlet Container com.ibm.websphere.appserver.portlet-2.0

      portlet-2.0

      		This feature provides a runtime environment for portlets that comply with JSR 168 and JSR 286 and a development environment for testing portlets deployed into WebSphere Portal Server.
      Portlet Serving com.ibm.websphere.appserver.portletserving-2.0

      portletserving-2.0

      		This feature provides the portlet serving or URL addressability functionality for portlets that are compliant with JSR 168 and JSR 286. This feature enables us to invoke a portlet under a defined URL from a browser.
      Web Cache Monitor com.ibm.websphere.appserver.webCacheMonitor-1.0

      webCacheMonitor-1.0

      		This feature provides monitoring of the distributed map cache and provides simple cache statistics, cache entries, and cache policy information for Servlet cache instances.

      To install additional features, specify the -properties parameter in the command line using either short names or symbolic names. Multiple feature names are separated with double commas. The following example installs the Portlet Container and Portlet Serving features:

        -properties user.feature=portlet-2.0,,portletserving-2.0,user.accept.license=true

      Beginning with v8.5.5.4, the extprogmodels feature is no longer available. Instead, install the extendedPackage-1.0 add-on, or install the individual features needed from the Liberty Repository. See the following topics for more information:

      We can install the complete set of Extended Programming Model features by specifying user.addon:

        -properties user.addon=extendedPackage-1.0,user.accept.license=true

      If we upgrade WebSphere Application Server Liberty profile v8.5.5.3 or previous versions containing the extprogmodels install feature, Installation Manager automatically installs the extendedPackage-1.0 add-on. We must specify the user.accept.license feature:

        -properties user.accept.license=true

      To learn more about the Liberty Repository and the assets it contains, see Liberty Repository.

    • 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.5.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 running the following command against the repository:

        ./imcl listAvailablePackages -repositories source_repository

    • We can also specify none, recommended or all with the -installFixes argument to indicate which interim fixes we 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.

    • For initial installations, it is a good practice to specify the user_data_root; otherwise, the default value for the user_data_root, /QIBM/UserData/WebSphere/AppServer/V85/LibertyCore, is used. Use the was.install.os400.profile.location property to specify the user_data_root. If the user_data_root is to be /QIBM/UserData/WebSphere/AppServer/V85/Liberty, for example, specify -properties was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppServer/V85/Liberty 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 Information Center.


Example

Here is an example of using the imcl command to install Websphere Application Server Liberty Core: 

./imcl install com.ibm.websphere.liberty.v85
  -repositories https://downloads.mycorp.com:8080/WAS_85_repository
  -installationDirectory /QIBM/ProdData/WebSphere/AppServer/V85/LibertyCore
  -properties was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppServer/V85/LibertyCore
  -sharedResourcesDirectory /QIBM/UserData/InstallationManager/IMShared
  -secureStorageFile $HOME/WASFiles/temp/credential.store -masterPasswordFile $HOME/WASFiles/IM/master_password_file.txt
  -acceptLicense


Parent topic:

Install Liberty on IBM i operating systems

Tasks:

Install Liberty on IBM i operating systems using response files

Install Liberty remotely on IBM i operating systems using the iRemoteInstall command

Add and remove features from Liberty on IBM i operating systems using response files

Verify the installation

Uninstall Liberty from IBM i operating systems using the command line

Uninstall Liberty from IBM i operating systems using response files

Install Liberty interim fixes on IBM i operating systems using the command line

Install Liberty fix packs on IBM i operating systems using the command line

Install Liberty fix packs on IBM i operating systems using response files

Uninstall Liberty interim fixes from IBM i operating systems using the command line

Uninstall Liberty fix packs from IBM i operating systems using the command line

Uninstall Liberty fix packs from IBM i operating systems using response files



Terms and conditions for information centers