Sample response file: Install IBM Web Enablement Liberty for IBM i

We can edit and use this example of a response file for installing IBM Web Enablement Liberty for IBM i.

<?xml version="1.0" encoding="UTF-8"?>

<!-- ##### Copyright ######################################################
# Licensed Materials - Property of IBM (c) Copyright IBM Corp. 2013. 
# All Rights Reserved. US Government Users Restricted Rights-Use, duplication 
# or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
####################################################################### -->

<!-- ##### Frequently Asked Questions #####################################
# The latest information about using Installation Manager is 
# located in the online Information Center. There we can find 
# information about the commands and attributes used in 
# silent installation response files.
# 
#     Installation Manager Information Center can be found at:
#     http://publib.boulder.ibm.com/infocenter/install/v1r6/index.jsp
# 
# Question 1. How do I record a response file using Installation Manager?
# Answer 1. Start Installation Manager from the command line under the 
# eclipse subdirectory with the record parameter and it will generate a  
# response file containing actions it performed, repositories it used, and   
# its preferences settings. Optionally use the -skipInstall parameter if 
# we do not want the product to be installed to the machine. Specify a  
# new agentDataLocation location value when doing a new installation. Do  
# not use an existing agentDataLocation for an installation because it might  
# damage the installation data and prevent you from modifying, updating,  
# rolling back, or uninstalling the installed packages.
#
# Windows: IBMIM -record <responseFile> -skipInstall <agentDataLocation>
# Linux or UNIX: ./IBMIM -record <responseFile> -skipInstall <agentDataLocation>
# 
# For example:
#   Windows = IBMIM.exe -record c:\temp\responsefiles\WASv85.install.Win32.xml
#     -skipInstall c:\temp\skipInstall\WebSphere_Temp_Registry
#   Linux or UNIX = ./IBMIM -record /home/user/responsefiles/WASv85.install.RHEL64.xml
#     -skipInstall c:\temp\skipInstall\WebSphere_Temp_Registry
# 
# Question 2. How do I run Installation Manager silently using response file?
# Answer 2. Create a silent installation response file, and run the following command 
# from the eclipse\tools subdirectory in the directory where you installed 
# Installation Manager:
#
#   Windows = imcl.exe -acceptLicense -showProgress 
#     input <response_file_path_and_name> -log <log_file_path_and_name> 
#   Linux, UNIX, IBM i and z/OS = ./imcl -acceptLicense -showProgress  
#     input <response_file_path_and_name> -log <log_file_path_and_name> 
# 
# For example: 
#   Windows = imcl.exe -acceptLicense -showProgress
#     input c:\temp\responsefile\WASv85.install.Win32.xml 
#   Linux, UNIX, IBM i and z/OS = ./imcl -acceptLicense -showProgress
#     input /home/user/responsefile/WASv85.install.RHEL64.xml
# 
# The -acceptLicense command must be included to indicate acceptance of all
#     license agreements of all offerings being installed, updated or modified.
# The -showProgress command shows progress when running in silent mode.
# Additional commands can be displayed by requesting help:  IBMIM -help
#
# Question 3. How do I store and pass credentials to repositories that 
# require authentication?
# Answer 3.  There are two methods for storing authentication credentials 
# for Installation Manager depending on the version being used, # either key ring files or storage files.
#
# Versions of Installation Manger before 1.6.2 use a key ring file to store 
# encrypted credentials for authenticating with repositories. Follow this 
# two-step process for creating and using a key ring file with Installation Manager.
# 
# First, create a key ring file with the credentials by starting 
# Installation Manager from the command line under eclipse subdirectory 
# with the keyring parameter.
# Use the optional password parameter to password protect the file.
# 
#   Windows = IBMIM.exe -keyring <path and file name> -password <password>
#   Linux, UNIX, IBM i and z/OS = ./IBMIM -keyring <path and file name> 
#                                 -password <password>
# 
# Installation Manager will start in graphical mode. Verify that the 
# repositories to which we need to authenticate are included in the 
# preferences, File / Preferences / Repositories. If they are not 
# listed, then click Add Repositories to add the URL or UNC path.
# Installation Manager will prompt for the credentials. If the repository 
# is already in the list, then any attempt to access the repository location, 
# such as clicking the Test Connections button, will also prompt for our # credentials. Enter the correct credential and check the Save password 
# checkbox. The credentials are saved to the key ring file you specified. 
# 
# Second, when you start a silent installation, run imcl under eclipse/tools
# subdirectory, and provide Installation Manager with the location of the key 
# ring file and the password if the file is protected. For example:
#
#   Windows = imcl.exe -acceptLicense -showProgress
#     input <path and file name of response file>
#     -keyring <path and name of key ring file> -password <password>
#   Linux, UNIX, IBM i and z/OS = ./imcl -acceptLicense -showProgress
#     input <path and file name of response file> 
#     -keyring <path and name of key ring file> -password <password>
#
# Versions of Installation Manager at 1.6.2 or higher use storage files 
# to store encrypted credentials. Complete the following steps to create # master password and storage files to use with Installation Manager.
#
# First, if we do not have a master password file already, create a text file 
# containing a master passphrase. An example of a passphrase is:
#   "This text is the passphrase for a master password file."
#
# Next, run imutilsc under the eclipse/tools subdirectory with the following 
# options to create and store user credentials in a storage file.
#   -secureStorageFile <path and file name of storage file>
#   -masterPasswordFile <path and file name of master password file>
#   -url <repository address> or -passportAdvantage <PPA repository address>
#   -userName <user name> 
#   -userPassword <password for user>
#
#  Example of a command to create a storage file by operating system #  Windows = imutilsc saveCredential -url http://myServer -userName myUserName 
#     -userPassword myPassword -secureStorageFile C:\IBM\credential.store 
#     -masterPasswordFile C:\IBM\master_password_file.txt
#  Linux, UNIX, IBM z/OS, and the OS X operating system = 
#    ./imutilsc saveCredential -url http://myServer -userName myUserName 
#    -userPassword myPassword -secureStorageFile /home/IBM/credential.store 
#    -masterPasswordFile /home/user/IBM/master_password_file.txt
#
# Usage hints:
#    * Do not use both the -url and -passportAdvantage options in the same command.
#    * Enclose file paths that include spaces with double quotation marks.
#    * If we use the IBM service repositories, we can specify the value:
#        http://www.ibm.com/software/repositorymanager/entitled/repository.xml   
#      for the -url option which is a generic service repository for IBM packages.
#    * Repeat steps to store credentials for multiple users in one file.
#    * Repeat steps to store credentials for multiple repositories in one file.
#
# Afterwards, when you start a silent installation, run imcl under the eclipse/tools
# subdirectory, and provide Installation Manager with the location of the storage 
# file. For example:
#
#   Windows = imcl.exe -acceptLicense -showProgress
#     input <path and file name of response file>
#     -secureStorageFile <path and name of storage file> 
#     -masterPasswordFile <path and name of master password file>
#   Linux, UNIX, IBM i and z/OS = ./imcl -acceptLicense -showProgress
#     input <path and file name of response file> 
#     -secureStorageFile <path and name of storage file> 
#     -masterPasswordFile <path and name of master password file>
#
####################################################################### -->

