Install an IIP silently

Install an integrated installation package (IIP) silently refers to installing the IIP from the command line without the use of the IIP installation wizard. Included installation contributions might not install silently based on contribution settings.

Use the Installation Factory to create an IIP before we can install the IIP. See for more information about creating an IIP.

The IIP installation wizard can be suppressed altogether so that it does not display when the IIP is run. The contribution invocations will be invoked using the built-in options that were specified by the installation factory user when the IIP was created, or using options specified on the IIP command line which will override the built-in ones (assuming the IIP creator did not disallow them to be overridden). It is important to note that although the IIP wizard will not display, each contribution in the IIP may or may not display independently based on the options you selected during IIP creation. In this case a true silent installation of an IIP means that there is neither an IIP installation wizard nor any contribution installation wizards.

We can query the status and progress of an appserver contribution in the IIP through the use of a new API. See for more information.

Use this procedure to perform a silent installation of WAS ND.


  1. Log on to the operating system. If installing as a non-root or non-administrative user, then there are certain limitations.




    [Solaris] <p> In addition, select a umask that allows the owner to read/write to the files, and allows others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users, a umask of 002 or 022 could be used, depending on whether or not the users share the group. To verify the umask setting, issue the following command:

    To set the umask setting to 022, issue the following command:
    umask 022

    [Windows] <p> When installing as an administrative user on a Windows operating system, a Windows service is automatically created to autostart the appserver. The installer user account must have the following advanced user rights:

    • Act as part of the operating system

    • Log on as a service

    For example, on some Windows operating systems, click Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignments to set the advanced options. See the Windows operating system documentation for more information.

    [Windows] <p> If you plan to run the appserver as a Windows service, do not install from a user ID that contains spaces. A user ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To work around this restriction, install with a user ID that does not contain spaces.

  2. If you want an end-to-end silent installation, make sure that we have configured all of the contributions to run silently.

    See for details on how to configure the various installation options of a contribution. You may also generate an IIP so that it installs in a mixed mode, with some contributions installing through their wizards and some installing silently. For example, we can include a contribution to install WAS to be installed through the wizard, and then install a feature pack contribution silently for a seamless installation.

  3. We can install the IIP silently by running the install command with the parameters listed in Table 1. Specify the -iipNoGUI parameter if you want to install silently, otherwise the installation wizard will be displayed. The install command is located at:

    Note that a contribution can be invoked with a combination of options specified directly on its command line as well as options specified in a response file. See for more information. However, any contribution options passed to the command line will cause the IIP installer to ignore all options specified in a specific contribution's response file. For example, during IIP creation we can specify the install location for a contribution and the user installing the IIP can also specify it in a response file. The install location specified directly on the command line will override the one set during IIP creation when the contribution is invoked and processes its options. In addition, any other options specified for that contribution during IIP creation will be subsequently ignored.

    The following options are available during installation. All options values containing spaces must be surrounded by single quotes. The options that can only be used on the command line have been noted.

    Table 1. IIP installation options
    Option Value Description Example


    [Windows] <p> -?

      Displays all available parameters for the IIP install command. This option can only be used on the command line. -help
    -iipResponseFile <path to IIP response file>

    Specifies location of the response file. Any option that can be specified on the command line when invoking the IIP can also be specified in an IIP response file (except the –iipResponseFile option itself). This includes the top-level IIP options described in this section as well as contribution-specific options. The order of the options in the response file is significant. Top-level options supported directly by the IIP UI must be first, and the options for the “primary” contribution (if any) must be second. Options for other contributions (if any) must follow, separated by –iipOptionSet options. Any line in the response file that begins with a ‘#’ is considered a comment and will be ignored.

    See for more information on the sample response file and its use. This option can only be used on the command line.

    -iipLogfile <path to log file> Directory path and name of the IIP log file -iipLogfile=C:\mylog.txt

    • all

    • config

    • info

    • error

    • warning

    • severe

    • off

    Verbosity of the log file. The default value is info. –iipLogLevel=info
    -iipTracefile <path to trace file> Directory path and name of the trace file -iipTracefile=C:\mytrace.xml

    • all

    • fine

    • finer

    • finest

    • off

    Verbosity of the trace file. The default value is off. –iipTracelevel=fine
    -iipNoGUI   Run the IIP without showing the IIP GUI. When the IIP is created, the IF user can specify that the IIP GUI should be displayed by default. This option can be specified by the IIP user to override that default. However, the IF user can also specify that this cannot be overridden, in which case using this option will result in an error. This option is intentionally not named “-silent” since it does not control whether or not the contributions in the IIP run in silent mode – that depends on the options specified for those contribution invocations. Using the name “-iipNoGUI” helps reinforce this. -iipNoGUI
    -iipShowGUI   Show the IIP GUI when the IIP is invoked. When the IIP is created, the IF user can specify that the IIP GUI should not be displayed by default. This option can be specified by the IIP user to override that default. However, the IF user can also specify that this cannot be overridden, in which case using this option will result in an error.

    Using this option will result in an error on an operating system where the GUI installer is not supported.

    -iipUserType <root or nonroot> Whether user is root or nonroot This is an important setting since the IIP creator can different option values to pass to the contribution based on the IIP installer user type. The default value is root. -iipUserType=nonroot
    -iipOptionSet <Invocation_ID>

    Refers to a specific contribution invocation. All subsequent options are assumed to be intended for the specified contribution, until another -iipOptionSet option is specified.

    Any options specified at IIP installation which are not preceded by the -iipOptionSetoption are assumed to belong to the primary contribution invocation. The invocation of the IIP will be virtually identical to the primary contribution invocation in terms of the option names and syntax.

    All contribution options will be ignored if the IIP is installed in GUI mode.

    –iipOptionSet=6.1.0-WS-WASBase_1-1 –OPT installLocation=C:\myLocation
    -iipDisable <Invocation_ID1, Invocation_ID2,...> Do not install the specified contributions during IIP installation. When the IIP is created, the user can specify which contributions should be suppressed by default when the IIP is installed, and whether this can be overridden. Using this option during install will result in an error if the IIP creator specified that suppression cannot be overridden. The IDs are comma-delimited. –iipDisable=6.1.0-WS-WASBase_1-1, 6.1.0-WS-WASBase_1-2

  4. After the installation, we can review the log and/or trace files for the IIP and also for each individual contribution. Please see that product's documentation for more logging information. The IIP log and trace files will default to the below location unless you specified another path using the -iipLogfile or -iipTrace parameters.



