Sun Java Enterprise System 5 Installation Guide for UNIX

Verifying After Postinstallation Configuration

This section provides guidelines for verifying that the Java ES product components are working after you have finished postinstallation configuration.

To start Java ES, you start the product components one after another, in a specific sequence. Some guidelines:

Start with the basic services provided by Directory Server and your web container (Web Server or an application server). Java ES creates runnable instances of Java ES Application Server and Web Server during installation.
Third-party web containers must already be installed and running using instructions in the third-party documentation.

Note –
HP-UX does not support third-party web containers. For Configure Now, Linux only supports the BEA WebLogic container.
Because Portal Server and Access Manager run inside the web container, Portal Server and Access Manager start when you start the web container.
If a service is already running when you start Java ES, the service should be stopped and then restarted after Java ES components are running.
It is good practice to stop and restart the Sun Java Web Console shared component, especially in relation to Directory Service Control Center, Monitoring Console, and Sun Cluster software:
- Solaris OS: /usr/bin/smcwebserver stop
- Solaris OS: /usr/bin/smcwebserver start
- Linux and HP-UX: /opt/sun/webconsole//bin/smcwebserver stop
- Linux and HP-UX: /opt/sun/webconsole//bin/smcwebserver start

The general sequence for bringing up the entire Java ES product component set is shown in the following table. The left column lists the order in which you should perform the startup, the middle column describes the task, and the right column lists the location of the instructions for performing the task.

Table 7–1 Preferred Startup Sequence for Java ES


Order	Task	Location of Instructions
1	Start Directory Server.	Starting and Stopping Directory Server
2	Start your chosen web container. If installed, Access Manager and Portal Server are automatically started.
	- Start Application Server (this starts Message Queue).	Starting and Stopping Application Server
	- Start Web Server.	Starting and Stopping Web Server
	- Start IBM WebSphere Server.	See the third-party documentation for the server.
	– Start BEA WebLogic Server.	See the third-party documentation for the server.
3	Start Portal Server Secure Remote Access.	Starting and Stopping Portal Server Secure Remote Access
4	Start Web Proxy Server	Starting and Stopping Web Proxy Server
5	Start Service Registry	Service Registry 3.1 Administration Guide
6	Start Monitoring Console	Starting the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide

To shut down the entire Java ES product component set, reverse the sequence.