Sun Java System Reference Configuration Series: Portal Service on Application Server Cluster

Setting Up Portal Server on ps1

This task consists of the following procedures:

ProcedureTo Install Portal Server on ps1

This procedure assumes that you are installing Portal Server on Solaris 10 8/07 OS or later version. Hence, no operating system patches need to be installed. The Java ES installer evaluates the state of the operating system and indicates if you need to install a patch. If you are using versions of the operating system older than Solaris 10 8/07 OS, it is better to install any required patches before you begin the actual Portal Server installation procedure.

This procedure runs the Java ES installer in Configure Later mode. After installation is complete, you manually configure a Portal Server instance to run in the Application Server cluster instance (as-cluster-inst-ps1).

The following procedure runs the Java ES installer without saving a state file. You can choose to run the installer and capture your input in a state file (-saveState state-filename). You could then use the state file to re-create the installation if, for example, you needed to reinstall Portal Server.

  1. On ps1, navigate to the directory with the unzipped installer.

    # cd /portdist_71u2/Solaris_sparc

  2. Start the Java ES installer.

    # ./installer

    This procedure uses the GUI installer. The installer can also be run in text mode by using the - nodisplay option.

    The Welcome panel opens.

  3. In the Welcome panel, click Next.

    The Software License Agreement panel opens.

  4. In the Software License Agreement Panel, review the license terms and click Yes, Accept License.

    The Choose Software Components panel opens.

  5. In the Choose Software Components panel, select the following components:

    • Portal Server 7.1

      • Netlet Proxy

      • Rewriter Proxy

    • Portal Server Secure Remote Access 7.1

    • Service Registry 3.1

      • Service Registry Client Support

    Unselect Access Manager and Directory Server, which are automatically selected by the installer.

    Note –

    Service Registry is used by Portal Server to support the Web Services for Remote Portals (WSRP) standard, in particular the WSRP producer implementation, which enables the publishing of portlets for use by remote WSRP consumers. Because the dependency on Service Registry is for such a specialized capability, installation of Service Registry is optional. For that reason, Service Registry was not included in the logical and deployment architectures of the reference configuration.

  6. Click Next.

    The Dependency Warning panel opens.

  7. In the Dependency Warning panel, choose Use Access Manager 7.1 Installed on a Remote Machine and click OK.

    The Specify Installation Directories panel opens.

  8. In the Specify Installation Directories panel, type the following values and click Next.

    Input Field 


    Portal Server 


    Service Registry 


    The installer checks the system, and the System Check panel opens.

  9. In the System Check panel, evaluate the results of the system check.

    If the system check is favorable, click Next.

    The Choose a Configuration Type panel opens.

  10. In the Choose a Configuration Type panel, select Configure Later and click Next.

    The Ready to Install Panel opens.

    Note –

    When you select the Configure Later option, Portal Server and Service Registry files will be copied to the computer, but no configuration takes place. You must configure these components after installation is complete.

    For example, the Configure Now option would have automatically deployed Portal Server in the default Domain Administration Server instance. However, you want instead to deploy Portal Server in a clustered Application Server instance. Therefore, you install in Configure Later mode, and subsequently create the Portal Server instance and deploy it to the Application Server cluster instance, as-cluster-inst-ps1.

  11. In the Ready to Install panel, indicate whether you want to open the software registration window during installation.

    This panel enables you to register the components that you have selected for installation with Sun Connection. Sun Connection is a Sun-hosted service that helps you track, organize, and maintain Sun hardware and software. For example, Sun Connection can inform you of the latest available security fixes, recommended updates, and feature enhancements.

    If you choose to register, information about the installation is sent to the Sun Connection database. You can also register at a later date, after installation has been completed.

  12. Click Install.

    The installer copies files to the computer.

  13. When the installation is complete, review the installation in the Summary field.

  14. Click Exit to exit the installer.

  15. Check the installation log files for any installation errors.

    # cd /var/sadm/install/logs

    # egrep -i 'fail|error' Java*

ProcedureTo Create a Portal Server Instance on ps1

This procedure uses the psconfig command and a configuration file to create a portal (pstestPortal) as well as a Portal Server instance (ps-inst-ps1) and a search instance (search-inst-ps1) that are both associated with the portal. The procedure deploys the search instance into the non-cluster Application Server instance on ps1 (as-inst-ps1) and the portal Server instance into all instances in Application Server cluster (pscluster).

