Customizing installation response files

To configure a silent installation of the product, change the options in the silent response file before you issue the install command. Silent installation mode does not accept interactive installation options on the command line. To specify nondefault options during a silent installation, you must use the response file. The installation program reads this file to determine installation option values when you install silently.

Verify that you have met the operating system prerequisites for the product. See Preparing the operating system for product installation for more information.

See Installing silently for more information about installing silently using a response file.

Customization considerations

Descriptions of mandatory options follow.

License acceptance

To install silently, you must accept the license agreement in the agreement option which is set to false by default. Change the value of the silentInstallLicenseAcceptance option to true. A value of false prevents the installation from running.

-OPT silentInstallLicenseAcceptance="true"

Non-root installation

Installing as a non-root or non-administrator user results in certain limitations. You must also have write access to the target directory where you intend to install the product. The following actions cannot be performed as a non-root or non-administrative user:
  • Creation of a Windows® or Linux® service for WebSphere® Application Server
  • Native registration with the operating system
  • Port conflicts may occur with other installations of WebSphere Application Server that are not registered with the operating system

Uncomment the following option to accept the limitations and install the product as non-root or non-administrator user. Setting the value to false indicates that you do not agree with these limitations and you will be prevented from installing the product.

-OPT allowNonRootSilentInstall="true"

Prerequisite checking

The installer checks the system for prerequisites by default.

Uncomment the following option to notify the installer to continue with the installation and log the warnings even though prerequisite checking of the operating system failed.
-OPT disableOSPrereqChecking="true"
Uncomment the following option to notify the installer to continue with the installation and log the warnings even though prerequisite checking failed.
-OPT disableNonBlockingPrereqChecking="true"

File permission checking

The installer does not check whether the current user has sufficient file permissions to perform the installation. Uncomment the following option to verify that you have sufficient file permissions to successfully perform the installation. For more information, read the Verifying and setting file permissions topic.
-OPT checkFilePermissions="true"

Installation type

Use the -OPT installType="install_type" option to specify the installation type. You can only specify one type of installation.
Table 1. Installation types.

The following installation types are available:

Response file value Description
installNew Installs a new copy of the product.
addFeature Adds features to an existing installation.
upgrade Upgrades a trial edition to a licensed edition, or upgrades Express edition to Base edition.

Profile type

Create a profile during silent installation by specifying the -OPT profileType="profile_type" option. You must specify a profile type, and some profile types require additional options.
Table 2. Profile types.

The following profile types are available:

Response file value Description
cell Creates a cell with two profiles: a deployment manager and an application server node that is already federated into the deployment manager cell. This is useful for development environments.
management Creates a management profile that provides the servers and services necessary to manage your WebSphere environment.
You must also specify the type of management profile in the profiles section with the -OPT PROF_serverType option:
  • DEPLOYMENT_MANAGER (default)
  • JOB_MANAGER
  • ADMIN_AGENT
standAlone Creates a standalone application server profile.
custom Creates a custom profile which belongs to a deployment manager cell, to make applications available to the Internet or to an intranet under the management of the deployment manager. You must federate this node to use it.
secureProxy Creates a DMZ Secure Proxy Server for IBM® WebSphere Application Server which accepts requests from the internet and forwards them to application servers. The server resides in the DMZ.
none Does not create a profile during installation. However, if you specify none, then you must create a profile after installation to have an operational product.
You can create profiles after installation using the following tools:
  • The Profile Management Tool
  • The manageprofiles command

Features

You must specify the -OPT feature="feature_name" option for each feature you want to install, whether you are installing a new application server product or just adding features to an existing installation. Even if you are not installing any features, you must still specify -OPT feature="noFeature" or the installation will fail.
Table 3. Features.

The following profile types are valid values:

