In silent mode, the Installation wizard gathers installation options from a response file instead of from the graphical user interface. This topic describes how to customize the response file for installing a customized installation package (CIP) for the product silently. A silent installation does not use the graphical user interface of the Installation wizard.
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.
If you customize the response file incorrectly, the installation wizard cannot install the product with the -options or -silent parameters. If the error is an invalid option value, the installer displays a warning message that confirm and stops the installation.
Compare your options response file to the file that is shipped with the product to make the necessary corrections. After correcting the file, reinstall.
Perform the following procedure to edit the response file.
Edit the version of the file that ships with the product. The example in responsefile.nd.txt is not guaranteed to be an accurate representation of what ships with the product.
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.
After installing the product from the installation image, the next step is to check for available updates. See Installing maintenance packages for more information.
After updating the product, create a profile if you have not yet done so. Start the Profile Management tool, and create a deployment manager cell. The cell contains a deployment manager profile and a federated application server profile.
Use the installver program to compare the checksum of all installed files against the bill of materials that ships with the product, if you want to perform more installation verification. See Verifying checksums of installed files.
After verifying
the product installation and starting the deployment
manager or a stand-alone application server, use the administrative console
to deploy an existing application. See Fast paths for WebSphere Application Server for more information.