Install WAS using Installation Manager response files

WAS v8.0 > Install the application serving environment > Distributed operating systems > Install the product > Install and uninstall the product

Install WAS using Installation Manager response files

Install Installation Manager on each of the systems onto which we will install WebSphere Application Server.

Use the Installation Manager included with WAS v8
Obtain the necessary files from the physical media or the web.
There are three basic options for obtaining and installing the product.
Access the physical media, and use local installation
You can access the product repositories on the product media.

Install Installation Manager on the system.
We can install Installation Manager using the product media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.
Use Installation Manager to install the product from the product repositories on the media.

Download the files from the Passport Advantage site, and use local installation
Licensed customers with a Passport Advantage ID and password can download the necessary product repositories from the Passport Advantage site.

Download the files from the Passport Advantage site.
Tip: See How to download WAS V8.0 from Passport Advantage Online for a list of the IBM WebSphere Application Server v8.0 installation images downloadable from the IBM Passport Advantage Online website and other information.
Install Installation Manager on the system.
We can install Installation Manager using the product media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.
Use Installation Manager to install the product from the downloaded repositories.
Access the live repositories, and use web-based installation
If we have a Passport Advantage ID and password, you can install the product from the web-based repositories.
Install Installation Manager on the system.
We can install Installation Manager using the product media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.
Use Installation Manager to install the product from the web-based repository located at
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v80
This location does not contain a web page that you can access using a web browser. This is a remote web-based repository location that specify in the response file so that the installation can access the files in this repository.
Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date installation files.
Notes:

If you do not have a Passport Advantage ID and password, install the product from the product repositories on the media or local repositories.
With the Packaging Utility, you can create and manage packages for installation repositories. We can copy multiple packages into one repository or copy multiple disks for one product into a repository. We can copy packages from Passport Advantage or a web-based repository into a local repository for example. For more information on the Packaging Utility, go to the IBM Installation Manager v1.4 Information Center.
Change to the location containing the Installation Manager installation files, and run one of the following commands to install Installation Manager:

Administrative installation:

installc.exe -acceptLicense -log log_file_path_and_name
./installc -acceptLicense -log log_file_path_and_name

Non-administrative installation:

userinstc.exe -acceptLicense -log log_file_path_and_name
./userinstc -acceptLicense -log log_file_path_and_name

Group-mode installation:

./groupinstc -acceptLicense -dataLocation application_data_location -log log_file_path_and_name
Notes on group mode:

Group mode allows multiple users to use a single instance of IBM Installation Manager to manage software packages.
This does not mean that two people can use the single instance of IBM Installation Manager at the same time.
Group mode is not available on Windows operating systems.

If you do not install Installation Manager using group mode, you will not be able to use group mode to manage any of the products that you install later using this Installation Manager.
Make sure that you change the installation location from the default location in the current user's home directory to a location that is accessible by all users in the group.
Set up your groups, permissions, and environment variables as described in the Group mode road maps in the IBM Installation Manager v1.4 Information Center before installing in group mode.
For more information on using group mode, read the Group mode road maps in the IBM Installation Manager v1.4 Information Center.
If you already have a version of Installation Manager installed on the system

If you already have a version of Installation Manager installed on the system and to use it to install and maintain the product, obtain the necessary product files from the physical media or the web.
There are three basic options for installing the product.
Access the physical media, and use local installation
You can access the product repositories on the product media. Use Installation Manager to install the product from the product repositories on the media.
Download the files from the Passport Advantage site, and use local installation
Licensed customers with a Passport Advantage ID and password can download the necessary product repositories from the Passport Advantage site.