<!-- ##### Agent Input ##############################################
#
# Note that the acceptLicense attribute has been deprecated. 
# Use the -acceptLicense command line option to accept license agreements.
#
# The clean and temporary attributes specify the repositories and other # preferences Installation Manager uses and whether those settings # should persist after the installation finishes.
# 
# Valid values for clean:
#      true = only use the repositories and other preferences that are 
#           specified in the response file.
#      false = use the repositories and other preferences that are 
#           specified in the response file and Installation Manager.
# 
# Valid values for temporary:
#      true = repositories and other preferences specified in the 
#           response file do not persist in Installation Manager.
#      false = repositories and other preferences specified in the 
#           response file persist in Installation Manager.
# 
####################################################################### -->

<agent-input clean="true" temporary="true">

<!-- ##### Repositories ###################################################
# Repositories are locations that Installation Manager queries for 
# installable packages. Repositories can be local (on the machine
# with Installation Manager) or remote (on a corporate intranet or 
# hosted elsewhere on the internet). 
# 
# If the machine using this response file has access to the internet, 
# then include the IBM WebSphere Live Update Repositories in the list 
# of repository locations. 
# 
# If the machine using this response file cannot access the internet, 
# then comment out the IBM WebSphere Live Update Repositories and 
# specify the URL or UNC path to custom intranet repositories and 
# directory paths to local repositories to use.
# 
####################################################################### -->

