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.

Why and when to perform this task

[5.0 only]Use this procedure to perform a silent installation of the Enterprise 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 you must customize.

Steps for this task

  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, you must 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.



    [5.0 only]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 WAS.PME.install.log file that it has not opened yet. Or, you might see messages in the WAS.PME.install.log 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. [5.0 only]Copy the response file as myoptionsfile to your disk drive and customize it, as described in Customizing the Enterprise options response file.

    There are three types of silent installation:

    • Extending an existing installation of the base WebSphere Application Server product
    • Extending an existing installation of the Network Deployment product
    • Installing and extending the base WebSphere Application Server product

    Copy the setup.response file to install the Enterprise product on a machine that has no existing product or that already has the base WebSphere Application Server product.

    Copy the setup_nd.response file to install the Enterprise product on a machine that already has the Network Deployment product.

  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

    [5.0 only]The WAS.PME.install.log 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

    [5.0 only]The WAS.PME.install.log 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

[5.0 only]You can install silently using the response file. If you are doing an umbrella installation of the base WebSphere Application Server product, examine the log.txt file for a line similar to this:

MessageAction, msg1, The WebSphere 5.1 install is complete.
This message is an indicator that you have successfully installed the base product. Examine the WAS.PME.install.log file for a line similar to this:
The InstallShield Wizard has successfully installed
     IBM WebSphere Application Server Enterprise.
This is an indicator that you have successfully installed the Enterprise product.

What to do next

Return to Installing the product to continue.


Related tasks
Customizing the Enterprise options response file[5.0 only]
Related reference
setup.response
setup_nd.response



Searchable topic ID:   tins_runSilent
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tins_runSilent.html

Library | Support | Terms of Use | Feedback