Chapter 7 Verifying Installed Product Components

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

This chapter includes the following sections:

• How to Use This Chapter

• Verifying After Installation

• Verifying After Postinstallation Configuration

• Accessing the Portal Server Desktop by Starting the Web Container

• Starting and Stopping Access Manager

• Starting and Stopping Application Server

• Starting and Stopping Directory Proxy Server

• Starting and Stopping Directory Server

• Starting and Stopping Message Queue

• Starting and Stopping Monitoring Console

• Starting and Stopping Portal Server Secure Remote Access

• Stopping and Rebooting Sun Cluster Software

• Starting and Stopping Web Proxy Server

• Starting and Stopping Web Server

• Next Steps

How to Use This Chapter

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

• Verifying after installation. This type of verification is used to discover if installation was basically successful; only some components can be started and stopped at this point.

• Verifying after postinstallation configuration. This type of verification is used to verify that all the components can be started and are capable of running. Instructions for starting and stopping each component individually are included.

The default installation locations of Java ES product components are different on the various operating system. Due to this difference, the procedures in this chapter often 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 product component, try the example. Default installation directories and ports are listed in Chapter 2, Default Installation Directories and Ports, in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX.

---

Verifying After Installation

This section provides instructions for verifying that installation of an example set of Java ES product component packages was successful. If you performed a Configure Now installation, a few of the product components in this example 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 Java ES installer updated the product registry to contain the product components that were installed. During uninstallation, the product registry is read by the Java ES uninstaller to determine which product components are present and can be uninstalled. Product registry is located here:

• Solaris OS: /var/sadm/install/productregistry

• Linux: /var/opt/sun/install/productregistry

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 Update 1 Installation Reference for UNIX. Listings of the packages for the Java ES components can be found in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX.

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.

To Verify That Installation Succeeded

After postinstallation configuration is complete, use some or all of the following steps in this example to verify basic installation of the specified set of product components.

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

   pkginfo -p

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

   To see the correct product component versions for this release, refer to Appendix A, Java ES Components for This Release. For example, the J2SE version for Solaris should be 1.5.0_12.

   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 Java ES 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_5_Summary_Report_install.*

5. For a Configure Now installation, start Portal Server and its related services.

   1. Start Directory Server instance:

      /opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dsins1

   2. Start Web Server instance:

      For Solaris:

      /var/opt/SUNWbsvr7/https-hostname.domainname/bin/startserv

      For Linux:

      /var/opt/sun/webserver7/https-hostname.domainname/bin/startserv

      Starting Web Server automatically starts Portal Server and Access Manager.

      ---

      Note –

      If you used a web container other than Web Server, the process might be different.

      ---

   3. Access the Web Server URL:

      http://hostname:port

   4. Start the administration instance:

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

   5. Access the administration URL for Web Server:

      http://hostname.domainname:8800

6. For a Configure Now installation, stop Portal Server and its related services:

   1. Stop the Web Server administration server:

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

   2. Stop Web Server:

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

   3. Stop Directory Server:

      /opt/SUNWdsee/ds6/bin/dsadm stop /var/opt/SUNWdsee/dsins1

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

   Accessing the Portal Server Desktop by Starting the Web Container

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

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

   http://hostname.domainname:port/amconsole

9. For a Configure Now installation, access Portal Server:

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

   http://hostname.domainname:port/portal

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

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 –

  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/sbin/smcwebserver stop

  • Solaris OS: /usr/sbin/smcwebserver start

  • Linux: /opt/sun/webconsole/bin/smcwebserver stop

  • Linux: /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 Update 1 Administration Guide
6	Start Monitoring Console	Starting the Monitoring Console in Sun Java Enterprise System 5 Update 1 Monitoring Guide

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

Accessing the Portal Server Desktop by Starting the Web Container

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). Portal Server 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:

• Starting and Stopping Application Server

• Starting and Stopping Web Server

Portal Server administrators use the Access Manager Console for managing end-user access to the Portal Server desktop. See Starting and Stopping Access Manager to open the Access Manager Console.

The following procedures pertain to accessing the end-user Portal Server Desktop after postinstallation configuration is complete:

• To Access the Portal Server Desktop from a Sun Web Container