Download the product repositories from the Passport Advantage site.
Tip: See How to download WAS V8.0 from Passport Advantage Online for a list of the IBM WebSphere Application Server v8.0 installation images downloadable from the IBM Passport Advantage Online website and other information.
Use Installation Manager to install the product from the downloaded repositories.
Access the live repositories, and use web-based installation
If we have a Passport Advantage ID and password, you can use Installation Manager to install the product from the web-based repositories. Use Installation Manager to install the product from the web-based repository located at
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v80
This location does not contain a web page that you can access using a web browser. This is a remote web-based repository location that specify in the response file so that the installation can access the files in this repository.
Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date installation files.
Notes:

If you do not have a Passport Advantage ID and password, install the product from the product repositories on the media or local repositories.
With the Packaging Utility, you can create and manage packages for installation repositories. We can copy multiple packages into one repository or copy multiple disks for one product into a repository. We can copy packages from Passport Advantage or a web-based repository into a local repository for example. For more information on the Packaging Utility, go to the IBM Installation Manager v1.4 Information Center.
Add the product repository to your Installation Manager preferences.
Start Installation Manager.
In the top menu, click File > Preferences.

Select Repositories.
Perform the following actions:
Click Add Repository.
Enter the path to the repository.config file in the location containing the repository files.
For example:

C:\repositories\product_name\local-repositories
/var/repositories/product_name/local-repositories

or
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v80
Click OK.
Deselect any locations listed in the Repositories window that you will not be using.

Click Apply.

Click OK.

Click File > Exit to close Installation Manager.
Use Installation Manager, you can work with response files to install the product in a variety of ways. We 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 the 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.
For example:
Administrator or non-administrator:
IBMIM.exe -skipInstall "C:\temp\imRegistry"
  -record C:\temp\install_response_file.xml
Administrator:
./IBMIM -skipInstall /var/temp/imRegistry
  -record /var/temp/install_response_file.xml
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 re-use that location for future recording sessions.

For more information, read the IBM Installation Manager v1.4 Information Center.
Add the appropriate repositories to your Installation Manager preferences.
In the top menu, click File > Preferences.

Select Repositories.
Perform the following actions for each repository:
Click Add Repository.
Enter the path to the repository.config file in the remote web-based repository or the local directory into which you unpacked the repository files.
For example:
Remote repositories:
https://downloads.mycorp.com:8080/WAS_80_repository
or
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v80
Local repositories:

C:\repositories\was80\local-repositories
/var/repositories/was80/local-repositories
Click OK.
Click Apply.

Click OK.
Click Install.
If you are prompted to authenticate, use the IBM ID and password that you registered with on the program website.
Installation Manager searches its defined repositories for available packages.
Perform the following actions.

Select IBM WAS Network Deployment and the appropriate version.
New feature: New feature: If you are installing the trial version of this product, select IBM WAS Network Deployment Trial.New feature:
If you already have the product installed on a WAS installation on the system, a message displays indicating that the product is already installed.
To create another installation of the product in another location, click Continue.
Tip: If the Search service repositories during installation and updates option is selected on the Installation Manager Repository preference page and you are connected to the Internet, you can click Check for Other Versions and Extensions to search for updates in the default update repositories for the selected packages. In this case, you do not need to add the specific service-repository URL to the Installation Manager Repository preference page.

Select the fixes to install.
Any recommended fixes are selected by default.
If there are recommended fixes, you can select the option to show only recommended fixes and hide non-recommended fixes.

Click Next.

Accept the terms in the license agreements, and click Next.

Specify the installation root directory for the product binaries, which are also referred to as the core product files or system files.
The panel also displays the shared resources directory and disk-space information.
The first time that you install a package using Installation Manager, specify the shared resources directory. The shared resources directory is where installation artifacts are located that can be used by one or more package groups. Use your largest drive for this installation. We cannot change the directory location until after you uninstall all packages.
Restrictions:

Delete the default target location and leaving an installation-directory field empty prevents you from continuing.
Do not use symbolic links as the destination directory.
Symbolic links are not supported.
Do not use a semicolon in the directory name.
WAS cannot install properly if the target directory includes a semicolon.
A semicolon is the character used to construct the class path on Windows systems.
The maximum path length on the Windows Server 2008, Windows Vista, and Windows 7 operating systems is 60 characters.

