Sun Java Communications Suite 5 Installation Guide

How to Use This Chapter

When the installer finishes installation, most product components require additional configuration before the Communications Suite environment is operational. The extent of this work depends on the configuration type you selected (Configure Now or Configure Later), and whether or not your product components will be configured for monitoring or Sun Cluster.

If you selected the Configure Later type during installation, the installer placed the product component package files in their respective directories. No parameter setting was done, and most product components are not operational because runtime services are not available. A number of product components include configuration tools for completing a Configure Later installation. When running the configuration tools, you can make any additional changes by following the instructions located in this guide, and in the product documentation for each product component.

Before acting on the information in this chapter, you should have installed the Communications Suite components. You can examine the product registry Solaris OS pkginfo command or the Linux rpm command to verify that the component packages have been installed. A list of packages associated with the components is contained in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX.

A summary report containing the configuration values that were set during installation is available here:

Solaris OS: /var/sadm/install/logs

Linux: /var/opt/sun/install/logs

After completing installation, look through the procedures included in this chapter for the product components you installed. If you determine that no additional configuration is required for your product components, you can start your product components by following the instructions in Chapter 7, Verifying Installed Product Components.

Note –

The default installation locations of Communications Suite product components might be different on the various platforms. Due to this, the procedures in this chapter use variables to represent these locations. For example, ApplicationServer-base represents the directory where Application Server is installed, regardless of platform.