You begin with an appropriate example configuration file as a template and edit the file to specify parameter values that are needed for the reference configuration.

  1. Create a config-ps1 configuration file.

    Use the example14.xml file as a template.

    # cd /opt/SUNWportal/samples/psconfig

    # cp example14.xml config-ps1.xml

  2. Open the config-ps1.xml file in a text editor.

  3. Modify config-ps1.xml to use the non-default values in the following table:



    AdministratorUserPassword (@ADMIN.PASSWORD@) 


    LDAPUserIdPassword (@AMLDAP.PASSWORD@) 


    DirectoryManagerPassword (@DIRMGR.PASSWORD@) 




    Host (@HOST.DOMAIN@)

    Port (Search instance) 


    WebContainerInstanceName (Search instance) 


    WebContainerInstanceDir (Search instance) 


    WebContainerDocRoot (Search instance) 


    WebContainerAdminPort (@ADMIN.PORT@) 


    WebContainerAdminPassword (@PASSWORD@) 


    WebContainerMasterPassword (@MASTER.PASSWORD@) 






    InstanceID (Portal Server instance)  


    Port (Portal Server instance) 


    WebContainerInstanceName (Portal Server instance) 


    WebContainerInstanceDir (Portal Server instance) 


    WebContainerDocRoot (Portal Server instance) 


  4. Save the modified config-ps1.xml file.

    The modified file is reproduced in Example Configuration File: Portal Server Instance on ps1.

  5. Run the psconfig command.

    # /opt/SUNWportal/bin/psconfig --config /opt/SUNWportal/samples/psconfig/config-ps1.xml

    The response should resemble the following:

    Successfully created file
    Copying config templates from: /opt/SUNWportal/template/config
    Successfully created file
    Validating the Input Config XML File
    Configuring Cacao Agent for Portal Software
    Configuring Derby Server Instance
    Connecting to Cacao MBean Server
    Creating Portals
    Domain domain1 started
    Successfully created Portal: pstestPortal
    Configuring Samples

ProcedureTo Modify the Configuration of the Portal Server Instance on ps1

The previous procedure deployed Portal Server by using pscluster as the target Application Server instance. The entry, however, needs to be targeted to as-cluster-inst-ps1, rather than to the cluster. The following procedure removes this entry from the pscluster configuration and adds it to the as-cluster-inst-ps1 configuration.

  1. Remove the entry from the cluster configuration.

    # /opt/SUNWappserver/sbin/asadmin delete-jvm-options --user admin --target pscluster ""

    When prompted, type the app-server-admin-password.

    The response should indicate that you successfully removed the instance from the cluster configuration:

    Command delete-jvm-options executed successfully.

  2. Add the entry to the as-cluster-inst-ps1 configuration.

    # /opt/SUNWappserver/sbin/asadmin create-system-properties --user admin --target as-cluster-inst-ps1

    When prompted, type the app-server-admin-password.

    The response should indicate that you successfully added Portal Server instance information to the Application Server instance on ps1:

    Command create-system-properties executed successfully.

  3. Restart the pscluster cluster.

    The cluster needs to be restarted for changes in configuration to take effect.

    # /opt/SUNWappserver/sbin/asadmin stop-cluster --user admin pscluster

    # /opt/SUNWappserver/sbin/asadmin start-cluster --user admin pscluster

ProcedureTo Start and Verify Portal Server on ps1

You start the Portal Server instance by restarting the Application Server instance (as-cluster-inst-ps1) in which it is deployed. You then verify that the instance is running by accessing the portal Welcome page in a browser.

  1. Stop the Application Server instance.

    # /opt/SUNWappserver/sbin/asadmin stop-instance --user admin as-cluster-inst-ps1

    When prompted, type the app-server-admin-password.

    The response should indicate that you successfully stopped the instance:

    Command stop-instance executed successfully.

  2. Restart the Application Server instance.

    # /opt/SUNWappserver/sbin/asadmin start-instance --user admin as-cluster-inst-ps1

    When prompted, type the app-server-admin-password.

    The response should indicate that you successfully started the instance:

    Command start-instance executed successfully.

  3. Verify that the Portal Server instance is running.

    1. Start a browser.

    2. Go to the following URL:

      The portal Welcome page opens, confirming that your Portal Server instance is running.