we have silently installed an integrated installation package.



The following is an example of a silent installation of a WAS ND Version 7.0 package. The IIP installer will launch silently using the specified response file, and install the ND contribution silently into the specified directory. The sample response file might have been edited to include different log and trace locations as well as other parameters. Note that since the installation location was specified for the contribution, all other options previously specified for the contribution will be ignored.
install -iipNoGUI -iipOptionSet=7.0.0-WS-WASND_1-1 -OPT installLocation='C:\Program Files\IBM\WebSphere\AppServer'
 -options D:\WAS\responseFile.txt -silent

  • Make sure that specify the -silent parameter only once for an invocation; otherwise, the installation fails. In above example, you should make sure that no -silent spec exists in the D:\WAS\responseFile.txt file before running the command.

  • If creating a cell profile during the installation, make sure that you specify port files, specify starting ports, or instruct the installer to use default ports. These are standard options in the response file.


Next steps

If an included contribution fails to install, we might need to edit that contribution's response file, which is different from the overall IIP response file. By default, contribution response files are located in IIP_home/ResponseFiles.

During IIP installation, workspace files that might contain crucial logging information from Eclipse are created in the following directory:

  • [Windows] <p> %USERPROFILE%\

  • [AIX]



    [Solaris] <p> $HOME/

We might want to manually delete these files periodically to free up disk space.


Related concepts

Related tasks

[AIX Solaris HP-UX Linux Windows]


Last updated Nov 11, 2010 1:01:09 PM CST