Silent installation is a non-interactive method used for installing Communications Suite on multiple hosts that share similar configurations. This chapter provides instructions for using silent mode to install the Communications Suite software.
This chapter includes the following sections:
To run a silent installation, you first run an interactive installation session using the silent install syntax of the installer command. This creates a state file that the silent installation process will use. During the interactive session, your responses to the installer are captured as a set of name-value pairs in a state file. Each name-value pair represents a single prompt or field in the installation process. With the state file as input, you can then run the installer on any number hosts. This process allows you to propagate one configuration across multiple hosts in your enterprise.
The installer cannot run a state file from a different version of Communications Suite or Java ES. That is, if you create your state file using Communications Suite 5, you cannot run this state file to install Java ES 2005Q4.
The following table presents the main events in a silent installation. Links to instructions are in the right column.
Table 5–1 Silent Installation Events
Event |
Location of Instructions |
---|---|
1. Verify that your hosts meet the Communications Suite installation prerequisites. | |
2. Run an interactive installation session to generate a state file. | |
- Using the graphical installer |
Chapter 3, Installing Communications Suite With the Graphical Interface |
- Using the text-based installer | |
3. Copy the state file to another host and edit the state file for that host. | |
4. (Optional) Edit the state file to run on a different platform from the platform where the state file was generated. | |
5. Run a silent installation session on each host. |
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.
Syntax examples:
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
Component |
Parameter Name |
---|---|
Common Server Settings |
CMN_HOST_NAME CMN_DOMAIN_NAME CMN_IPADDRESS CMN_ADMIN_USER CMN_ADMIN_PASSWORD CMN_SYSTEM_USER CMN_SYSTEM_GROUP |
Access Manager |
IS_WS_HOST_NAME IS_WS_INSTANCE_DIR (if Web Server is the web container) CONSOLE_HOST IS_SERVER_HOST IS_DS_HOST IS_DS_HOSTNAME COOKIE_DOMAIN_LIST |
Application Server |
ASNA_ADMIN_HOST_NAME AS_WEB_SERVER_LOCATION AS_WEB_SERVER_PLUGIN_TYPE |
Directory Server |
CREATE_INSTANCE DSEE_INSTANCE_DIR DSEE_INSTANCE_PORT DSEEE_INSTANCE_SSL_PORT DSEE_DN_MANAGER DSEE_INSTANCE_USER DSEE_INSTANCE_GROUP DSEE_INSTANCE_PASSWORD DSEE_SUFFIX |
Web Server |
WS_ADMIN_HOST |
Web Proxy Server |
CMN_WPS_INSTALLDIR WPS_ADMIN_USER WPS_ADMIN_PASSWORD WPS_ADMIN_PORT WPS_ADMIN_RUNTIME_USER WPS_INSTANCE_RUNTIME_USER WPS_ISNTANCE_PORT WPS_INSTANCE_AUTO_START WPS_PROXY_DOMAIN |
A state file can only be run on a host of the same platform type as the host where the state file was generated unless you edit the state file ID. Each platform has a different type of state file ID. There are two ways to create a state file to run on a platform other than the one on which it was created:
Using the Installer
Using Platform-Specific Distribution Files
This procedure generates a state file ID by running the installer on the platform on which you want to perform silent installation.
The following command works only if you are generating an ID for the same platform on which you are running the command.
If you are not logged in as root, become superuser.
Navigate to the directory where the installer is located:
cd installer-directory |
Run the installer with the -id option.
./installer -id |
The command generates an encrypted identifier.
Copy the identifier and paste the value into the state file, as the value for the STATE_BEGIN and STATE_DONE parameters.
The following is an example of the state file identifier within a state file:
[STATE_BEGIN Sun Java(tm) Enterprise System \ f31c7e86a64605bc5b9b629931a30b275a0eb447] . . . [STATE_DONE Sun Java(tm) Enterprise System \ f31c7e86a64605bc5b9b629931a30b275a0eb447] |
This procedure generates a state file ID by using the Communications Suite distribution files for a specific platform. The Communications Suite distribution DVD contains all platform-specific distributions. This procedure works if you download a single platform-specific distribution or even if you are generating an ID for a platform different from the one on which you are running the command.
In the platform/.install directory, run this command:
java -classpath . -D"wizard.idInfo" class |
where platform and class are listed in the following table:
Platform |
Platform Variable |
Class Variable |
---|---|---|
Solaris 9 SPARC |
Solaris_sparc |
EntsysInstall_SunOS_sparc_9 |
Solaris 10 SPARC |
Solaris_sparc |
EntsysInstall_SunOS_sparc_10 |
Solaris 9 x86 |
Solaris_x86 |
EntsysInstall_SunOS_x86_9 |
Solaris 10 x86 |
Solaris_x86 |
EntsysInstall_SunOS_x86_10 |
Linux x86 |
Linux_x86 |
EntsysInstall_Linux_x86_generic |
The command generates an encrypted identifier.
Copy the identifier and paste the value into the state file, as the value for the STATE_BEGIN and STATE_DONE parameters.
The following is an example of the state file identifier within a state file:
[STATE_BEGIN Sun Java(tm) Enterprise System \ f31c7e86a64605bc5b9b629931a30b275a0eb447] . . . [STATE_DONE Sun Java(tm) Enterprise System \ f31c7e86a64605bc5b9b629931a30b275a0eb447] |
You should run the installer on a host that has the same operating system as the host on which you generated the state file. If you cannot do this, refer to Creating a Platform-Appropriate State File ID.
If you have problems during installation, refer to Chapter 10, Troubleshooting.
Silent installation can be lengthy, depending on the number and type of product components that you are installing.
Verify that your state file is edited correctly for the host.
If you are not logged in as root, become superuser.
Navigate to the directory where the installation program is located.
cd installer-directory |
Run the installer using the following syntax:
./installer -nodisplay -noconsole -state statefile |
-nodisplay |
Suppress the graphical display. |
-noconsole |
Start the installer in silent mode, suppressing the user interface. |
-state |
Use the specified state file as input to a silent installation. |
statefile |
Specify an absolute or relative pathname to a state file. |
After installation is complete, proceed to the next host and repeat Steps 1 through 4.
While the installer is running, you can monitor progress by examining changes to the installation log.
In a terminal window, change to the log file directory:
Solaris OS:cd /var/sadm/install/logs
Linux: cd /var/opt/sun/install/logs
Locate the log files for the current installation.
The shared components are installed first and the product components follow.
The timestamp variable represents the time the log was created. The variable has the format MMddhhmm.
MM |
Specifies the month |
dd |
Specifies the date |
hh |
Specifies the hour |
mm |
Specifies the minute |
Use the tail command to watch messages as they are written to the logs:
tail -f logfile-name |
To exit the tail program, press Ctrl+C.
After you have completed the installer portion of your Communications Suite installation, proceed as follows:
Verifying After Installation provides instructions for verifying that this phase of installation was successful.
Chapter 6, Completing Communications Suite Postinstallation Configuration provides instructions on postinstallation configuration.