You can install WebSphere® Application
Server Version 8.5 using Installation Manager response files.
About this task
Using Installation Manager, you can work with response
files to install the product 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
- Optional: Record a response file to install
the product.
On one of your systems, perform the
following actions to record a response file that will install the
product.
- From a command line, change to the eclipse subdirectory
in the directory where you installed Installation Manager.
- Start Installation Manager from the command line using
the -record option.
Tip: When you record a new response file, you
can specify the -skipInstall parameter. Using this parameter has
the following benefits:
For more information, read the IBM® Installation
Manager Version 1.6 Information Center or the IBM Installation
Manager Version 1.5 Information Center.
- Follow the instructions described in Installing the product on distributed operating systems using the GUI.
- Optional: If you are using an authenticated
remote repository, create a keyring response file for installation.
Note: In a keyring file, you can store credentials for URLs
that require authentication, such as your remote repositories.
- From a command line, change to the eclipse subdirectory in the
directory where you installed Installation Manager.
- Start Installation Manager from the command line using the -record
option.
- When a window opens that requests your credentials for the authenticated
remote repository, enter the correct credentials and save them.
- Click File > Exit to close Installation Manager.
For more information on keyring files, read the IBM Installation
Manager Version 1.6 Information Center.
Note: Starting
in Installation Manager Version 1.6.2, the
-keyring and
-password options
that have been used to access credentials in a keyring file are deprecated.
When you use Installation Manager Version 1.6.2 and later, use the
-secureStorageFile and
-masterPasswordFile options
to store credentials in a credential storage file. There is no migration
path from keyring files to storage files because of the differences
in the file structures. You must create a storage file to replace
a keyring file. 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.
- Use the response files to install the product.
- Optional: Use the response file to install
the keyring file.
Go to a command line on each
of the systems on which you want to install the product, change to
the eclipse/tools subdirectory in the directory
where you installed Installation Manager, and install the keyring
file.
- Use the response file to install the product.
Go to a command line on each of the systems on which you
want to install the product, change to the eclipse/tools subdirectory
in the directory where you installed Installation Manager, and install
the product.
Notes: - The relevant terms and conditions, notices, and other information
are provided in the license-agreement files in the lafiles or product_name/lafiles subdirectory
of the installation image or repository for this product.
- The program might write important post-installation instructions
to standard output.
Read the IBM Installation
Manager Version 1.6 Information Center or the IBM Installation
Manager Version 1.5 Information Center for more information.
Example
![[Windows]](../images/windows.gif)
The following is an example of a response
file for installing the product.
<?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.ND.v85" />
</server>
<install modify='false'>
<offering id='com.ibm.websphere.ND.v85'
profile='IBM WebSphere Application Server V8.5'
features='core.feature,ejbdeploy,thinclient,embeddablecontainer,com.ibm.sdk.6_32bit,liberty' installFixes='none'/>
</install>
<profile id='IBM WebSphere Application Server V8.5'
installLocation='C:\Program Files\IBM\WebSphere\AppServer'>
<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='en'/>
</profile>
</agent-input>
![[AIX]](../images/aixlogo.gif)
![[Linux]](../images/linux.gif)
![[Solaris]](../images/solaris.gif)
Important: If you are installing on a 64-bit system, you must
include one of the options for an IBM Software Development Kit.
- If you want to use the 32-bit IBM Software Development Kit, include com.ibm.sdk.6_32bit as
a feature in the response file.
For example:
<offering profile='IBM WebSphere Application Server V8.5'
features='core.feature,com.ibm.sdk.6_32bit' id='com.ibm.websphere.ND.v85'/>
- If you want to use the 64-bit IBM Software Development Kit, include com.ibm.sdk.6_64bit as
a feature in the response file.
For example:
<offering profile='IBM WebSphere Application Server V8.5'
features='core.feature,com.ibm.sdk.6_64bit' id='com.ibm.websphere.ND.v85'/>
Follow these guidelines:
- Include this feature only if you are installing on a 64-bit system;
do not include it if you are installing on a 32-bit system.
- This does not apply to Solaris x86 64-bit
systems.
- You must include one of the two options if you are installing
on a 64-bit system.
- You cannot modify this installation later and change the selection.
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 product, specify a different
installation location and a new package group for each installation.
For example, to install a second copy of the product into the C:\Program
Files\IBM\WebSphere\AppServer_2 directory and create the IBM
WebSphere Application Server V8.5_2 package group:
- Replace
<profile id='IBM WebSphere Application Server V8.5'
installLocation='C:\Program Files\IBM\WebSphere\AppServer'>
with<profile id='IBM WebSphere Application Server V8.5_2'
installLocation='C:\Program Files\IBM\WebSphere\AppServer_2'>
- Replace
<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer'/>
with<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer_2'/>
- Replace
<offering id='com.ibm.websphere.ND.v85'
profile='IBM WebSphere Application Server V8.5'
features='core.feature,ejbdeploy,thinclient,embeddablecontainer,com.ibm.sdk.6_32bit,liberty' installFixes='none'/>
with<offering id='com.ibm.websphere.ND.v85'
profile='IBM WebSphere Application Server V8.5_2'
features='core.feature,ejbdeploy,thinclient,embeddablecontainer,com.ibm.sdk.6_32bit,liberty' installFixes='none'/>
- To add the optional features, add each desired feature in the
offering as an entry in a comma-separated list. For example, to install
all of the optional features (except for
the optional IBM Software Development Kit on 64-bit systems):
Replace
<offering id='com.ibm.websphere.ND.v85'
profile='IBM WebSphere Application Server V8.5'
features='core.feature' installFixes='none'/>
with
<offering id='com.ibm.websphere.ND.v85'
profile='IBM WebSphere Application Server V8.5'
features='core.feature,samples,ejbdeploy,thinclient,embeddablecontainer,liberty' installFixes='none'/>
where:- core.feature indicates the full WebSphere Application
Server profile
- samples indicates the sample applications feature
- thinclient indicates the standalone thin clients
and resource adapters
- embeddablecontainer indicates the embeddable
EJB container
- ejbdeploy indicates the EJBDeploy tool for pre-EJB
3.0 modules
- liberty indicates the
Liberty profile
![[AIX]](../images/aixlogo.gif)
![[Linux]](../images/linux.gif)
![[Solaris]](../images/solaris.gif)
com.ibm.sdk.6_32bit allows
you to choose a 32-bit Software Development Kit if you are installing
on a 64-bit system
![[AIX]](../images/aixlogo.gif)
![[Linux]](../images/linux.gif)
![[Solaris]](../images/solaris.gif)
com.ibm.sdk.6_64bit allows
you to choose a 64-bit Software Development Kit if you are installing
on a 64-bit system
Notes: - The features samples, thinclient, embeddablecontainer,
and ejbdeploy are subfeatures of core.feature.
- If no features are specified, the default features (core.feature, ejbdeploy, thinclient,
and embeddablecontainer) are installed. To install
only the features that you want, specify the list of features explicitly.
- You must install core.feature, liberty (Liberty profile),
or both.
- You cannot use the Installation Manager
modify, update, or rollback functions to modify this installation
later and add or remove core.feature (full WebSphere
Application Server profile) or liberty (Liberty profile).
You can use these functions to add or remove the ejbdeploy, thinclient, embeddablecontainer,
or samples subfeatures of core.feature later.
- You cannot upgrade from a trial or Express
edition and add or remove core.feature (full WebSphere
Application Server profile) or liberty (Liberty profile).
- 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 Version 1.6 Information Center or the IBM Installation
Manager Version 1.5 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.
What to do next
You can create a standalone application server profile, management
profile, managed (custom) profile, cell profile, or secure proxy profile using
the Profile Management Tool or the manageprofiles command.