[V5.1 and later]Installing silently

This topic describes how to perform a silent installation of the product as the root user on a Linux or UNIX-based operating system, or from a user ID that belongs to the Administrator group on a Windows platform.

 

Overview

Use this procedure to perform a silent installation of the WebSphere Application Server Network Deployment product.

A silent installation uses the installation program to install the product. However, instead of displaying a wizard interface, the silent installation causes the installation program to read all of your responses from a file that customize.

  1. Verify that the user ID has sufficient authority to perform the task.

    Install silently as root on a Linux or UNIX-based platform, or as a user that belongs to the administrator group on a Windows platform. Some steps for installing silently on a Windows platform require the administrator group user to have the following advanced user rights:

    • Act as part of the operating system

    • Log on as a service

    The installation wizard grants your Windows user ID the advanced user rights, if the user ID belongs to the administrator group. The silent installation does not grant these rights. If you create a new user ID on a Windows platform to perform the silent installation, restart the system to activate the proper authorizations for the user ID, before you can perform a successful silent installation.


    Installation tip

    Operating platform Tip in Platform-specific tips for installing and migrating
    Windows platforms A Windows user ID with spaces cannot be validated for installing services.


    If you attempt a silent installation of services or the embedded messaging feature without the required authorizations, the installation might fail while attempting to write to a log.txt file that it has not opened yet. Or, you might see messages in the log.txt file that are similar to the following messages:

    (Jan 30, 2003 12:04:32 PM), Setup.product.install,
com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1,
higherVersionFoundPasses: false
(Jan 30, 2003 12:04:32 PM), Setup.product.install,
com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1,
defaultEvalResult: false
(Jan 30, 2003 12:04:32 PM), Setup.product.install,
com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1,
checkOnlyCurrentVersion: true
(Jan 30, 2003 12:04:34 PM), Setup.product.install,
com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1,
higherVersionFoundPasses: false
(Jan 30, 2003 12:04:34 PM), Setup.product.install,
com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1,
defaultEvalResult: false
(Jan 30, 2003 12:04:34 PM), Setup.product.install,
com.ibm.ws.install.conditions.PCWebSphereCheckCondition, msg1,
checkOnlyCurrentVersion: false
(Jan 30, 2003 12:04:41 PM), Setup.product.install,
com.ibm.ws.install.actions.LogMessageAction, msg1, INST0058E:
The install failed or did not complete due to one or more errors.

  2. Copy the response file as myoptionsfile to your disk drive and customize it, as described in Customizing the Network Deployment options response file.

    The name of the original file is responsefile.

  3. Issue one of these commands to use your custom response file:

    Windows platforms

    "fully_qualified_CD_drive_D:\win\install" -options "fully_qualified_disk_drive_C:_WAS\myoptionsfile

    The log.txt file is in the install_root\logs directory.

    Linux and UNIX-based platforms

    fully_qualified_mnt_cdrom/install -options fully_qualified_disk_drive_/tmp/WAS/myoptionsfile

    The log.txt file is in the install_root/logs directory.

    You can find the sample options response file in the operating-system platform directory on the product CD.

  4. Reboot your machine in response to the prompt that might appear on Windows platforms.

    If you install the embedded messaging feature, -P mqSeriesBean.active="true", certain conditions, such as a locked file, might require you to reboot. You have the option of rebooting immediately, after which the installation program resumes the installation at the point it left off. You can also defer rebooting to a convenient time, such as after the overall installation is complete.

 

Results

You can install silently using the response file. Examine the log.txt file for lines similar to these: 

com.ibm.ws.install.actions.WSAdminInstallEarsAction, msg1,
  Installing ear with:           
    util\launcher.exe
       "C:\WebSphere\DeploymentManager\bin\wsadmin.bat"
       -conntype NONE
       -c "$AdminApp install \\"C:/WebSphere/DeploymentManager/
          installableApps/adminconsole.ear\\
          "{
             -node NodeName
             -cell CellName
             -server dmgr
             -copy.sessionmgr.servername dmgr
             -appname adminconsole
          }"
This is an indicator that you have successfully installed the product.

 

What to do next

Return to Installing the product to continue.

Related tasks
Customizing the Network Deployment options response file
Related reference
responsefile