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

Setting Up an Application Server Cluster Node on ps2

This task creates the second node of an Application Server cluster. It consists of the following procedures:

ProcedureTo Install Application Server on ps2

This procedure is very similar to the procedure for installing Application Server on ps1, except that you do not install the Domain Administration Server (DAS) component on ps2 because only one DAS instance is required in an Application Server cluster.

The procedure assumes that you are installing Java ES components 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 Java ES installation procedure.

The following procedure installs Application Server, HADB, Java DB, and Access Manager SDK, all of which are needed to support Portal Server on this computer, and all of which can be configured using the Java ES installer's Configure Now capability. Installation of Portal Server requires custom configuration and is performed in a subsequent procedure (see To Install Portal Server on ps2).

The 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 these components.

  1. Download the Java ES software distribution to ps2.

    The procedure is documented in To Download the Software Distribution.

  2. Log in as root or become superuser.

    # su -

  3. Start the Java ES installer.

    # cd /portdist_71u2/Solaris_sparc

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

  4. In the Welcome panel, click Next.

    The Software License Agreement panel opens.

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

    The Choose Software Components panel opens.

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

    • Application Server Enterprise Edition 8.2 patch 2

      • Application Server Node Agent

      • Command Line Administration Tool

    • High Availability Session Store 4.4.3 (automatically selected)

    • Java DB (automatically selected)

      • Java DB Client

      • Java DB Server

    • Install Multilingual Package(s) for all selected components (this is selected automatically but optional if using English)

  7. Click Next.

    The Dependency Warning panel opens.

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

    The installer evaluates the Java SE Software Development Kit on the computer and determines if an upgrades is required. On a fresh copy of Solaris 10 8/07 OS, an upgrade is needed, and the Java SE Software Development Kit Upgrade Required panel opens.

  9. In the Java SE Software Development Kit Upgrade Required panel select Automatic Upgrade to the Version Included with the Installer and click Next.

    The installer evaluates the Java ES shared components on the computer and determines if any upgrades are required. On a fresh copy of the Solaris 10 8/07 OS, shared component upgrades are needed, and the Shared Components Upgrades Required panel opens.

  10. In the Shared Components Upgrades Required panel, click Next.

    The installer upgrades the shared components. The Specify Installation Directories panel opens.

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

    Input Field 


    Application Server 


    Application Server Data and Configuration 


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

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

  13. In the Choose a Configuration Type panel, select Configure Now and click Next.

    The Custom Configuration Panel opens.

  14. In the Custom Configuration Panel, note the following message and click Next.

    The following component products cannot be configured during installation:
    Java DB
    Click Next to configure the other components.

    The Specify Administrator Account Preferences panel opens.

  15. In the Specify Administrator Account Preferences Panel, type the following values and click Next.

    Input Field 


    Administrator User ID  


    Administrator Password 


    The Common Server Settings Panel opens.

  16. In the Common Server Settings panel, type the following values and click Next.

    Input Field 


    Host Name 


    DNS Domain Name

    Host IP Address

    System User 


    System Group 


    The High Availability Session Store (HADB) panel opens.

  17. In the Application Server:High Availability Session Store (HADB) panel, type the following values and click Next.

    Input Field 


    HADB Management Port 


    HADB Resource Directory 


    HADB Administrator Group 


    The Application Server: Domain Administration Server panel opens.

  18. In the Application Server: Node Agent panel, type the following values and click Next.

    Input Field 


    Admin Host Name

    Master Password 


    Admin Port 


    Node Agent Name 


    The Ready to Install panel opens.

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

  20. Click Install.

    The installer copies files to the computer. The installer also configures the Access Manager SDK to interoperate with the Access Manager service and the Directory Server service. The installer also creates an instance of the Application Server Domain Administration Server (DAS) for the default Application Server domain, which is domain1.

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

  22. Click Exit to exit the installer.

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

    # cd /var/sadm/install/logs

    # egrep -i 'fail|error' Java*

ProcedureTo Start a Node Agent on ps2

This procedure starts the node agent (na-ps2) on ps2 that was specified during Portal Server installation.

  1. Run the start—node—agent command:

    # /opt/SUNWappserver/sbin/asadmin start-node-agent --user admin na-ps2

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

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

    The response should indicate that you successfully started a node agent:

    Command start-node-agent executed successfully.

ProcedureTo Create and Start an Application Server Instance on ps2

This procedure creates and starts a new Application Server instance (as-cluster-inst-ps2) on ps2, which belongs to pscluster.

  1. Run the create—instance command:

    # /opt/SUNWappserver/sbin/asadmin create-instance --user admin --host --cluster pscluster --nodeagent na-ps2 --systemproperties HTTP_LISTENER_PORT=80 as-cluster-inst-ps2

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

    The response should indicate that you successfully created the instance:

    Command create-instance executed successfully.

  2. Run the start—instance command:

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

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

    The response should indicate that you successfully started the instance:

    Command start-instance executed successfully.