Click Next.

Select the languages for which translated content should be installed.
English is always selected.

Click Next.

Select the features to install.
Choose from the following features:

EJBDeploy tool for pre-EJB 3.0 modules
This option installs the EJBDeploy tool for pre-EJB 3.0 modules.
For transitioning users: The EJBDeploy tool was installed automatically with the product in WAS v7 and earlier. It is now an optional feature.trns
Before you deploy applications on the server, run the EJBDeploy tool on applications that contain EJB modules that are based on specifications prior to EJB 3.0. Running the EJBDeploy tool generates deployment code for enterprise beans in the application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer required because WAS uses a new feature called "JITDeploy", which automatically generates code when the application starts.
Tip: Unexpected errors might occur if applications that are provided with IBM WebSphere Application Server, such as the samples, require the optional EJBDeploy tool for pre-EJB 3.0 modules but the feature is not installed. If you deploy and use applications that might require pre-EJB 3.0 modules, include the optional EJBDeploy feature in all WAS installations that will be used by servers running the pre-EJB 3.0 applications.
Tip: We can run the Installation Manager later to modify this installation and add or remove this feature.
Standalone thin clients, resource adapters, and embeddable containers
IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, you can use the embeddable EJB container to run enterprise beans outside the application server.

Standalone thin clients and resource adapters
This option installs the IBM standalone thin clients and resource adapters.
IBM thin clients provide a set of clients for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. IBM resource adapters provide the resource adapters for JMS.
New feature: Embeddable EJB container
This option installs the embeddable EJB container.
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 environment. We 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.

Tip: We can run the Installation Manager later to modify this installation and add or remove these features.
Sample applications
This option installs the sample applications for learning and demonstration environments.
The samples include both source code files and integrated enterprise applications that demonstrate some of the latest Java (TM) Platform, Enterprise Edition (Java EE) and WebSphere technologies. The samples are recommended for installation to learning and demonstration environments, such as development environments. However, they are not recommended for installation to production application server environments.
Tip: We can run the Installation Manager later to modify this installation and add or remove this feature.
IBM Software Development Kit
This option allows you to choose between a 32-bit and 64-bit Software Development Kit.
Notes:

This option displays only if you are installing on a 64-bit system.
This does not apply to Solaris x86 64-bit systems.
We must select one of the two options.
You cannot modify this installation later and change this selection.

Click Next.
Review the summary information, and click Install.

If the installation is successful, the program displays a message indicating that installation is successful.
The program might also display important post-installation instructions as well.

If the installation is not successful, click View Log File to troubleshoot the problem.

Click Finish.

Click File > Exit to close Installation Manager.
Optional: If you are using an authenticated remote repository, create a keyring file for installation.
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.
For example:
Administrator or non-administrator:
IBMIM.exe -skipInstall "C:\temp\imRegistry"
  -keyring C:\IM\im.keyring
  -record C:\temp\keyring_response_file.xml
Administrator:
./IBMIM -skipInstall /var/temp/imRegistry
  -keyring /var/IM/im.keyring
  -record /var/temp/keyring_response_file.xml
Non-administrator:
./IBMIM -skipInstall user_home/var/temp/imRegistry
  -keyring user_home/var/IM/im.keyring
  -record user_home/var/temp/keyring_response_file.xml
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, read the IBM Installation Manager v1.4 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 to install the product, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the keyring file.
For example:
Administrator or non-administrator:
imcl.exe -acceptLicense
  input C:\temp\keyring_response_file.xml
  -log C:\temp\keyring_log.xml
Administrator:
./imcl -acceptLicense
  input /var/temp/keyring_response_file.xml
  -log /var/temp/keyring_log.xml
Non-administrator:
./imcl -acceptLicense
  input user_home/var/temp/keyring_response_file.xml
  -log user_home/var/temp/keyring_log.xml
