Install Liberty on IBM i operating systems using response files

Install Liberty on IBM i operating systems using response files

We can WAS Liberty on IBM i operating systems using Installation Manager response files.

Prepare for the installation before using this procedure.
Before installing WebSphere Application Server, ensure that the user profile has *ALLOBJ and *SECADM special authorities.
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.

To use the Installation Manager that comes with this product, perform the following actions:

Obtain the necessary files.
There are three basic options for obtaining and installing Installation Manager and the product.

Access the physical media, and use local installation
We can access the product repositories on the media.

Install Installation Manager on the system.
We can install Installation Manager using the media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.
Use Installation Manager to install the product from the product repositories on the media.

Download the files from the Passport Advantage site, and use local installation
Licensed customers with a Passport Advantage ID and password can download the necessary product repositories from the Passport Advantage site.

Download the files from the Passport Advantage site.

Install Installation Manager on the system.
We can install Installation Manager using the media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.
Use Installation Manager to install the product from the downloaded repositories.

Access the live repositories, and use web-based installation
If we have a Passport Advantage ID and password, we can install the product from the web-based repositories.

Install Installation Manager on the system.
We can install Installation Manager using the media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.
Use Installation Manager to install the product from the web-based repository located at
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85

This location does not contain a web page that we can access using a web browser. This is a remote web-based repository location that we must specify in the response file so the installation can access the files in this repository.

Whenever possible, we should use the remote web-based repositories so that we are accessing the most up-to-date installation files.

If we do not have a Passport Advantage ID and password, install the product from the product repositories on the media or local repositories.

Install Installation Manager.

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

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

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

Change to the temporary directory where you unpacked the Installation Manager files.

installc -acceptLicense -log log_file_path_and_name

For more information on installing Installation Manager, see the IBM Installation Manager Information Center.
Use only the installc command to install Installation Manager.

If you already have a version of Installation Manager installed on the system and to use it to install and maintain the product, obtain the necessary product files.
There are three basic options for installing the product.

Access the physical media, and use local installation
We can access the product repositories on the media. Use Installation Manager to install the product from the product repositories on the media.

Download the files from the Passport Advantage site, and use local installation
Licensed customers with a Passport Advantage ID and password can download the necessary product repositories from the Passport Advantage site.

Download the product repositories from the Passport Advantage site.
Use Installation Manager to install the product from the downloaded repositories.

Access the live repositories, and use web-based installation
If we have a Passport Advantage ID and password, we can use Installation Manager to install the product from the web-based repositories. Use Installation Manager to install the product from the web-based repository located at
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85

This location does not contain a web page that we can access using a web browser. This is a remote web-based repository location that we must specify in the response file so the installation can access the files in this repository.
Whenever possible, we should use the remote web-based repositories so that we are accessing the most up-to-date installation files.

If we do not have a Passport Advantage ID and password, install the product from the product repositories on the media or local repositories.

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.

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

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

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

Use a response file to install the product.
Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the product. For example:
./imcl -acceptLicense input $HOME/WASFiles/temp/install_response_file.xml -log $HOME/WASFiles/temp/install_log.xml -secureStorageFile $HOME/WASFiles/temp/credential.store -masterPasswordFile $HOME/WASFiles/master_password_file.txt

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.

/QIBM/ProdData/InstallationManager is the default installation location for Installation Manager files on IBM i systems.

The program might write important post-installation instructions to standard output.

Read the IBM Installation Manager Information Center for more information.

Example

The following is an example of a response file for installing the product with no optional features into the /QIBM/ProdData/WebSphere/AppServer/V85/LibertyCore directory using a web-based repository located at http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85.
<?xml version="1.0" encoding="UTF-8"?> <agent-input> <server> <repository location='http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85'/> </server> <profile id='WebSphere Liberty V8.5' installLocation='/QIBM/ProdData/WebSphere/AppServer/V85/LibertyCore'> <data key='was.install.os400.profile.location' value='/QIBM/UserData/WebSphere/AppServer/V85/LibertyCore'/> <data key='user.import.profile' value='false'/> </profile> <install modify='false'> <offering profile='WebSphere Liberty V8.5' features='' id='com.ibm.websphere.liberty.v85'/> </install> <preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='/QIBM/UserData/InstallationManager/IMShared'/> <preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/> <preference name='com.ibm.cic.common.core.preferences.readTimeout' value='30'/> <preference name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount' value='0'/> <preference name='offering.service.repositories.areUsed' value='true'/> <preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode' value='false'/> <preference name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication' value='false'/> <preference name='http.ntlm.auth.kind' value='NTLM'/> <preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/> <preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/> <preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles' value='false'/> <preference name='PassportAdvantageIsEnabled' value='false'/> <preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/> </agent-input>

