test

Sun Java Enterprise System 5 Update 1 Installation Guide 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:

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.

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