This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.

Installing Liberty on distributed operating systems by using response files

You can install WebSphere® Application Server Liberty Core by using Installation Manager response files.

Before you begin

Prepare each of the systems onto which you want to install the offering as described in Installing Installation Manager and preparing to install Liberty.

About this task

Using Installation Manager, you can work with response files to install the offering in various ways. You can record a response file by using the GUI as described in the following procedure, create a new response file, or copy and modify an existing response file.

[8.5.5.4 or later]To install Version 8.5.5.4 and later of Liberty, you must have IBM Installation Manager Version 1.6.2 or later.

Procedure

  1. Optional: Record a response file to install the offering.

    On one of your systems, perform the following actions to record a response file that can install the offering.

    1. From a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.
    2. Start Installation Manager from the command line by using the -record option.
      For example:
      • For Windows platforms Administrator or non-administrator:
        IBMIM.exe -skipInstall "C:\temp\imRegistry" 
          -record C:\temp\install_response_file.xml
      • For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platformsAdministrator:
        ./IBMIM -skipInstall /var/temp/imRegistry 
          -record /var/temp/install_response_file.xml
      • For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platformsNon-administrator:
        ./IBMIM -skipInstall user_home/var/temp/imRegistry 
          -record user_home/var/temp/install_response_file.xml
      Tip: When you record a new response file, you can specify the -skipInstall parameter. Using this parameter has the following benefits:
      • No files are installed, which speeds up the recording.
      • If you use a temporary data location with the -skipInstall parameter, Installation Manager writes the installation registry to the specified data location while recording. When you start Installation Manager again without the -skipInstall parameter, you then can use your response file to install against the real installation registry.

        Do not use the -skipInstall operation on the agent data location that is used by Installation Manager. This operation is unsupported. Use a clean writable location, and reuse that location for future recording sessions.

      For more information, read the IBM® Installation Manager documentation.

    3. Follow the instructions that are described in Installing Liberty on distributed operating systems using the GUI.
  2. Optional: Create a credential-storage file for installation. If you are using an authenticated remote repository, you can store credentials for URLs that require authentication, such as remote repositories, in a credential-storage file. For IBM Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. For previous versions of Installation Manager, the -keyring and -password options are used to access credentials in a keyring file. These options are deprecated in Version 1.6.2. There is no migration path from keyring files to storage files because of the differences in the file structures.
  3. Use the response files to install the offering.

    Go to a command line on each of the systems on which you want to install the offering, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the offering.

    For example:
    • For Windows platforms Administrator or non-administrator:
      imcl.exe -acceptLicense 
        input C:\temp\install_response_file.xml 
        -log C:\temp\install_log.xml 
        -secureStorageFile C:\IM\credential.store -masterPasswordFile C:\IM\master_password_file.txt
    • For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platformsAdministrator:
      ./imcl -acceptLicense 
        input /var/temp/install_response_file.xml 
        -log /var/temp/install_log.xml 
        -secureStorageFile /var/IM/credential.store -masterPasswordFile /var/IM/master_password_file.txt
    • For AIX platformsFor HP UNIX platformsFor LINUX platformsFor Solaris platformsNon-administrator:
      ./imcl -acceptLicense 
        input user_home/var/temp/install_response_file.xml 
        -log user_home/var/temp/install_log.xml 
        -secureStorageFile user_home/var/IM/credential.store -masterPasswordFile user_home/var/IM/master_password_file.txt
    Notes:
    • The relevant terms and conditions, notices, and other information are provided in the license-agreement files in the lafiles or offering_name/lafiles subdirectory of the installation image or repository for this offering.
    • The program might write important post-installation instructions to standard output.

    Read the IBM Installation Manager documentation for more information.

Example

For Windows platformsThe following is an example of a response file for installing the offering.
<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean="true" temporary="true">
<server>
<repository location="http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85" />
</server>
<install modify='false'>
<offering id='com.ibm.websphere.liberty.v85' 
  profile='WebSphere Liberty V8.5' 
  features='embeddablecontainer' installFixes='none'/>
</install>
<profile id='WebSphere Liberty V8.5' 
  installLocation='C:\Program Files\IBM\WebSphere\Liberty'>