Tips:

Make sure that the repository location points to the web-based or local product repository. For example:
<repository location='https://downloads.mycorp.com:8080/WAS_85_repository'/>

The following line from the example specifies the default value of the profile location for IBM i:
<data key='was.install.os400.profile.location' value='/QIBM/UserData/WebSphere/AppServer/V85/LibertyCore'/>
To override this default location, specify a different location

The following line from the example specifies the default value of the shared resources directory for IBM i:
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='/QIBM/UserData/InstallationManager/IMShared'/>
To override this default location, specify a different location
There is only one shared resources directory for Installation Manager. If there has been an installation on the system in the past, it will use that shared resources directory and not the one specified in the response file.

To disable remote searches for updates in the response file, set the following preferences to false:

offering.service.repositories.areUsed
Used for searching remote repositories for updates to installed offerings

com.ibm.cic.common.core.preferences.searchForUpdates
Used for searching for updates to Installation Manager

For example:
<preference value='false' name='offering.service.repositories.areUsed'/> <preference value='false' name='com.ibm.cic.common.core.preferences.searchForUpdates'/>
We can find more details on silent preference keys in the IBM Installation Manager Information Center.

To install more than one instance of an offering, we must make the profile ID of each additional instance unique. For example:
<offering profile='WebSphere Liberty V8.5 - Another User's WAS Liberty CORE' features='' id='com.ibm.websphere.liberty.v85'/>
This must be changed in both places that specify the profile ID in the response file.

Here are some examples of changes that you could make to manipulate this response file to perform alternative actions.

To alter the location of the installation, simply change the installation location. For example:
Replace
<profile id='WebSphere Liberty V8.5' installLocation='/QIBM/ProdData/WebSphere/AppServer/V85/LibertyCore'>
with
<profile id='WebSphere Liberty V8.5' installLocation='/home/user/IBM/Websphere/AppServer/V85/Server'>

To install from a local repository instead of the live remote repository, replace the repository location. For example:
Replace
<repository location='http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85'/>
with
<repository location='/home/user/repositories/WAS85/local-repositories'/>

To add the optional features, add each desired feature in the offering as an entry in a comma-separated list.
In the following list, the offering IDs to be used in the response files are enclosed in parentheses:

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.

For example, to install the Embeddable EJB container:
Replace
<offering profile='WebSphere Liberty V8.5' features='' id='com.ibm.websphere.liberty.v85'/>
with
<offering profile='WebSphere Liberty V8.5' features='embeddablecontainer' id='com.ibm.websphere.liberty.v85'/>

We can specify additional assets to install from the Liberty Repository.
To install Liberty Repository assets, have access to the internet, and have IBM Installation Manager v1.6.2 or later. Previous versions of Installation Manager do not have the option to install Liberty Repository assets. If we are using a response file and have not updated Installation Manager to 1.6.2 or later, the assets that we specify in the response file are ignored during the installation.
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 two extra data key elements in the response file. We can use either the symbolic name or the short name.
The following example installs the Portlet Container and Portlet Serving features using the symbolic name.
<data key='user.feature' value='com.ibm.websphere.appserver.portlet-2.0,,com.ibm.websphere.appserver.portletserving-2.0'/> <data key='user.accept.license' value='true'/>
The following example installs the Portlet Container and Portlet Serving features using the short name:
<data key='user.feature' value='portlet-2.0,,portletserving-2.0'/> <data key='user.accept.license' value='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:

Install Liberty Repository assets

Liberty features

The following example installs the Extended Programming Models using the user.addon parameter and the Portlet Container and Portlet Serving features using the user.feature parameter with symbolic names:
<data key='user.addon' value='extendedPackage-1.0'/> <data key='user.feature' value='com.ibm.websphere.appserver.portlet-2.0,,com.ibm.websphere.appserver.portletserving-2.0'/> <data key='user.accept.license' value='true'/>
The following example installs the Extended Programming Models using the user.addon parameter and the Portlet Container and Portlet Serving features using the user.feature parameter with short names:
<data key='user.addon' value='extendedPackage-1.0'/> <data key='user.feature' value='portlet-2.0,,portletserving-2.0'/> <data key='user.accept.license' value='true'/>

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

Parent topic:

Install Liberty on IBM i operating systems
Tasks:

Install Liberty on IBM i operating systems using the command line

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

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.