Response file value Description
noFeature Does not install any additional features. If you are not installing any features, then you must specify this value or the installation will fail.
samplesSelected Installs the samples applications for learning and demonstration environments. The samples are not recommended for installation on production environments.
Avoid trouble Avoid trouble: Specify a value for the -OPT PROF_samplesPassword option if you are enabling security. See the "Administrative security" section.gotcha
languagepack.console.all Installs all the non-English language files for using the administrative console from machines with non-English locales. If you do not select this option then only the English language pack is installed.
languagepack.server.all Installs all the non-English language files that support the application server runtime environment such as the wsadmin tool and logging. If you do not select this option then only the English language pack is installed.

Administrative security

Specify whether you want to enable administrative security. Turning on administrative security activates the settings that protect your server from unauthorized users. Administrative security is enabled by default during profile creation. There might be some environments where no security is needed such as a development system. On these systems you can elect to disable administrative security. However, in most environments you should keep unauthorized users from accessing the administrative console and your business applications. Administrative security must be enabled to restrict access. Set -OPT PROF_enableAdminSecurity to true or false, and specify a user name and password.

If you have chosen to install the samples applications and are enabling administrative security, then you must uncomment and specify a value for the -OPT PROF_samplesPassword option.

  -OPT PROF_enableAdminSecurity="true"
  -OPT PROF_adminUserName=
  -OPT PROF_adminPassword=
  -OPT PROF_samplesPassword=

Examples

The following response file examples demonstrate simple installation scenarios without any profile customization. Uncomment the listed options or change their values to match the examples. Read the Installing silently topic for silent installation command specifics
  • Example 1: New installation with a standalone profile with no features

    The following minimum options will create a new installation of the product that includes a standalone profile with no installed features. The user must be root or an administrative user. The directory value for installLocation is the default root user installation directory for an HP-UX, Linux, or Solaris machine.

    -OPT silentInstallLicenseAcceptance="true"
    -OPT installType="installNew"
    -OPT profileType="standAlone"
    -OPT feature="noFeature"
    -OPT PROF_enableAdminSecurity="false"
    -OPT installLocation="/opt/IBM/WebSphere/AppServer"
    
  • Example 2: New installation with a standalone profile with no features with administrative security enabled

    The following minimum options will create a new installation of the product that includes a standalone profile with no installed features and with administrative security enabled. The user must be root or an administrative user. The directory value for installLocation is the default root user installation directory for an HP-UX, Linux, or Solaris machine.

    -OPT silentInstallLicenseAcceptance="true"
    -OPT installType="installNew"
    -OPT profileType="standAlone"
    -OPT feature="noFeature"
    -OPT PROF_enableAdminSecurity="true"
    -OPT PROF_adminUserName="wasadmin"
    -OPT PROF_adminPassword="password"
    -OPT installLocation="/opt/IBM/WebSphere/AppServer"
    
  • Example 3: New non-root installation with a standalone profile with no features with administrative security enabled

    The following minimum options will create a new installation of the product that includes a standalone profile with no installed features and with administrative security enabled. The application server is installed by a non-root user. The directory value for installLocation is the default non-root user installation directory for an HP-UX, Linux, or Solaris machine, where user_home is the non-root user's home directory.

    -OPT silentInstallLicenseAcceptance="true"
    -OPT allowNonRootSilentInstall="true"
    -OPT installType="installNew"
    -OPT profileType="standAlone"
    -OPT feature="noFeature"
    -OPT PROF_enableAdminSecurity="true"
    -OPT PROF_adminUserName="wasadmin"
    -OPT PROF_adminPassword="password"
    -OPT installLocation="user_home/IBM/WebSphere/AppServer"
    

Profile creation details

The response file contains a full section of example options for each available profile type near the end of the file. You can use one of these profile examples in addition to the basic options previously reviewed to customize any profile that you create. Options include profile path, port value assignment, node, host, and cell names, and many other profile details.




Related concepts
Non-root installations
Related reference
install command

Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 11:43:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=rins_customize_responsefile
File name: rins_customize_responsefile.html