You can silently install a customized installation package (CIP) that contains the application server product by using the command line and a response file. To configure the installation, change the options in the response file before you issue the installation command.
You can install a customized installation package (CIP) that includes a WebSphere® Application Server product and one or more maintenance packages and other customization. You must create a CIP with the IBM® Installation Factory before you can install the CIP. See Developing and installing customized installation packages for more information about creating a customized installation package (CIP).
Consider the following before starting this installation.
Customize the response file to add your selections before attempting to install silently.
Use the response file to supply values to the installation wizard as the wizard runs in silent mode. The wizard does not display interactive panels when it runs in silent mode, but reads values from the response file instead.
Be precise when supplying values in the file: Customize the options response file precisely to let the installation program read the option values that the file contains. Incorrect specifications affect the silent interface of the installation wizard. For example, always enclose values in double quotation marks.
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.
Spanned images
If you are installing a spanned CIP, then you must keep all of the CIP images in the same parent directory and name them by disc number, or DISC<disc_number>. For example, name the first disc image DISC1, the second disc DISC2, and so on. Each directory must contain a valid image or the CIP installation will fail.
./install -is:tempdir /temp1
install -is:tempdir c:\temp
This procedure results in creating a customized response file and using the file to start a silent installation. The silent installation takes some time to complete.
Troubleshooting
If you customize the response file incorrectly, the installation wizard cannot install the product with the -options or -silent parameters.
Compare your options response file to the file that is shipped with the product and make any necessary corrections. After correcting the file, reinstall.
Verify the success of the installer program by examining the app_server_root/logs/install/log.txt file to verify that there were no file system or other unusual errors while installing. See the "Troubleshooting installation" topic for more information on other installation logs and log locations.
Verify or troubleshoot the installation if the app_server_root/logs/install/log.txt file or the app_server_root/logs/manageprofiles/pmt.log file does not contain a record of a problem, but problems exist. 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 pmt.log file is in the user_home directory. 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.
After installing the product from the installation image, the next step is to check for available updates before you alter the configuration of the product. Read the "Installing maintenance packages" topic for more information.
After updating the product, create a profile if you have not yet done so. Use the Profile Management Tool or the manageprofiles command to create a profile.
On Windows systems, use the Start menu to locate IBM WebSphere and select appropriate menu options to display the First steps option for the profile that you intend to verify.
The First steps console, firststeps.sh, is available in the profile_root/firststeps directory. A separate First steps console exists for each profile, except custom profiles. Use the First Steps console of each profile to verify the profile.
After verifying the product installation and starting the standalone application server, use the administrative console to deploy an existing application. See Fast paths for WebSphere Application Server for more information.
In this information ...Related tasks
Related information
| IBM Redbooks, demos, education, and more(Index) |