<server>
    <!-- ##### IBM WebSphere Live Update Repositories ####################
     # These repositories contain WebSphere Application Server Liberty offerings, 
     # and updates for those offerings
     # 
     # To use the secure repository (https), have an IBM ID, 
     # which can be obtained by registering at: http://www.ibm.com/account
     # or the Passport Advantage account.
     # 
     # And, use a key ring file with the response file.
     ################################################################## -->
<repository location="http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.WEBENAB.v85"/>
    <!-- <repository location="https://www.ibm.com/software/rational/repositorymanager/repositories/websphere" /> -->

    <!-- ##### Custom Repositories #######################################
     # Uncomment and update the repository location key below 
     # to specify URLs or UNC paths to any intranet repositories 
     # and directory paths to local repositories to use.
     ################################################################## -->
    <!-- <repository location='https:\\w3.mycompany.com\repositories\'/> -->
    <!-- <repository location='/home/user/repositories/websphere/'/> -->

    <!-- ##### Local Repositories ########################################
     # Uncomment and update the following line when using a local      # repository located on our own machine to install a 
     # WebSphere Application Server Liberty offering.
     ############################################################# -->
    <!-- <repository location='insert the full directory path inside single quotes'/> -->
</server>

<!-- ##### Install Packages ###############################################
#
# Install Command
#
# Use the install command to inform Installation Manager of the 
# installation packages to install. 
# 
# The modify attribute is optional and can be paired with an install 
# command to add features or paired with an uninstall command to 
# remove commands. If omitted, the default value is set to false.
#    false = indicates not to modify an existing install by adding 
#            or removing features.
#    true = indicates to modify an existing install by adding or 
#           removing features.
# 
# The offering ID attribute is required because it specifies the 
# offering to be installed. The offering listed must be present in 
# at least one of the repositories listed earlier. The example 
# command below contains the offering ID for the WEBENAB 
# edition of WAS Liberty. 
# 
# The version attribute is optional. If a version number is provided, 
# then the offering will be installed at the version level specified 
# as long as it is available in the repositories. If the version 
# attribute is not provided, then the default behavior is to install 
# the latest version available in the repositories. The version number 
# can be found in the repository.xml file in the repositories.
# For example, <offering ... version='8.5.5000.20130326_0211'>.
# 
# The profile attribute is required and typically is unique to the # offering. If modifying or updating an existing installation, the 
# profile attribute must match the profile ID of the targeted installation 
# of WAS Liberty.
# 
# The features attribute is optional. Offerings always have at least
# one feature; a required core feature which is installed regardless 
# of whether it is explicitly specified. If other feature names 
# are provided, then only those features will be installed. 
# Features must be comma delimited without spaces.
# 
# The feature values for WebSphere Application Server Liberty include:
#  liberty,embeddablecontainer,extprogmodels
#
# The features embeddablecontainer,extprogmodels
# are subfeatures of liberty.
# 
# We can use these functions to add or remove feature embeddablecontainer or extprogmodels later.
# 
# The installFixes attribute indicates whether fixes available in 
# repositories are installed with the product. By default, all 
# available fixes will be installed with the offering.
# 
# Valid values for installFixes:
#      none = do not instavailable fixes with the offering.
#      recommended = installs available recommended fixes with the offering.
#      all = installs available fixes with the offering.
# 
# Interim fixes for offerings also can be installed while they
# are being installed by including the offering ID for the interim
# fix and specifying the profile ID. 
# 
# Installation Manager supports installing multiple offerings at once.
# Additional offerings can be included in the install command, # with each offering requiring its own offering ID, version, profile value, 
# and feature values.
# 
# Profile Command
# 
# A separate profile command must be included for each offering listed 
# in the install command. The profile command informs Installation # Manager about offering specific properties or configuration values.
# 
# The installLocation specifies where the offering will be installed.
# If the response file is used to modify or update an existing 
# installation, then ensure the installLocation points to the 
# location where the offering was installed previously. 
# 
# The eclipseLocation data key should use the same directory path to 
# WebSphere Application Server Liberty as the installationLocation attribute.
# 
# Include data keys for product specific profile properties. 
# For instance, Installing WebSphere Application Server Liberty Offerings on 
# a 64-bit system will require to include one of the options for an IBM Software 
# Development Kit, this can be specified by data key cic.selector.arch, its value 
# can be either x86 (for 32-bit), or x86_64 (for 64-bit).
# 
# More details for cic.selector.arch can be found in the link below:
#
# https://infocenters.hursley.ibm.com/was/vNext/draft/help/index.jsp?topic=%2Fcom.ibm.websphere.wlp.core.doc%2Fae%2Ftwlp_ins_installation_dist_silent.html
# 
####################################################################### -->

