Setting Up an Application Server Cluster Node on ps1

This task creates the infrastructure for an Application Server cluster and sets up the first node of that cluster. It consists of the following procedures:

• Install Application Server on ps1

• Start the Application Server Domain on ps1

• Start a Node Agent on ps1

• Create a Cluster Configuration File

• Create and Start an Application Server Instance on ps1

To Install Application Server on ps1

This 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 Setting Up Portal Server on ps1).

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

   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

     • Domain Administration Server

     • Application Server Node Agent

     • Command Line Administration Tool

   • High Availability Session Store 4.4.3 (automatically selected)

   • Java DB 10.2.2.1 (automatically selected)

     • Java DB Client

     • Java DB Server

   • Access Manager 7.1

     • Access Manager SDK

   • 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	Value
    Application Server	/opt/SUNWappserver
    Application Server Data and Configuration	/var/opt/SUNWappserver
    Access Manager	/opt

    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	Value
    Administrator User ID	admin
    Administrator Password	app-server-admin-password

    The Common Server Settings Panel opens.

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

    Input Field	Value
    Host Name	ps1
    DNS Domain Name	pstest.com
    Host IP Address	10.0.2.3
    System User	root
    System Group	root

    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	Value
    HADB Management Port	1862
    HADB Resource Directory	/var/opt
    HADB Administrator Group	root

    The Application Server: Domain Administration Server panel opens.

18. In the Application Server: Domain Administration Server panel, type the following values and click Next.

    Input Field	Value
    Admin Port	4849
    JMX Port	8686
    HTTP Port	8080
    HTTPS Port	8181
    Master Password	app-server-master-password

    The Application Server: Node Agent panel opens.

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

    Input Field	Value
    Admin Host Name	ps1.pstest.com
    Master Password	app-server-master-password
    Admin Port	4849
    Node Agent Name	na-ps1

    The Access Manager: Specify Configuration Information panel opens.

20. In the Access Manager: Specify Configuration Information panel, type the following values and click Next.

    The following values must match the values that were used when Access Manager was installed on am1 and am2).

    Input Field	Value
    Install Type	Legacy Mode
    Administrator User ID	amAdmin
    Administrator Password	access-manager-admin-password
    LDAP User ID	amldapuser
    LDAP Password	access-manager-LDAP-password
    Password Encryption Key	password-enc-key

    The Access Manager: Specify Directory Server panel opens.

21. In the Access Manager: Specify Directory Server Information panel, type the following values and click Next.

    The following values must match the values that were used when Directory Server was installed on ds1 and ds2, except for the host and port values. Those values must match the directory service load balancer values.

    Input Field	Value
    Directory Server Host	ds.pstest.com
    Directory Server Port	389
    Access Manager Directory Root Suffix	dc=pstest,dc=com
    Directory Manager DN	cn=Directory Manager
    Directory Manager Password	directory-manager-password

    The Access Manager: Specify Directory Server Data panel opens.

22. In the Access Manager: Specify Directory Server Data panel, type the following values and click Next.

    Input Field	Value
    Is Directory Server Provisioned With User Data?	Yes
    Organization Marker Object Class	sunISManagedOrganization
    Organization Naming Attribute	o
    User Marker Object Class	inetorgperson
    User Naming Attribute	uid

    The Access Manager: Specify Web Container for Running Access Manager Services panel opens.

23. In the Access Manager: Specify Web Container for Running Access Manager Services panel, type the following values and click Next.

    Input Field	Value
    Remote Host	am.pstest.com
    Services Deployment URI	amserver
    Cookie Domain	.pstest.com
    Remote Services Port	80
    Remote Services Protocol	HTTP

    The Ready to Install panel opens.

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

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

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

27. Click Exit to exit the installer.

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

    # cd /var/sadm/install/logs

    # egrep -i 'fail|error' Java*

To Start the Application Server Domain

This procedure starts a Domain Administration Server (DAS) for the default domain (domain1) and the Application Server instance on ps1 in which it runs.

1. Run the start—domain command:

   # /opt/SUNWappserver/sbin/asadmin start-domain --user admin domain1

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

   The response should indicate that you successfully started the domain:

   Domain domain1 started

To Start a Node Agent on ps1

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

1. Run the start—node—agent command:

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

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

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

   Command start-node-agent executed successfully.

To Create a Cluster Configuration

This procedure creates an Application Server cluster (pscluster) in the default domain (domain1). New Application Server instances will be created as members of this cluster on ps1 and ps2. The cluster configuration file must be created before you create the Application Server instances that constitute the cluster.

1. On ps1, run the create—cluster command:

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

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

   The response should indicate that you successfully created the cluster and its cluster configuration file, pscluster-config:

   Command create-cluster executed successfully.

To Create and Start an Application Server Instance on ps1

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

1. Create an Application Server instance.

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

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

   The response should indicate that you successfully created the instance:

   Command create-instance executed successfully.

2. Start the instance created in Step 1.

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