This topic describes how to perform a silent installation of the product.
Before you begin
Select the appropriate installation path before you begin the installation.
Before starting the silent installation, see Using the launchpad to start the installation for information about the Installation solutions diagrams. The diagrams show typical topologies for the product. The solutions are also in Planning the installation (diagrams).
Why and when to perform this task
Use this procedure to perform a silent installation of the WebSphere Application Server Network Deployment product.
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.
Steps for this task
umaskTo set the umask setting to 022, issue the following command:
umask 022
For example, on some Windows systems, click Administrative Tools > Local Security Policy > User Rights Assignments to see the advanced options. See your Windows documentation for more information.
The installation wizard grants your Windows user ID the
advanced user rights, if the user ID belongs to the administrator group. The
silent installation does not grant these rights. If you create a new user
ID on a Windows platform to perform a silent installation, you must restart
the system to activate the proper authorizations for the user ID before you
can perform a successful silent installation.
When
installing the WebSphere Application Server as a Windows service, do not use
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 problem, install with a user ID that does not contain spaces, or do not
choose to install Windows services.
The name of the original file is responsefile.nd.txt.
You must also create a profile for the Network Deployment product to create an operational environment. You can create a deployment manager profile, an application server profile, or a custom profile that becomes a managed node when you add the node into a deployment manager cell.
-silent
The -silent parameter is not required. If it exists in any of the files, the file cannot create a profile during a silent product installation. If you use the Profile creation wizard in silent mode, the additional parameter does not affect the creation of a profile. However, when the silent installation of the Network Deployment product attempts to call a silent profile response file, the parameter prevents the creation of the profile.
You can find the sample options response file in the WAS directory on the product CD.
Result
The Installation wizard and the Profile creation wizard record installation events in the following log files:
Log | Content | Indicators |
---|---|---|
install_root/logs/log.txt | Logs all installation events |
|
install_root/logs/wasprofile/wasprofile_create_profile_name.log |
|
|
install_root/logs/wasprofile/wasprofile_delete_profile_name.log |
|
|
install_root/profiles/profile_name/logs/pctLog.txt | Logs all profile creation events that occur when using the Profile creation wizard |
|
Log more information when InstallShield for MultiPlatforms (ISMP) cannot start the Installation wizard.
Verify or troubleshoot the installation if the install_root/logs/log.txt file or the profiles_install_root/profile_name/logs/pctLog.txt file does not contain a record of any problems, but problems exist. If the profiles_install_root/profile_name 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 profiles_install_root/profile_name 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 Linux and UNIX systems. 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
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
What to do next
Return to Installing the product and additional software to continue.