Chapter 7 Verifying Installed Components

This chapter provides instructions for verifying that the Sun JavaTM Enterprise System (Java
ES) components have been installed and configured successfully. The procedures here
do not address more complex interactions among components that might occur after configuring
such functionality as single sign-on.

The default installation locations of Java ES components are different
on the Solaris OS and the Linux operating system. Due to this difference, the procedures
in this chapter use placeholders to represent these locations. For example, AccessManager-base represents the base installation directory for Access Manager.

Tip –

In most cases, the examples in this chapter are based on default information.
If you do not remember the installation or configuration values specified for your
component, try the example.

Verifying After Installation

This section provides instructions for verifying that installation of the Java
ES component packages was successful. If you performed a Configure Now installation,
some of the components are configured and ready to run. However, the purpose of the
guidelines in this section is simply to verify that the packages are installed correctly,
with no partial packages or missing components.

A good way to verify that packages were installed successfully is to examine
the product registry. After installation, the Java ES installer updated the product
registry to contain the components that were installed. During uninstallation, this
same file is read by the Java ES uninstaller to determine which components are present
and can be uninstalled.

Looking at the installation logs is also helpful, as is checking a few of the
components to see if the correct version is contained in the appropriate directory.

Finally, you can try to start components that were part of a Configure Now installation,
such as Web Server or Directory Server.

Verifying After Post-Installation Configuration

This section provides guidelines for verifying that the Java ES components are
working after you have finished post-installation configuration.

To start Java ES, you start the components one after another, in a
specific sequence. You 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 these services during installation. Because Portal Server and Access Manager run
inside the web container, they start when you start the web container.

The general sequence for bringing up the entire Java ES 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.

When the startup process has completed, an additional message is displayed:

Domain domain1 started

Verify that the Application Server processes are running. For example,
on Solaris OS:

/usr/bin/ps -ef | grep appserv

/opt/SUNWappserver/appserver/lib/appservDAS domain1

To Access the Admin Console

Step

To access the Admin Console, use the following URL format in your browser: https://localhost:port

If the browser is running on the host on which the Application Server was installed,
specify localhost for the host name. Replace localhost with the name of the system that the Application Server software
is running on if the browser is on another system. Replace the port variable
with the Admin port number assigned during installation. The default port number assigned
during installation is 4849. For example:

To Access the Calendar Server Graphical Interface

Step

If you are already provisioned in the LDAP directory that Calendar Server
points to, you can log into Calendar Server. In your browser, use the http://hostname.domainname [:port] format to access Calendar Server.
For example:

Starting and Stopping Communications Express

Communications Express is a web-based communications client that comprises an
address book, a mail client and a calendar. It is accessed by typing the following
URL into the address field of a web browser:

http://webcontainer-host:
webcontainer-port/URI path

where

webcontainer-host is the host name of the
web container instance in which the Communications Express application is configured.

webcontainer-port is port number of the
web container instance in which the Communications Express is configured.

URI path is the URI where Communications Express is deployed.

Starting and Stopping Directory Proxy Server

For all UNIX-type systems, log in as root if the server runs on ports less than
1024. On ports greater than 1024, log in either as root or using the administrator
account for the server. Directory Proxy Server depends on Administration Server.

To Start Directory Proxy Server

Steps

Change to DirectoryProxyServer-base/dps-instancename where instancename is usually the host name. For example, the default is:

cd /var/opt/mps/serverroot/dps-host1

Enter the following command to start the Directory Proxy Server process.

./start-dps

Verify that the Directory Proxy Server process is running. For example,
on Solaris OS:

/usr/bin/ps -ef | grep dps

./ldapfwd -t /var/opt/mps/serverroot/dps-or03/etc/tailor.txt

To Stop Directory Proxy Server

Steps

Change to DirectoryProxyServer-base/dps-instancename where instancename is usually the host name. For example, the default is:

cd /var/opt/mps/serverroot/dps-host1

Enter the following command to stop the Directory Proxy Server process.

./stop-dps

Verify that Directory Proxy Server is no longer running. For example:

/usr/bin/ps -ef | grep dps

