WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Silently installing a CIP for WebSphere Extended Deployment

You can silently install a customized installation package (CIP) for the product by using either a fully-qualified response file, which you configure specifically to your needs, or parameters that pass to the command line. With a silent installation, you can bypass the Installation wizard, which is useful in some environments.

Before you begin

To perform a silent installation, you must have the appropriate authority. On a Linux or UNIX operating system, you must be authorized as the root user. On a Windows operating system, your user ID must belong to the Administrator group and have the following advanced user rights: If you create a new user ID on a Windows operating system, restart the system before attempting a silent installation.

Create the build definition file and the CIP before you silently install the CIP.

To create a customized installation package using the IBM Installation Factory for WebSphere Extended Deployment 6.0.1, you must first install the IBM Installation Factory for WebSphere Application Server 6.0.2. To create a customized installation package using the IBM Installation Factory for WebSphere Extended Deployment 6.0.2, you must first install the IBM Installation Factory for WebSphere Application Server 6.0.2.

About this task

A silent installation uses the same installation program that the graphical user interface (GUI) version uses. However, instead of displaying a wizard interface, the silent installation reads all of your responses from a file that you customize, or from parameters that you pass to the command line. You can use either method to silently install the product. The silent and command-line installations accept a series of parameters. For further details, learn about the specific installation arguments.

Procedure

  1. Optional: If you choose to install the CIP by launching the options response file, first customize the file.
    1. Copy the response file, xdsetup.response.txt, from the product CD to your disk drive. Rename and save the file as myoptionsfile.txt. The xdsetup.response exists only if the Extended Deployment feature is included in the package. Similarly, the response file xd_mixedserver.response exists only if Mixed Server environment features are included in the package.
    2. Open and edit the response file in the text editor of your choice. The file includes comments to assist the configuration process and must include these parameters:
      • The license agreement
      • The location of the product installation
      • The list of profiles to augment
      • The location of the centralized installation manager repository
      Tip: The location that you select for your installation is how the installation program determines where your previous WebSphere Application Server instance is located. If you install on a node with multiple WebSphere Application Server instances, clearly define your location.
    3. Issue the proper command to launch your customized response file. Substitute the name and correct path of your response file if you renamed the file to something other than the provided example.
      • [For Windows operating system] install.bat -options C:\drive_path\myoptionsfile.txt -silent
      • [For Linux operating system] [For Unix operating system] ./install -options /absolute_path/myoptionsfile.txt -silent

      The log file is WAS.XD.install.log.

  2. Optional: If you choose to install the CIP by passing certain parameters to the command line, issue the following command to launch the installation:
    • [For Windows operating system] install.bat -silent -P silentInstallLicenseAcceptance.value=true -W installLocation=installation_location

      where installation_location is an existing WebSphere Application Server Network Deployment installation location.

      You can use the following optional parameters to specify particular profiles to augment:

      -W profileaugmentinputInstallWizardBean.profileNameList=profiles_separated_by_commas

    • [For Linux operating system] [For Unix operating system] ./install -silent -P silentInstallLicenseAcceptance.value=true -W installLocation=installation_location

      where installation_location is an existing WebSphere Application Server Network Deployment installation location.

      You can use the following optional parameters to specify particular profiles to augment:

      -W profileaugmentinputInstallWizardBean.profileNameList=profiles_separated_by_commas

  3. Review the resulting logs for errors or an installation failure.

Results

You silently installed the customized installation package (CIP).

What to do next

Create a new profile, or augment an existing profile by using the WebSphere Extended Deployment Profile wizard . You can omit this task if you augmented the profile through the Installation wizard.



Related concepts
Build definition file
Related tasks
Creating a build definition file to generate a CIP
Creating profiles
Planning the installation
Installing the product
Related reference
Installation arguments
Task topic    

Terms of Use | Feedback

Last updated: Nov 30, 2007 3:57:26 PM EST
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/install/tifcipsilent.html