test

Sun Java Communications Suite 5 Installation Guide

Chapter 7 Verifying Installed Product Components

This chapter provides instructions for verifying that the Communications Suite product components have been installed and configured successfully. The procedures here do not address more complex interactions among product components that might occur afterinitial configuring, such as single sign-on configuration.

This chapter includes the following sections:

How to Use This Chapter

There are two types of verification presented in this chapter: verifying directly after installation, and verifying after all post-installation configuration is done.

The default installation locations of Communications Suite product components are different on the various 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.

Verifying After Installation

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

A good way to verify that packages were installed successfully is to examine the product registry. After installation, the installer updated the product registry to contain the product components that were installed. Product registry is located here:

You can also check a few of the product component directories to see if software is in the appropriate directory. Default directories are listed in Chapter 2, Default Installation Directories and Ports, in Sun Java Enterprise System 5 Installation Reference for UNIX. Listings of the packages for the Communications Suite components can be found in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX. During uninstallation, the product registry is read by the uninstaller to determine which product components are present and can be uninstalled.

Looking at the installation logs is also helpful, especially if any of the packages do not seem correct in the product registry. For instructions on using the logs and the Log Viewer, refer to Examining Installation Log Files.

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

ProcedureTo Verify That Installation Succeeded

Use some or all of the following steps to verify basic installation.

  1. Verify that no partial packages were installed. On Solaris OS:


    pkginfo -p

  2. Verify that the correct version of a product component is present.

    To see the correct product component versions for this release, refer to Appendix E, Product Components for This Release. For example, the J2SE version for Solaris should be 1.5.0_06. 


    cd /usr/jdk
ls -l

  3. Verify that the installed product components are reflected in the product registry.

    1. On Solaris, use the prodreg tool to view installed packages:


      prodreg &

    2. Expand the Java Enterprise System Node to view the packages installed by the installer.

    3. You can also use the following command to view the productregistry file directly.


      more /var/sadm/install/productregistry

  4. Review the configuration data you provided during installation by opening the summary log:


    cd /var/sadm/install/logs
more Java_Enterprise_System_Summary_Report_install.*

  5. For a Configure Now installation, start the following services:

    1. Start Directory Server instance:


      /DirectoryServer-Base/bin/dsadm start /var/opt/SUNWdsee/dsins1

    2. Start Web Server instance:

      Solaris: /var/opt/SUNWwbsvr7/admin-server/bin/startserv

      Linux: /var/opt/sun/webserver7/admin-server/bin/startserv

      Starting Web Server automatically starts Access Manager.

    3. Access the Web Server URL:


      http://hostname:port

    4. Access the administration URL for Web Server:


      http://hostname:8800

  6. For a Configure Now installation, stop the following services:

    1. Stop the Web Server administration server:

      Solaris: /var/opt/SUNWwbsvr7/admin-server/bin/stopserv

      Linux: /var/opt/sun/webserver7/admin-server/bin/stopserv

    2. Stop Web Server:

      Solaris: /var/opt/SUNWwbsvr7/https-hostname.domainname/bin/stopserv

      Linux: /var/opt/sun/webserver7/https-hostname.domainname/bin/stopserv

    3. Stop Directory Server:


      DirectoryServer-Base/bin/dsadm stop /var/opt/SUNWdsee/dsins1

  7. For a Configure Now installation, start the web container to access Access Manager services

  8. For a Configure Now installation, access the Access Manager console

    For login, User ID is amadmin, password was entered during installation


    http://hostname:port/amconsole

  9. If errors occur, restart Web Server and repeat the steps.

Verifying After Post-Installation Configuration

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

To start Communications Suite, you start the product 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). Communications Suite creates runnable instances of these services during installation. Because Access Manager runs inside the web container, Access Manager starts when you start the web container.

The general sequence for bringing up the entire Communications Suite 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 Communications Suite

Order 

Task 

Location of Instructions 

1 

Start Directory Server. 

Starting and Stopping Directory Server

2 

Start your chosen web container. If installed, Access Manager is started. If installed and configured, Communications Express is also started. 