<install modify="false">
<offering id="com.ibm.websphere.liberty.WEBENAB.v85" profile="WebSphere Liberty V8.5" features="liberty,embeddablecontainer,extprogmodels" installFixes="none" /> 
</install>
<profile id="WebSphere Liberty V8.5" installLocation="/QIBM/ProdData/WebSphere/Liberty/V85/Express">
<data key="eclipseLocation" value="/QIBM/ProdData/WebSphere/Liberty/V85/Express" />
<data key="cic.selector.arch" value="x86_64" /> 
</profile>

<!-- ##### Shared Data Location ###########################################
# Uncomment the preference for eclipseCache to set the shared data 
# location the first time we use Installation Manager to do an 
# installation.
# 
# Eclipse cache location can be obtained from the installed.xml file found in 
# Linux/Unix: /var/ibm/InstallationManager
# Windows: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager # from the following property:  
# <property name='cacheLocation' value='C:\Program Files\IBM\IMShared'/>
#
# Open the installed.xml file in a text editor because the style sheet 
# might hide this value if opened in a web browser.
# For further information on how to edit preferences, refer to the public library at:
# http://publib.boulder.ibm.com/infocenter/install/v1r5/index.jsp?topic=/com.ibm.silentinstall12.doc/topics/r_silent_prefs.html
#
# After the shared data location is set, it cannot be changed
# using a response file or the graphical wizard.
# 
# Ensure that the shared data location is a location that can be written 
# to by all user accounts that are expected to use Installation Manager.
#
# By default, Installation Manager saves downloaded artifacts to 
# the shared data location. This serves two purposes. 
# 
# First, if the same product is installed a more than once to the machine, 
# then the files in the shared data location will be used rather than 
# downloading them again. 
# 
# Second, during the rollback process, the saved artifacts are used. 
# Otherwise, if the artifacts are not saved or are removed, then 
# Installation Manager must have to access the repositories used to 
# install the previous versions.
# 
# Valid values for preserveDownloadedArtifacts:
#     true = store downloaded artifacts in the shared data location #     false = remove downloaded artifacts from the shared data location # 
####################################################################### -->

<!-- 
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='C:\Program Files\IBM\IMShared'/>
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/> 
-->


<!-- ##### Preferences Settings ###########################################
# Additional preferences for Installation Manager can be specified. 
# These preference correspond to those that are located in the graphical
# interface under File / Preferences. 
# 
# If a preference command is omitted from or commented out of the response 
# file, then Installation Manager uses the preference value that was 
# previously set or the default value for the preference. 
# 
# Preference settings might be added or deprecated in new versions of # Installation Manager. Consult the online Installation Manager # Information Center for the latest set of preferences and 
# descriptions about how to use them.
#
# http://publib.boulder.ibm.com/infocenter/install/v1r6/index.jsp
# 
####################################################################### -->

<!--
<preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.readTimeout' value='45'/>
<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.keepFetchedFiles' value='false'/>
<preference name='PassportAdvantageIsEnabled' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/>
<preference name='com.ibm.cic.agent.ui.displayInternalVersion' value='false'/>
 --> 
 
</agent-input>

Parent topic: Use the sample response files