• To Access the Portal Server Desktop from BEA WebLogic

• To Access the Portal Server Desktop from IBM WebSphere

To Access the Portal Server Desktop from a Sun Web Container

The web protocol for Portal Server can be either HTTP or HTTPS. By default, the host is hostname.domain.

1. In a browser window, use the following URL format to display the sample Desktop (the default Portal Access URL and default deployment URI are/portal):

   http://hostname.domain:port/portal

   When you enter the URL, the welcome page is displayed, including a short description of Portal Server and links to the sample portals that you selected for installation. Click one of the links to access the anonymous portal desktop for the sample portal. If the sample desktop displays without any exception, your Portal Server installation was successful.

2. Enter the following in the browser:

   http://hostname.domain:port/psconsole

3. Verify that the gateway is running on the specified port (default is 443):

   netstat –an | grep port-number

   If the gateway is not running, use the following command to start the gateway:

   PortalServer-base/bin/psadmin start-sra-instance –u amadmin -f amadmin-password-file – –instance-type gateway – –instance-name GatewayInstancename

4. View the log files to verify that there are no problems logged.

5. Run Portal Server in secure mode by typing the gateway URL in your browser:

   https://gateway-hostname.domainname:port

   If you have chosen the default port (443) during installation, you need not specify the port number.

6. For a mobile device, use the following URL format:

   http://hostname.domain:port/portal/dt

   ---

   Note –

   The Portal Server URL and the deployment URI must be the same. For example, if the Portal Server URL is http://hostname.domain:port/portal, the deployment URI must be /portal.

   • Portal ID: The default value is portal1.

   • Search ID: The default value is search1.

   • Deployment URI: The default value is /portal.

   ---

To Access the Portal Server Desktop from BEA WebLogic

1. In a new browser window on Solaris OS, use the following URL to display the Sample Desktop:

   http://beaweblogic-host: port/portal

   Display of the Sample Desktop confirms successful deployment of Portal Server on BEA WebLogic.

To Access the Portal Server Desktop from IBM WebSphere

1. In a new browser window on Solaris OS, use the following URL to display the Sample Desktop:

   http://ibmwebsphere-hostname: port/portal

   Display of the Sample Desktop confirms successful deployment of Portal Server on IBM WebSphere.

Starting and Stopping Access Manager

To start and stop Access Manager after postinstallation configuration is complete, start and stop the web container in which Access Manager is running.

To Access the Access Manager Login Page

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

• Legacy (6.x):

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

  or

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

• Realm (7.x):

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

1. Use the following URL format to access the default page in Legacy (6.x) mode:

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

   The Access Manager login page appears.

2. Use the following URL format to access the default page in Realm (7.x) mode:

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

   The Access Manager login page appears.

3. Log in.

   The default administrator account is amadmin. Your login confirms successful installation.

Starting and Stopping Application Server

Application Server is configured as a domain. The Java ES installer creates the default administrative domain with the default port number 4849. The Administration Server instance name is server. To use Application Server after postinstallation configuration is complete, start the domain and access the graphical Administration Console. 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.

---

To Start the Application Server Domain

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

   ---

   Note –

   The contents of the administrator password file should be AS_ADMIN_PASSWORD=password.

   ---

2. Start the domain. For example:

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

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

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

To Access the Administration Console

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

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

   https://mycomputer.example.com:4849

   Display of the Administration Console Login screen confirms successful installation.

   ---

   Note –

   More information on installing the Application Server, the Domain Administration Server, and its various port numbers and concepts can be found in the Sun Java System Application Server Enterprise Edition 8.2 Installation Guide.

   ---

To Stop Application Server

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

2. Stop the Application Server instances. For example:

   ./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 Directory Proxy Server

After postinstallation configuration is complete, use the following procedures for starting and stopping Directory Proxy Server.

To Start Directory Proxy Server

1. If a Directory Proxy Server instance does not yet exist, create one.

2. On the command line, change to DirectoryProxyServer-base/bin.

3. Start the Directory Proxy Server instance. For example:

   ./dpadm start /var/opt/SUNWdsee/dpsins1

To Stop Directory Proxy Server

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

