Performing Postinstallation Configuration and Verification

This section contains questions about completing postinstallation configuration and then verifying that the Java ES components work.

• Q28: What postinstallation configuration is required?

• Q29: How do I know if the postinstallation configuration succeeded?

• Q30: How do I start and stop Java ES components?

Q28: What postinstallation configuration is required?

Answer: When the Java ES installer finishes, most product components require additional configuration to work together. The extent of the configuration tasks varies depending on the configuration type you selected during installation (Configure Now or Configure Later), whether you installed Sun Cluster software or Monitoring Console, and how much extended configuration is needed to build your deployment.

For product components that require postinstallation configuration, refer to Chapter 6, Completing Postinstallation Configuration, in Sun Java Enterprise System 5 Installation Guide for UNIX. (If components are not included in this listing, postinstallation configuration is not required.)

• Configure Now or Configure Later configuration type

  • If you selected Configure Now, the installer prompted you for configuration values for the components being configured. Very little additional configuration is required for the components you configured, but there might be some.

  • If you selected Configure Later, the installer placed the component packages in their respective directories, parameter setting was not done, and most components are not yet operational. In most cases, you will use the component configuration tools and files to complete a Configure Later installation.

• Sun Cluster software Sun Cluster configurations are supported only on Solaris OS, using the Configure Later configuration type. If you installed Sun Cluster software, you need to perform postinstallation configuration as described in Sun Cluster Postinstallation Configuration in Sun Java Enterprise System 5 Installation Guide for UNIX. Understanding the high-level Sun Cluster installation tasks might help with configuration. See Sun Cluster Software Example in Sun Java Enterprise System 5 Installation Guide for UNIX.

• Monitoring Console To perform monitoring, you must enable and sometimes configure the monitoring service with each component you have installed. For instructions, see Chapter 3, Installing and Using Monitoring Console, in Sun Java Enterprise System 5 Monitoring Guide. You can see the basic installation sequence in Monitoring Console Only Example in Sun Java Enterprise System 5 Installation Guide for UNIX.

• Man pages If the product components you installed have man pages, some configuration might be required. See Verifying Man Pages in Sun Java Enterprise System 5 Installation Guide for UNIX. Table 6-1 lists the Java ES components that have man pages.

After any type of Java ES deployment, you can use the component configuration tools to make additional changes or enhancements to your configuration.

Q29: How do I know if the postinstallation configuration succeeded?

Answer: After you complete postinstallation configuration, follow the postinstallation verification procedure to verify that your Java ES components have basic functionality. See Verifying After Postinstallation Configuration in Sun Java Enterprise System 5 Installation Guide for UNIX. The installer does not start the Java ES components, so starting the components is part of verifying success of the installation and the initial configuration.

The verification procedure determines only whether the basic installed Java ES is working, not whether you installed the components correctly according to your deployment plan. If the resulting installation does not meet your needs, you can run the uninstaller to uninstall all of the product components, and then perform a new installation.

Q30: How do I start and stop Java ES components?

Answer: You activate Java ES by starting the components in a specific sequence, beginning with the basic services provided by Directory Server and your web container (Web Server or an application server). When you start the web container, the components that run in that web container, such as Portal Server and Access Manager, are automatically started. The preferred startup sequence is described in Table 7–1 in Verifying After Postinstallation Configuration in Sun Java Enterprise System 5 Installation Guide for UNIX. To stop Java ES, stop the components in the reverse order. Instructions for starting and stopping individual product components are contained in Chapter 7, Verifying Installed Product Components, in Sun Java Enterprise System 5 Installation Guide for UNIX.