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 IBM i prerequisites for more information.
See Installing WebSphere Application Server for IBM i 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"
SDK | Response file option |
---|---|
IBM® Technology for JDK 6 - 32 bit (5722-JV1 or 5761JV1 option 11) | -OPT i5osjdklocation="/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit" |
IBM Technology for JDK 6 - 64 bit (5722-JV1 or 5761JV1 option 12) | -OPT i5osjdklocation="/QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit" |
IBM Developer Kit for Java 1.6 (5722-JV1 or 5761JV1 option 10) | -OPT i5osjdklocation="/QIBM/ProdData/Java400/jdk6" |
If no SDK is specified, IBM Technology for JDK 6 - 32 bit will be selected by default if it is installed. If IBM Technology for JDK 6 - 32 bit is not installed, IBM Technology for JDK 6 - 64 bit will be selected. If IBM Technology for JDK 6 - 32 bit and IBM Technology for JDK 6 - 64 bit are not installed, IBM Developer Kit for Java 1.6 will be selected. If no valid SDKs are installed, the installation will fail.
Response file value | Description |
---|---|
upgrade | Upgrades a trial edition to a licensed edition, or upgrades Express edition to Base edition. |
Response file value | Description |
---|---|
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. |
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 |
---|---|
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. |
-OPT defaultProfileLocation="/QIBM/UserData/WebSphere/AppServer/V7/<edition>"
-OPT allowOverrideProfileLocation="true"
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.