2. Stop the Directory Server Proxy Server instance. For example:

   ./dpadm stop /var/opt/SUNWdsee/dpsins1

Starting and Stopping Directory Server

After postinstallation configuration is complete, use the instructions in this section to start and stop 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 this variable is not unset, you might receive an error when dsadm cannot find a dependent library.

---

To Start Directory Server

1. If a Directory Server instance does not yet exist, create one.

2. On the command line, change to DirectoryServer-base/bin.

3. Start the Directory Server instance. For example:

   ./dsadm start /var/opt/SUNWdsee/dsins1

To Stop Directory Server

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

2. Stop the Directory Server instance. For example:

   ./dsadm stop /var/opt/SUNWdsee/dsins1

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.

To Start Message Queue Broker

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

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

To 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 [ -b hostname:port ]

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

Starting and Stopping Monitoring Console

After postinstallation configuration is complete, refer to instructions in the Starting the Monitoring Console in Sun Java Enterprise System 5 Update 1 Monitoring Guide.

Starting and Stopping Portal Server Secure Remote Access

The Secure Remote Access product component of Portal Server offers browser-based secure remote access to portal content and services from any remote device with a Java technology-enabled browser. The Gateway subcomponent presents the content securely from internal web servers and application servers through a single interface to a remote user. Portal Server Secure Remote Access depends on Portal Server and Access Manager or the Access Manager SDK.

After postinstallation configuration is complete, use the following instructions for starting and stopping the Gateway.

To Start Portal Server Secure Remote Access Gateway

1. After installing the Gateway subcomponent and creating the required profile, start the Gateway. For example:

   gateway-install-root/SUNWportal/bin/psadmin start-sra-instance --adminuser \ amadmin --passwordfile /tmp/password --name default --type gateway

   default is the default gateway profile created during installation. You can create your own profiles later, and restart the Gateway with the new profile.

2. Verify that the Gateway is running on the specified port:

   netstat -an | grep port-number

   The default Gateway port is 443.

To Stop Portal Server Secure Remote Access Gateway

1. Stop the Gateway. For example:

   gateway-install-root/SUNWportal/bin/psadmin stop-sra-instance --adminuser / amadmin --passwordfile /tmp/password --name default --type gateway

   This command stops all the Gateway instances that are running on that particular host.

2. Run the following command to check that the Gateway processes are no longer running:

   /usr/bin/ps -ef | grep entsys5i

Stopping and Rebooting Sun Cluster Software

Although Sun Cluster software is not started and stopped like other Java ES 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 Proxy Server

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

To Start Web Proxy Server Administration Server and Instance

1. On the command line, change to WebProxyServer-base/proxy-admserv.

2. Start the Web Proxy Administration Server. For example:

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

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

3. On the command line, change to WebProxyServer-base/proxy-hostname.domainname.

4. Start the Web Proxy Server instance. For example:

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

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

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

   /usr/bin/ps -ef | grep proxy

To Start the Socks Server

1. On the command line, change to WebProxyServer_base/proxy-instance-name.

2. Start the Socks Server:

   ./start-sockd

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

   /usr/bin/ps -ef | grep sockd

To Access the Administration Server Graphical Interface

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.

To Stop Web Proxy Server

1. On the command line, change to WebProxyServer-base/proxy-admserv.

2. Stop the Admin Server. For example:

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

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

3. On the command line, change to WebProxyServer-base/proxy-instance-name.

4. Stop the Web Proxy Server instance. For example:

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

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

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

   /usr/bin/ps -ef | grep proxy

To Stop the Socks Server

1. On the command line, change to WebProxyServer_base/proxy-instance-name.

2. Stop the Socks Server:

   ./stop-sockd

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

   /usr/bin/ps -ef | grep sockd

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.

To Start Web Server

1. Start the Administration Server. For example:

   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 example:

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

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

3. Access the Web Server Administration Server administration instance:

   In a browser window, use 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.

To Stop Web Server

1. Stop the Administration Server. For example:

   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 example:

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

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

Next Steps

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

• All Java ES product documentation: http://docs.sun.com/coll/1286.3

• Sun Cluster System Administration Guide for Solaris OS

• Sun Cluster Data Services Planning and Administration Guide for Solaris OS