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.
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"
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"
The installer checks the system for prerequisites by default.
-OPT disableOSPrereqChecking="true"
-OPT disableNonBlockingPrereqChecking="true"
-OPT checkFilePermissions="true"
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. |
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:
|
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:
|
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.![]() |
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. |
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=
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.