To Verify Sun Java System Portal Server 7.2 Installation

1. Start Directory Server, web container, and Gateway.

2. Access Portal Server. For example, type the URL in the browser.

   http://host.domain-name:port/portal-URI

   The Welcome page appears. The page displays a short description of Portal server and links to sample portals that you selected for installation. Click on one of the links and access the anonymous portal desktop for the sample portal. If the sample portal desktop displays without exception, your Portal Server installation was successful.

3. Type http://host.domain-name:port/psconsole.

4. Verify whether Java DB process is running.

   netsatat -an | grep 1527

   If Java DB is not running, start Java DB. For more information, refer to To Start and Stop Java DB

5. Check whether the Common Agent Container is running.

   On the Solaris platform, type the following:

   /usr/sbin/cacaoadm status

   This command should return the PIDs for running the Common Agent Container processes.

   On the Linux platform, type the following:

   /opt/sun/cacao/bin/cacaoadm status

   If the Common Agent Container is not running, restart it.

   On the Solaris platform, type the following:

   /usr/sbin/cacaoadm stop /usr/sbin/cacaoadm start

   On the Linux platform, type the following:

   /opt/sun/cacao/bin/cacaoadm stop /opt/sun/cacao/bin/cacaoadm start

   ---

   Note –

   By default, Common Agent Container creates a self-signed CA certificate and uses it to sign the server certificate of the Common Agent Container agent. The subject DN of this server certificate is CN=hostname_agent (or CN=hostname_default_agent on Microsoft Windows). When this default server certificate is to be replaced by another server certificate signed by the CA of the user's choice, the subject DN of the new server certificate must be kept the same as the original one for Portal Server administration to continue function without interruption.

   ---

6. Verify whether Directory Server is running using the following commands:

   netstat -an | grep 389

   If it is not running, start the Directory Server using the following command:

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

7. Verify whether the Application Server 9.1 is running using the following command:

   netstat -an | grep 8080

   If it is not running, start the server using the following command:

   /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin domain1

8. Run the following command to check if the Gateway is running on the specified port (the default port is 443):

   netstat -an | grep 443

   If the Gateway is not running, do the following:

   psadmin switch-sra-status -u amadmin -f password-file on

   PortalServer-base/bin/psadmin provision-sra -u amadmin -f amadmin-password-file --gateway-profile gateway-profile -p portal-id --enable

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

   1. Create a file and add the amadmin password in plaint text.

   2. Also view the log files. The log file name is picked up from the property called debug.com.sun.portal.handler.java.util.logging.FileHandler.pattern in the platform.conf file.

9. Access Portal Server in secure mode by typing the Gateway URL in your browser:

   https://gateway-machine-name:443

   If you chose a different port number other than the default port (443) during installation, you need not specify that port number.