</profile>
</agent-input>
For AIX platformsFor LINUX platformsFor Solaris platformsFor Windows platformsImportant: If you are installing on a 64-bit system, you must include one of the options for an IBM Software Development Kit.
  • You can use the cic.selector.arch property key and related value to specify the architecture to install, 32 bit or 64 bit.
    Here is an example of specifying a 32-bit architecture:
    <profile>
    ...
    <data key='cic.selector.arch' value='x86'/>
    ...
    </ptofile>

    If you do not specify anything for this key, you receive a correct match for your system. For a 64-bit system, the installation defaults to a 64-bit installation.

    Your choice here applies to all packages that are installed in the package group. For information about the supported values for the cic.selector.key keys, see the Values for cic.selector.key table in the Installation Manager documentation.

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'/>
You can find more details on silent preference keys in the IBM Installation Manager documentation.
The following examples show you how to change response file in order to perform alternative actions.
  • To install multiple copies of this offering, specify a different installation location and a new package group for each installation. For example, to install a second copy of the offering into the C:\Program Files\IBM\WebSphere\Liberty_2 directory and create the WebSphere Liberty V8.5_2 package group, replace:
    <profile id='WebSphere Liberty V8.5' 
      installLocation='C:\Program Files\IBM\WebSphere\Liberty'>
    with:
    <profile id='WebSphere Liberty V8.5_2'
      installLocation='C:\Program Files\IBM\WebSphere\Liberty_2'>
  • To add optional features, add them as an entry in a comma-separated list. For example:
    <offering id='com.ibm.websphere.liberty.v85' 
      profile='WebSphere Liberty V8.5'
      features='embeddablecontainer' installFixes='none'/>
    • 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 that you can use to run enterprise beans in a standalone Java Platform, Standard Edition (SE) environment. You can run enterprise beans by 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.
  • Liberty Repository[8.5.5.2 or later]You can specify additional assets to install from the Liberty Repository. For a list of Liberty Repository assets, see the downloads page on WASdev.net.

    To install Liberty Repository assets, you must have access to the internet, and you must have IBM Installation Manager Version 1.6.2 or later. Previous versions of Installation Manager do not have the option to install Liberty Repository assets. If you use a response file and did not update Installation Manager to Version 1.6.2 or later, the assets that you specify in the response file are ignored during installation.

    If you want to install additional features, specify two extra data key elements in your response file. You 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'/>
    [8.5.5.5 or later]For Version 8.5.5.5 and later, user.accept.license=true is not required.
    Liberty Repository[8.5.5.4 or later]Beginning with Version 8.5.5.4, the extprogmodels feature is no longer available. Instead, install the extendedPackage-1.0 addon, or install the individual features that you need from the Liberty Repository. See the following topics for more information:
    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'/>
    [8.5.5.5 or later]For Version 8.5.5.5 and later, user.accept.license=true is not required.
    Liberty Repository[8.5.5.6 or later]You can also install assets from an instance of the Liberty Asset Repository Service or local directory-based repositories. For more information, see Installing assets using Installation Manager. Add the repository on repository elements. If Installation Manager does not recognize the repository, point directly to the repository.config file. When you install assets, the repositories are accessed in the order that you specify them.
    <server>
    <repository location="http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.v85" />
    <repository location="https://your_onprem_asset_repo_url" />
    <repository location="D:\IBM\LocalAssetRepo" />
    [8.5.5.8 or later]<repository location="D:\IBM\LocalAssetRepo2.zip" />
    </server>
    By default, the Liberty Repository is the last of the repositories that are accessed during installation. To disable access to the Liberty Repository, set the user.useLibertyRepository parameter to false:
    <data key='user.addon' value='extendedPackage-1.0'/>
    <data key='user.feature' value='portlet-2.0,,portletserving-2.0'/>
    <data key='user.useLibertyRepository' value='false'/>

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

  • 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 versions 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 changing the following preference in your response file:
    <preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/>
    to this:
    <preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='false'/>

    For more information on setting your Installation Manager preferences, see the IBM Installation Manager documentation.

    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.

Icon that indicates the type of topic Task topic



Timestamp icon Last updated: Tuesday, 12 December 2017
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-libcore-mp&topic=twlp_ins_installation_dist_silent
File name: twlp_ins_installation_dist_silent.html