To create a state file, you must run an interactive session of the installer. A state file generated by the installer takes advantage of the installer’s real-time dependency checking and error reporting.
Do not create a state file manually. This method can cause problems at installation time, configuration time, or server startup time.
You create the initial state file by running the installer interactively using the parameters of the installer command that tell the installer to capture your answers. As you proceed through the pages of the installer, your answers are captured and a state file is generated. The installer determines the order of the product components to be installed, so you can specify the components in any order. When you complete the installation, the state file is available in the location that you specified.
You can use the -no option if you do not want software to be installed during this session.
To create a state file using the graphical interface:
./installer -saveState statefile_path
To create a state file using the text-based interface:
./installer -nodisplay -saveState statefile_path
To create a state file using the graphical interface without installing software in this session:
./installer -no -saveState statefile_path
Full syntax for the installer command can be found in Appendix F, Installation Commands.
Refer to Appendix G, Example State File to see an example of a generated state file.
After you have generated a state file, you must edit the state file to ensure that the local parameters are set correctly for the destination host. These parameters include host name, domain name, IP address, and other such settings.
You might also need to change the state file ID, if you plan to do an installation on a platform that is different from the one on which you generated the initial state file.
This section addresses the following:
When editing the state file, follow these guidelines:
Do not modify parameters, except to edit their values.
Do not remove a parameter, even if it does not have a value.
Do not add a parameter.
Do not change the order in which parameters appear.
Notice original types and formats and maintain them as you type new values. For example:
If the old value is a host name, type a host name and not a fully qualified domain name.
If the old value starts with a leading slash, make sure that the new value starts with a leading slash.
Replace any value that you delete. For a required parameter, installation or configuration could fail if the parameter has been deleted.
Retain the case of the original value.
The following table lists parameters that you might need to edit, depending on the product components you want to install or on your host setup. For example, the host on which you generated the state file might be in the same domain as the host on which you are installing.
For a description of each parameter, refer to the tables in Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX.Table 5–2 State File Parameters Often Edited for Silent Installation
Common Server Settings
IS_WS_INSTANCE_DIR (if Web Server is the web container)
Web Proxy Server