Start Application Server (also 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 Access Manager 

Starting and Stopping Access Manager

5 

Start Instant Messaging. 

Starting and Stopping Instant Messaging Server and Multiplexor

6 

Start Messaging Server. 

Starting and Stopping Messaging Server

7 

Start Calendar Server. 

Starting and Stopping Calendar Server

9 

Start Monitoring Console 

Starting the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide

To shut down the entire Communications Suite product component set, reverse the sequence.

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 product component, try the example.

Starting and Stopping Access Manager

To start and stop Access Manager, start and stop the web container in which it is running.

ProcedureTo Access the Access Manager Login Page

Accessing the login page depends on the type of installation you did for Access Manager:

  1. Use the following URL format to access the default page in Legacy Mode:


    http://web-container-host:port/amconsole

    The Access Manager login page appears.

  2. Log in.

    A successful login to Access Manager confirms successful deployment of the software. The default administrator account is amadmin.

Starting and Stopping Application Server

Application Server is configured as a domain. The installer creates the default administrative domain with the default port number 4849. More information can be found in the Chapter 1, Getting Started, in Sun Java System Application Server Enterprise Edition 8.2 Administration Guide.

Note –

Starting Application Server also starts Message Queue.

ProcedureTo Start the Application Server Domain

  1. On the command line, change to ApplicationServer-base/bin and enter:


    % asadmin start-domain --user admin-id --passwordfile \
path_to_admin-password_file domainname

  2. Enter the values that you provided during installation. A message is displayed telling you that the server is starting:


    Starting Domain domain1, please wait. Log redirected to install_dir...

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


    Domain domain1 started

  3. Start individual Application Server instances. For example:


    ./asadmin start-domain --domain domain1 --user
    Note –

    If you receive a message indicating failure to start, configuration changes might not be applied yet. In this case, run the asadmin reconfig command. For example: 


    asadmin reconfig --user admin --password adminadmin --host localhost --port 4849 server

  4. 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

ProcedureTo Stop Application Server

  1. On the command line, change to ApplicationServer-base/bin.

  2. Enter the following command to stop the Application Server instances.


    ./asadmin stop-domain --domain domain1

  3. Verify that Application Server is no longer running. For example:


    /usr/bin/ps -ef | grep appserv

Starting and Stopping Calendar Server

ProcedureTo Start Calendar Server

  1. On the command line, change to the sbin directory.

    Solaris OS: /opt/SUNWics5/cal/sbin

    Linux: /opt/sun/calendar/sbin

  2. Enter the following command to start Calendar Server.


    ./start-cal

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


    /usr/bin/ps -ef | grep cal
    		 

    /opt/SUNWics5/cal/lib/cshttpd -d 3
/opt/SUNWics5/cal/lib/enpd -p 57997 -c config/ics.conf
/opt/SUNWics5/cal/lib/csadmind
/opt/SUNWics5/cal/lib/csnotifyd
/opt/SUNWics5/cal/lib/csstored
/opt/SWUNics5/cal/lib/watcher
/opt/SUNWics5/cal/config/watcher

ProcedureTo Access the Calendar Server Graphical Interface

  1. 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:

    http://mycomputer.example.com:89

    At initial login, Calendar Server creates a default calendar for you. Your login to Calendar Server confirms successful installation.

ProcedureTo Stop Calendar Server

  1. Change to the sbin directory.

    Solaris OS: /opt/SUNWics5/cal/sbin

    Linux: /opt/sun/calendar/sbin

  2. Enter the following command to stop Calendar Server.


    ./stop-cal

  3. Verify that Calendar Server is no longer running. For example:


    /usr/bin/ps -ef | grep cal

Starting and Stopping Communications Express

Communications Express is a web-based communications client that includes 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://webcontinaer-host:webcontainer-port/URIpath

where

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.

Note –

Before using the dsadm command to start or stop Directory Server, verify that the LD_LIBRARY_PATH environment variable is unset. If it is not unset, you might receive an error when dsadm cannot find a dependent library.

ProcedureTo Start Directory Server

  1. If a Directory Server instance does not yet exist, create one. See the Directory Server Administration documentation for details.

  2. Start Directory Server instance:

    Solaris OS: /opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dsins1

    Linux: /opt/sun/ds6/bin/dsadm start /var/opt/sun/dsins1

ProcedureTo Stop Directory Server

  1. Stop Directory Server instance:

    Solaris OS: /opt/SUNWdsee/ds6/bin/dsadm stop /var/opt/SUNWdsee/dsins1

    Linux: /opt/sun/ds6/bin/dsadm stop /var/opt/sun/dsins1

Starting and Stopping Instant Messaging Server and Multiplexor

Starting the Instant Messaging server enables Instant Messenger clients to connect to the server. 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 product components are enabled.

Note –

For information on starting the Instant Messaging client (and the server on the Windows operating system), refer to the Sun Java System Instant Messaging 7.2 Administration Guide.

ProcedureTo Start Instant Messaging and the Multiplexor

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

    Solaris OS: cd /opt/SUNWiim/sbin

    Linux: cd /opt/sun/im/sbin

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


    ./imadmin start

  3. Verify that the Instant Messaging processes are running:


    ./imadmin status
    		 

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

ProcedureTo Stop Instant Messaging

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

    Solaris OS: cd /opt/SUNWiim/sbin

    Linux: cd /opt/sun/im/sbin

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


    ./imadmin stop

  3. Verify that the Instant Messaging processes are not running:


    ./imadmin check

Starting and Stopping Message Queue

Message Queue uses a broker to route and deliver messages. (To scale the Message Queue service, brokers can be clustered.) The imqbrokerd command starts a broker.

ProcedureTo Start Message Queue Broker

  1. Change to the MessageQueue-base/bin directory.

  2. Enter the following command to start the Message Queue broker:


    ./imqbrokerd

  3. Verify that the broker process is running. For example:

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

    Linux: /bin/ps -ef | grep imqbrokerd

ProcedureTo Stop Message Queue Broker

  1. When you stop a running broker, you are prompted for user admin user name and password.

    Solaris OS: /usr/bin/imqcmd shutdown bkr [ -bhostname:port]

    Linux: /opt/sun/mq/bin/imqcmd shutdown bkr [ -b hostname:port]

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.

ProcedureTo Start Messaging Server

  1. Change to the MessagingServer-base/sbin directory.

  2. Enter the following command to start the Messaging Server:


    ./start-msg

  3. Verify that the Messaging Server processes are running. For example:

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


    /usr/bin/ps -ef | grep SUNWmsgsr
    		 

    /opt/SUNWmsgsr/lib/enpd
/opt/SUNWmsgsr/lib/stored -d
/opt/SUNWmsgsr/lib/popd -d 5
/opt/SUNWmsgsr/lib/imapd -d 5 -D 6
/opt/SUNWmsgsr/lib/mshttpd -d 5 -D 6
/opt/SUNWmsgsr/lib/dispatcher
/opt/SUNWmsgsr/lib/job_controller
/opt/SUNWmsgsr/lib/tcp_lmtp_server
/opt/SUNWmsgsr/lib/tcp_smtp_server
/opt/SUNWmsgsr/lib/tcp_smtp_server
/opt/SUNWmsgsr/lib/imsched
/opt/SUNWmsgsr/lib/watcher

ProcedureTo Stop Messaging Server

  1. Change to the MessagingServer-base/sbin directory.

  2. Enter the following command to stop the Messaging Server:


    ./stop-msg

  3. Verify that the Messaging Server processes are not running. For example, on Solaris OS:


    /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.

Starting and Stopping Monitoring Console

Monitoring Console cannot be run from the same host where any of the product components are installed. For instructions for using Monitoring Console, refer to Starting the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide.

Stopping and Rebooting Sun Cluster Software

Although Sun Cluster software is not started and stopped like other product components, the software can be stopped by rebooting into noncluster mode. For instructions, refer to the Sun Cluster System Administration Guide for Solaris OS.

Starting and Stopping Web Server

When you install Web Server, two server instances are installed by default: an Administration Server instance and a Web Server instance.

ProcedureTo Start Web Server

  1. Start the Admin Server:

    For Solaris OS: /var/opt/SUNWwbsvr7/admin-server/bin/startserv

    For Linux: /var/opt/sun/webserver7/admin-server/bin/startserv

  2. Start the Web Server instance:

    For Solaris OS: /var/opt/SUNWwbsvr7/https-instanceName/bin/startserv

    For Linux: /var/opt/sun/webserverr7/https-instanceName/bin/startserv

  3. Access the Web Server Administration Server administration instance

    In the browser, enter the http://hostname .domainname:adminport format. For example:

    For SSL port (this is the default): https://host1.example.com:8989

    For HTTP port: http://host1.example.com:8800

    Your login confirms successful installation.

ProcedureTo Stop Web Server

  1. Stop the Admin Server:

    For Solaris OS: /var/opt/SUNWwbsvr7/admin-server/bin/stopserv

    For Linux: /var/opt/sun/webserver7/admin-server/bin/stopserv

  2. Stop the Web Server instance:

    For Solaris OS: /var/opt/SUNWwbsvr7/https-instanceName/bin/stopserv

    For Linux: /var/opt/sun/webserverr7/https-instanceName/bin/stopserv

Starting and Stopping Web Proxy Server

ProcedureTo Start Web Proxy Server Admin Server and Instance

When you install Web Proxy Server, two server instances are installed by default: a Web Proxy Server Admin Server instance and a Web Proxy Server instance.

  1. On the command line, start the Web Proxy Admin Server by changing to WebProxyServer-base/proxy-admserv:

    • Solaris OS: /opt/SUNWproxy/proxy-admserv/start

    • Linux: /opt/sun/webproxyserver/proxy-admserv/start

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

    • Solaris OS: /opt/SUNWproxy/proxy-server1/start

    • Linux: /opt/sun/webproxyserver/proxy-server1/start

  3. Verify that the Web Proxy Server processes are running. For example:


    /usr/bin/ps -ef | grep proxy

ProcedureTo Start the Socks Server

  1. From the command line, go to WebProxyServer_base/proxy-serverid.

  2. Start the Socks Server:


    ./start-sockd

  3. Verify that the Socks Server processes are running.

    For example:


    /usr/bin/ps -ef | grep sockd

ProcedureTo Access the Administration Server Graphical Interface

  1. Use the http://hostname.domainname:adminport format to access the Administration Server graphical interface. For example:

    http://host1.example.com:8888

    Your login confirms successful installation.

ProcedureTo Stop Web Proxy Server

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

    • Solaris OS: /opt/SUNWproxy/proxy-admserv/stop

    • Linux: /opt/sun/webproxyserver/proxy-admserv/stop

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

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

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

  3. Verify that the Web Proxy Server processes are not running. For example:


    /usr/bin/ps -ef | grep proxy

ProcedureTo Stop the Socks Server

  1. From the command line, go to WebProxyServer_base/proxy-serverid.

  2. Start the Socks Server:


    ./stop-sockd

  3. Verify that the Socks Server processes are not running. For example:


    /usr/bin/ps -ef | grep sockd

Next Steps

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