Fix Pack 8550

Installing Liberty on distributed operating systems using response files

You can install WebSphere® Application Server Liberty Network Deployment 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 a variety of ways. You can record a response file using the GUI as described in the following procedure, or you can generate a new response file by hand or by taking an example and modifying it.

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 will 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 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 platforms For HP UNIX platforms For LINUX platforms For Solaris platforms Administrator:
        ./IBMIM -skipInstall /var/temp/imRegistry 
          -record /var/temp/install_response_file.xml
      • For AIX platforms For HP UNIX platforms For LINUX platforms For Solaris platforms Non-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 actually installed, and this 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.

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

      For more information, read the IBM® Installation Manager Information Center.

    3. Follow the instructions described in Installing Liberty on distributed operating systems using the GUI.
  2. Optional: If you are using an authenticated remote repository, create a credential-storage response file for installation.
    Tip: In a credential-storage file, you can store credentials for URLs that require authentication, such as your remote repositories.
    Note: When you use Installation Manager Version 1.6.2 and later, you should use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. In versions of Installation Manager earlier than Version 1.6.2, the -keyring and -password options were used to access credentials in a keyring file. These options were 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. 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.
  3. Use the response files to install the offering.
    1. Optional: Use the response file to install the credential-storage file.

      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 credential-storage file.

      For example:
      • For Windows platforms Administrator or non-administrator:
        imcl.exe -acceptLicense 
          input C:\temp\credentialstorage_response_file.xml 
          -log C:\temp\credentialstorage_log.xml
      • For AIX platforms For HP UNIX platforms For LINUX platforms For Solaris platforms Administrator:
        ./imcl -acceptLicense 
          input /var/temp/credentialstorage_response_file.xml 
          -log /var/temp/credentialstorage_log.xml
      • For AIX platforms For HP UNIX platforms For LINUX platforms For Solaris platforms Non-administrator:
        ./imcl -acceptLicense 
          input user_home/var/temp/credentialstorage_response_file.xml 
          -log user_home/var/temp/credentialstorage_log.xml
    2. Use the response file 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 platforms For HP UNIX platforms For LINUX platforms For Solaris platforms Administrator:
        ./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 platforms For HP UNIX platforms For LINUX platforms For Solaris platforms Non-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 Information Center for more information.

Example

For Windows platforms The 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.ND.v85" />
</server>
<install modify='false'>
<offering id='com.ibm.websphere.liberty.ND.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 platforms For LINUX platforms For Solaris platforms For Windows platforms Important: 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 will get 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 Information Center.

Tip: 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 Information Center.
Here are some examples of changes that you could make to manipulate this response file 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. For example, 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 the optional features, add each desired feature in the offering as an entry in a comma-separated list. For example:
    <offering id='com.ibm.websphere.liberty.ND.v85' 
      profile='WebSphere Liberty V8.5'
      features='embeddablecontainer,extprogmodels' 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 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.

    • Extended Programming Models (extprogmodels)

      The Extended Programming Models feature provides a rich set of programming models such as Web Services, JMS (including Message-Driven Beans), and Mongo 2.0.

    Note: If no features are specified, the default features (embeddablecontainer and extprogmodels) are installed. To install only the feature that you want, specify that feature explicitly.
  • Fix Pack 8552 You can add a list of additional features that are separated by commas:
    Choose from the following additional features:
    • Portlet Serving: provides the Portlet serving or URL addressability functionality for JSR 168 and JSR 286 compliant portlets. This feature allows you to invoke a portlet under a defined URL from a browser.
    • Portlet Container: provides a runtime environment for JSR 168 and JSR 286 compliant portlets.
    • Web Cache Monitor: provides monitoring of the distributed map cache, with simple cache statistics, cache entries, and cache policy information for Servlet cache instances.
    The following message contains information about additional features:
    # Two optional data keys were introduced for WebSphere Application Server Liberty
    # offerings in version 8.5.5.2 that enable installing additional product assets 
    # during an installation or update. 
    # 
    #  <data key='user.feature' value='FeatureA,FeatureB'/>
    #  <data key='user.accept.license' value='true'/>
    #
    # Use the user.feature data key to specify the names of one or more assets to install. 
    # Separate multiple assets names with a comma.
    #
    # For Liberty version 8.5.5.2, the available assets are: 
    #   com.ibm.websphere.appserver.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.
    #   com.ibm.websphere.appserver.portletserving-2.0 - This feature provides the Portlet serving 
    #   or URL Addressability functionality for JSR 168 and JSR 286 compliant portlets. This 
    #   feature allows to invoke a portlet under a defined URL from a browser.
    #   com.ibm.websphere.appserver.portlet-2.0 - This feature provides a runtime environment 
    #   for JSR 168 and JSR 286 compliant portlets.
    # 
    # A current list of the assets available for installation is maintained in the following article.
    #    http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twlp_ins_installation_dist_gui
  • 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 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 Information Center.

    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

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Monday, 21 April 2014
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twlp_ins_installation_dist_silent
File name: twlp_ins_installation_dist_silent.html