Starting and Stopping Directory Server

If Directory Server is part of a cluster, ensure that you are working on the
active node for the logical host. Directory Server has no dependencies.

Starting and Stopping Instant Messaging Server and Multiplexor

Starting the Instant Messaging server enables Sun Java System Instant Messenger
clients to connect to it. Stopping the Instant Messaging server closes all connections
and disconnects all clients. The configuration of a given instance specifies whether
only the multiplexor, only the server or both these components are enabled. Instant
Messaging depends on Directory Server and Web Server.

To Start Instant Messaging Server and Multiplexor

Steps

Enter the following command to start the Instant Messaging Server and
Multiplexor process:

./imadmin start

Verify that the Instant Messaging processes are running:

./imadmin status

Server [UP}
Multiplexor [UP]
Agent:calendar [DOWN]
Watchdog [UP]

To Stop Instant Messaging

Steps

Change to the InstantMessaging-base/sbin/ directory. For example:

On Solaris OS: cd /opt/SUNWiim/sbin On Linux: cd /opt/sun/im/sbin

Enter the following command to stop the Instant Messaging Server and Multiplexor
process:

./imadmin stop

Verify that the Instant Messaging processes are not running:

./imadmin check

Starting Message Queue

The heart of the Message Queue service is the Message Server. The Message Server
performs message routing and delivery services using one or more brokers. The imqbrokerd command
starts a broker.

To Start Message Queue Message Server Broker

Steps

Change to the MessageQueue-base/bin directory.

Enter the following command to start the Message Queue Message Server
broker:

./imqbrokerd

Verify that the broker process is running. For example:

On
Solaris OS: /usr/bin/ps -ef | grep imqbrokerd

/bin/sh /usr/bin/imqbrokerd

On Linux: /bin/ps -ef | grep imqbrokerd

/bin/sh ./imqbrokerd

Starting and Stopping Messaging Server

The Messaging Server start-msg utility starts all of the
messaging server processes, or optionally, one specified service. The services started
can be controlled by enabling or disabling the configuration parameters. Messaging Server depends
on Directory Server and Administration Server.

To Start Messaging Server

Steps

Change to the MessagingServer-base/sbin directory.

Enter the following command to start the Messaging Server:

./start-msg

Verify that the Messaging Server processes are running.

Notice that the list of processes varies according to the Messaging Server features
you have configured to use.

To Stop Messaging Server

Steps

Verify that the Messaging Server processes are not running. For example.

/usr/bin/ps -ef | grep SUNWmsgsr

Some Messaging Server processes might take several minutes to stop because
they wait for their current transactions to complete.

To Access Messenger Express

Messenger Express is a web-based electronic mail program that enables end users
to access their mailboxes using a browser.

Steps

If you are already provisioned in the LDAP directory to which Messaging Server points,
you can log in using your browser. Use the http://hostname.domainname[:
port] format to access Messenger Express. For example:

http://mycomputer.example.com:80

If the LDAP directory is not yet provisioned, you can login as admin, specifying the password you entered during configuration.

Starting the Web Container to Access Portal Server Desktop

The Portal Server startup and shutdown mechanisms are part of the startup
and shutdown mechanisms for the web container on which it runs (Sun Java Systems or
third-party). It also depends on Directory Server, Access Manager and the Access Manager SDK.
See the following sections to start your Sun web container, Access Manager, and Portal Server after
installation and configuration:

To Stop Web Proxy Server

Steps

On the command line, stop the Admin Server by changing to WebProxyServer-base/proxy-admserv:

Solaris OS: /opt/SUNWproxy/proxy-admin stop

Linux: /opt/sun/webproxyserver/proxy-admin stop

On the command line, stop the Web Proxy Server instance by changing to
the WebProxyServer-base/proxy-hostname.domain :

Solaris OS: /opt/SUNWproxy/proxy-server1 stop

Linux: /opt/sun/webproxyserver/proxy-server1 stop

Next Steps

If you have completed this chapter, you have verified that the Java ES components
that you installed and configured are functional. You can now begin administering
the components. The following documentation can help you get started: