Response file for silent installation

The response file provides input to the Installation Manager (IM) when it is running a silent installation. You edit the response file to control the silent installation.

The response file is located in the responsefiles directory at the top level of your WSRR product DVD or download directory. All the default paths specified in the response file are relative to the responsefiles directory. The file is named template_response.xml. The response file is called from the silent installation script and should not be moved or renamed (although you can make a copy of the original response file before you modify it so that you can revert to the default version if required).

The response file passes parameters to the IM silent installation command. The response file completes the following tasks:

Defines the repositories that IM uses to locate install or upgrade files for IM, WebSphere Application Server, and WSRR.
Defines the installation location for IM, and installs it. If IM is already installed, it will upgrade itself if required.
Installs WebSphere Application Server Network Deployment.
Installs WSRR into a location relative to the WebSphere Application Server.

You must modify certain fields in the response file before you run the script file that calls it.

Repository locations

A repository is a location that stores data for installing, modifying, rolling back, updating, or uninstalling packages. You modify the response file to specify the location of the following repositories, or you can leave the fields unchanged to accept the default values.

IM Repository Location

Specify the location of the repository that holds installation or update data for IM itself. By default this is set to the IM directory at the top level of your WSRR product DVD or download directory. For example:

<repository location='../IM/' temporary='true'/>

If you do not already have IM installed, and are installing on Windows 64bit or Linux/x86-64, you can choose to use 64-bit IM by specifying the 64-bit IM directory. Specify the following repository location:

<repository location='../IM64/' temporary='true'/>

Note: You cannot update an existing 32-bit IM installation to be 64-bit.

WSRR Repository Location

Specify the location of the repository that holds installation data for WSRR. By default this field is set to the repository directory at the top level of your WSRR product DVD or download directory. For example:

<repository location="../repository/" />

You can also add a repository entry for the location that holds fix packs for your version of WSRR. If you add this repository in addition to the installation repository for WSRR, then the silent installation will install the latest version, including available fix packs.

<repository location="http://public.dhe.ibm.com/software/websphere/bpm/repositories/server/wsrr/850/updates/repository.config" />

Installation Manager location

The silent installation installs itself, or checks for updates if it is already installed. You specify the location where IM will be installed, or already is installed. The response file contains a placeholder path which you must edit.

For example, if you are installing on a UNIX or Linux system, you can specify the standard installation location for IM:

<profile kind='self' installLocation='/opt/IBM/InstallationManager/eclipse' id='IBM Installation Manager'>
  <data key='eclipseLocation' value='/opt/IBM/InstallationManager/eclipse'/>
</profile>

if you are installing on a Windows system, you can specify the standard installation location for IM:

<profile kind='self' installLocation='C:\Program Files\IBM\InstallationManager\eclipse' id='IBM Installation Manager'>
  <data key='eclipseLocation' value='C:\Program Files\IBM\InstallationManager\eclipse'/>
</profile>

You should also edit the Eclipse cache location to match the path that you specified for the IM installation.

Example for Linux and UNIX systems:

<preference value="/opt/IBM/InstallationManager/eclipseCache" name="com.ibm.cic.common.core.preferences.eclipseCache" />

Example for Windows systems:

<preference value="C:\Program Files\IBM\InstallationManager\eclipseCache" name="com.ibm.cic.common.core.preferences.eclipseCache" />

Note: You should not edit the <install> section which instructs the silent install script to install IM. If IM is already installed, this step is skipped.

WebSphere Application Server location

You specify an installation directory for WebSphere Application Server (this directory is also used to install WSRR).

Example for UNIX and Linux systems:

<profile installLocation='/opt/IBM/WebSphere/ServiceRegistry' id='IBM WebSphere Application Server - ND'>
  <data key='eclipseLocation' value='/opt/IBM/WebSphere/ServiceRegistry'/>
  <data key="cic.selector.nl" value="en" />
</profile>

Example for Windows systems:

<profile installLocation='C:\IBM\WebSphere\ServiceRegistry' id='IBM WebSphere Application Server - ND'>
  <data key='eclipseLocation' value='C:\IBM\WebSphere\ServiceRegistry'/>
  <data key="cic.selector.nl" value="en" />

</profile>

You can specify that the WebSphere Application Server Administrative Console is displayed in your local language by adding the following line to the installation directory specification:

<data key="cic.selector.nl" value="language_code"/>

Where language_code specifies the language to display, for example, "ja" for Japanese.

You must ensure that the language pack is available on the client machine where you are accessing the Administrative Console. You must also modify the Install section of the file (see the following description).

The WebSphere Application Server profile name is set to "IBM WebSphere Application Server - ND" by default. If you have an existing WebSphere Application Server installation that uses that profile id, then you must edit the response file to specify an alternative name.

Install section

The <install> section directs the silent install script to install WebSphere Application Server and WSRR. You do not need to modify this section unless you want the WebSphere Application Server Administrative Console to display in your local language.

If you do want the Administrative Console to display in your local language, you should modify this section as shown in the following example:

<install modify=true>
	<offering profile="IBM WebSphere Application Server - ND" id="com.ibm.websphere.ND.v85" 
   features="core.feature,consoleLanguagesSupport.feature,runtimeLanguagesSupport.feature,
   import.configLauncher.feature,import.productProviders.feature"/> 
		<offering profile="IBM WebSphere Application Server - ND" id="com.ibm.wsrr.server" /> 
</install>

Note: If you have edited the response file to display the Administrative Console in your local language, then, after successful installation, you must open the console and edit the JVM properties before the setting takes effect:

In the Administrative Console, select Servers > WebSphere application servers > server_name > Java and Process Management > Process Definition > Java Virtual Machine
Add "-Duser.language=language_code" to the Generic JVM arguments, where language_code is the code for your language. For example "ja" for Japanese.
Close the console and restart the server.