Preparing response files to install WebSphere Process Server as a

Chapter 3. Preparing the environment

4.2 Installing WebSphere Process Server binaries

4.2.1 Preparing response files to install WebSphere Process Server as a

The following steps prepare the response files located in the software repository downloaded in 3.6, “Creating a software repository” on page 35:

1. The response file and script for installing the WebSphere Process Server are located in the following <base_dir>/responsefiles/WBI directory. The files are:

– Script file: run_templates

– Response file: template_response.xml

2. Back up the original run_templates script and template_response.xml

response file (Example 4-1).

Example 4-1 Backup commands

$ mv run_templates wps_binary_install

$ mv template_response.xml wps_binary_install_template.xml

3. Edit the wps_binary_install script in accord with Example 4-2. All changes that are required are highlighted in bold.

Example 4-2 Edit the install script

#!/bin/sh

#################################################################### # sample_run_templates

# Note: Before you run this script, make sure that you modify the parameters that follow this comment. Also make sure that you # have modified all of the options in the response file template. If required also comment out steps that

# you do not need to perform (for example, comment out WAS install if the product is already installed on your system).

# All templates are run relative to the directory in which this script runs.

#################################################################### #

# Set the directory name where this file is located. curdir="`pwd`"

PROGDIR="`dirname "$0"`" cd "${PROGDIR?}"

cd "${curdir?}"

TEMPDIR=/tmp/wbpm/install

############## PARAMETERS ############## WAS_IMAGE="${PROGDIR}"/../../WAS

# AIX default WAS_LOCATION=/usr/IBM/WebSphere/ProcServer # HP-UX default WAS_LOCATION=/opt/IBM/WebSphere/ProcServer # SunOS default WAS_LOCATION=/opt/IBM/WebSphere/ProcServer # Linux default WAS_LOCATION=/opt/ibm/WebSphere/ProcServer # WAS_LOCATION = the path to the directory where WebSphere Application Server Network Deployment will be installed to

WAS_LOCATION=/opt/IBM/WebSphere/ProcServer

IM_IMAGE="${PROGDIR}"/../../IM KEYRING=

#####################################################

# Install WebSphere Application Server Network Deployment silently as a non-root user.

# Note: Comment out this section if WebSphere Application Server Network Deployment is already installed

#####################################################

"${WAS_IMAGE}"/install -silent -OPT silentInstallLicenseAcceptance=true -OPT

allowNonRootSilentInstall=true -OPT disableOSPrereqChecking=true -OPT disableNonBlockingPrereqChecking=true -OPT

installType=installNew -OPT profileType=none -OPT

feature=samplesSelected -OPT feature=languagepack.console.all -OPT feature=languagepack.server.all -OPT

installLocation="${WAS_LOCATION}"

echo WAS rc: $?

#####################################################

# Install WebSphere Process Server and prerequisite products. #

# The example template runs the following procedures: # 1. Install or update to IM v1.3.2

# 2. Synchronize the WebSphere Application Server Network Deployment installation with IM

# 3. Install the WebSphere Application Server Feature Pack for XML # 4. Install the WebSphere Application Server Feature Pack for SCA # 5. Install WebSphere Process Server using IM

###################################################### # Installs WebSphere Process Server silently as non-root user echo "${IM_IMAGE}"/userinst --launcher.ini

"${IM_IMAGE}"/user-silent-install.ini -input "${PROGDIR}"/wps_binary_install.xml -log "${WAS_LOCATION}"/wps/silent_install.log "${IM_IMAGE}"/userinst --launcher.ini "${IM_IMAGE}"/user-silent-install.ini -input "${PROGDIR}"/wps_binary_install.xml -log "${WAS_LOCATION}"/wps/silent_install.log exit $?

4. Edit the wps_binary_install_template.xml file as shown in Example 4-3. All changes that are required are highlighted in bold.

a. Edit the repository section to add fix pack repositories. Add the location of local repositories that have been downloaded and extracted in the

repository section.

Example 4-3 Edit wps_binary_install_template.xml file

<!--<repository

location="http://public.dhe.ibm.com/software/websphere/repositories/" />-->

</server>

b. Edit the location of the Installation Manager (Example 4-4).

Example 4-4 Edit the Installation Manager location

<!--

################################################################# #####

This profile node defines where IBM Installation Manager (IM) is/or will be installed.

If you want to modify where IM is installed modify both the installLocation and eclipseLocation values to specify the correct directory

################################################################# ###########-->

<profile kind='self' installLocation='/opt/IBM/IM/eclipse' id='IBM Installation Manager'>

<data key='eclipseLocation' value='/opt/IBM/IM/eclipse'/> </profile>

c. Edit the profile install location. References to the Installation Manager profile refer to the binary installation location,

not

the WebSphere Application Server profiles (Example 4-5).

Example 4-5 Edit profile install location

If you would like to create the default profile uncomment and provide valid values for the ID and password properties below ################################################################# ########### # AIX default installLocation/eclipseLocation='/usr/IBM/WebSphere/ProcServer' # HP-UX default installLocation/eclipseLocation='/opt/IBM/WebSphere/ProcServer' # SunOS default installLocation/eclipseLocation='/opt/IBM/WebSphere/ProcServer'

Note: For this publication, the response file has been modified to

specify that the Installation Manager be installed in

/opt/IBM/IM/eclipse and the cache installed in

# Linux default

installLocation/eclipseLocation='/opt/ibm/WebSphere/ProcServer' -->

<profile installLocation='/opt/IBM/WebSphere/ProcServer' id='IBM WebSphere Application Server - ND'>

<data key='eclipseLocation'

value='/opt/IBM/WebSphere/ProcServer'/>

<!-- ###################################

</profile>

d. Edit the command to import WebSphere Application Server Network Deployment to IM (Example 4-6).

If you changed the profile ID in Example 4-5 on page 42, you must also change the profile ID here.

Example 4-6 Add WAS imports

<!--

################################################################# #####

This command directs IM to import WebSphere Application Server Network Deployment, whose location is specified in the previous section, into IM.

If you changed the profile ID above, you must also change the profile ID here.

################################################################# ###########-->

<import profile="IBM WebSphere Application Server - ND" type="WAS" /

e. Specify that you want to install the required prerequisites along with WebSphere Process Server.

f. If the profile ID in Example 4-5 on page 42 has been changed, then the profile ID must be changed here as well. Recall that the term

profile

in Installation Manager refers to the binary installation location

(Example 4-7).

Example 4-7 Add prerequisite install

</install>

g. Because we are installing fix pack updates from local artifacts along with the base install, the values in Example 4-8 need to be changed in the response file.

Example 4-8 Add fix packs

<!--

################################################################# #####

Modifying the properties in this section depends upon your type of install and might be required if you are installing updates along with the base install .

################################################################# ###########--> <preference value="true" name="offering.service.repositories.areUsed" /> <preference value="false" name="com.ibm.cic.common.core.preferences.searchForUpdates" />

In document Deploying WebSphere Business Process Management V7 in Secured Production Environments (Page 53-58)