Installing WebSphere Application Server Network Deployment using silent installation refers to using a file to supply installation options without user interaction. To configure the installation, change the options in the response file before you issue the installation command.
This procedure also describes installing a CIP silently.
Before starting this installation, see the following topics:
The "Planning to install" diagrams show typical topologies for the product.
Ensure that the operating system for the machine has prerequisite software installed.
A silent installation uses the installation wizard to install the product in silent mode, without the graphical user interface. Instead of displaying a wizard interface, the silent installation causes the installation program to read all of your responses from a file that you provide. To specify non-default options during a silent installation, you must use the response file. To install silently, you must accept the license agreement in the agreement option.
The installation wizard and the Profile Creation wizard record installation events in the following log files:
Log | Content | Indicators |
---|---|---|
app_server_root/logs/log.txt | Logs all installation events | |
app_server_root/wasprofileprofile_name.log | ||
app_server_root/logs/wasprofile/wasprofile_delete_ profile_name.log | ||
profile_root/logs/pctLog.txt | Logs all profile creation events that occur when using the Profile Creation wizard | |
app_server_root\logs\instconfig.log (Not available on systems such as AIX or Linux) | Logs the activities of ANT configuration scripts that run at the end of the installation procedure. |
Log more information when InstallShield MultiPlatform (ISMP) cannot start the installation wizard.
Verify or troubleshoot the installation if the app_server_root/logs/log.txt file or the profile_root/logs/pctLog.txt file does not contain a record of a problem, but problems exist. If the profile_root directory exists, the pctLog.txt file is in the logs directory. If the error happens early in the installation, look for the logs in the system temporary area. The installation program copies the logs from the system temporary area to the logs directory at the end of the installation.
If the profile_root directory does not exist, the pctLog.txt file is in the USER_HOME directory and is named .$~pctLog.txt. Issue the env command to display the USER_HOME directory on operating systems such as AIX or Linux. See the environment variable settings on Windows system to display the value of the variable.
install -options fully_qualified_options_response_file_name -silent -log # !fully_qualified_log_file_name @ALL
install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt @ALL
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt @ALL
install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt @ALL
./install -is:javaconsole
install.exe -is:javaconsole
Ensure that you have at least 250 MB free in your temporary directory before attempting to install WebSphere Application Server.
The following examples show how to use the -log parameter when creating a deployment manager profile.
./pctAIX.bin -options /usr/IBM/WebSphere/silentFiles/responsefile.pct.NDstandAloneProfile.txt -silent -log !/usr/IBM/WebSphere/silentFiles/pctlog.txt @ALL
./pctLinux.bin -options /opt/IBM/WebSphere/silentFiles/responsefile.pct.NDstandAloneProfile.txt -silent -log # !/opt/IBM/WebSphere/silentFiles/log.txt @ALL
pctWindows.exe -options "C:\IBM\WebSphere\silentFiles\responsefile.pct.NDstandAloneProfile.txt" -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt @ALL
Go to Installing the product and additional software to continue the installation and configuration of your system.