For more information on keyring files, read the IBM Installation Manager v1.4 Information Center.
Use the response file to install the product: Go to a command line on each of the systems on which to install the product, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the product.
For example:
Administrator or non-administrator:
imcl.exe -acceptLicense
  input C:\temp\install_response_file.xml
  -log C:\temp\install_log.xml
  -keyring C:\IM\im.keyring
Administrator:
./imcl -acceptLicense
  input /var/temp/install_response_file.xml
  -log /var/temp/install_log.xml
  -keyring /var/IM/im.keyring
Non-administrator:
./imcl -acceptLicense
  input user_home/var/temp/install_response_file.xml
  -log user_home/var/temp/install_log.xml
  -keyring user_home/var/IM/im.keyring
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 v1.4 Information Center for more information.
Example

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.v80" />

</server>
<install modify='false'>
<offering id='com.ibm.websphere.ND.v80'
  profile='IBM WAS Network Deployment V8.0'
  features='core.feature,ejbdeploy,thinclient,embeddablecontainer,com.ibm.sdk.6_32bit' installFixes='none'/>
</install>
<profile id='IBM WAS Network Deployment V8.0'
  installLocation='C:\IBM\WebSphere\AppServer'>
<data key='eclipseLocation' value='C:\IBM\WebSphere\AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='en'/>
</profile>
</agent-input> 
Tip: See Sample response file: Installing IBM WAS Network Deployment for an annotated sample of a response file for performing this procedure.
Important: If you are installing on a 64-bit system, include one of the options for an IBM Software Development Kit.
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 WAS Network Deployment V8.0'
    features='core.feature,com.ibm.sdk.6_32bit' id='com.ibm.websphere.ND.v80'/> 
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 WAS Network Deployment V8.0'
    features='core.feature,com.ibm.sdk.6_64bit' id='com.ibm.websphere.ND.v80'/> 
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.
We 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.

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'/>
We can find more details on silent preference keys in the IBM Installation Manager v1.4 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 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 WAS Network Deployment V8.0_2 package group:
Replace
<profile id='IBM WAS Network Deployment V8.0'
  installLocation='C:\IBM\WebSphere\AppServer'> 
with
<profile id='IBM WAS Network Deployment V8.0_2
  installLocation='C:\IBM\WebSphere\AppServer_2
Replace
<data key='eclipseLocation' value='C:\IBM\WebSphere\AppServer'/> 
with
<data key='eclipseLocation' value='C:\IBM\WebSphere\AppServer_2'/> 
Replace
<offering id='com.ibm.websphere.ND.v80'
  profile='IBM WAS Network Deployment V8.0'
  features='core.feature,com.ibm.sdk.6_32bit,ejbdeploy,thinclient,embeddablecontainer' installFixes='none'/> 
with
<offering id='com.ibm.websphere.ND.v80'
  profile='IBM WAS Network Deployment V8.0_2'
  features='core.feature,com.ibm.sdk.6_32bit,ejbdeploy,thinclient,embeddablecontainer' 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.v80'
  profile='IBM WAS Network Deployment V8.0'
  features='core.feature' installFixes='none'/> 
with
<offering id='com.ibm.websphere.ND.v80'
  profile='IBM WAS Network Deployment V8.0'
  features='core.feature,samples,ejbdeploy,thinclient,embeddablecontainer' installFixes='none'/> 
where samples indicates the sample applications feature, thinclient indicates the standalone thin clients and resource adapters, embeddablecontainer indicates the embeddable EJB container, and ejbdeploy indicates the EJBDeploy tool for pre-EJB 3.0 modules.
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 v1.4 Information Center.
What to do next

We 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.
Install and uninstall the product
Install and uninstall features
Install and uninstall interim fixes and fix packs
Upgrade from a trial offering using the GUI
Uninstall the product from distributed operating systems using the GUI
Uninstall the product from distributed operating systems using response files

+
Search Tips | Advanced Search