How To Create a Sun Java Enterprise System Application Server Cluster

A cluster appears to clients as a single Application Server instance. The server instances that constitute a cluster can run on the same machine, or can be located on different machines. Each cluster member in a cluster must run the same version of Application Server.

A cluster provides:

• Increase application availability with the server's failover capabilities.

• Increase throughput by scaling applications across multiple servers.

Before You Begin

Before you create a cluster, you must create an Application Server domain and an Domain Administration Server.

To create a cluster, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.

Steps

1. From the Common Tasks section in the browser interface, click Sun Java System AS 8.

2. Under SJSAS 8.1 AppServer infrastructure->SJSAS 8.1 clusters click Manage.

3. Under Component Procedures click the Run action next to default: install.

4. In the Plan Parameters area, select the variable settings for the cluster you want to install.

   • If the variable settings have been established for this component, select the appropriate settings from the menu.

   • If the settings are not available from the menu, click Select From List.

     The Select Variable Settings From List window displays.

     • To create a new set of variable settings, select Create Set.

       The following list provides commonly-updated variables for the Install component.

       variable set name

       Required. A name for the new variable set you create.

       installIdentifier

       A unique ID to associate domains, clusters, node agents, and Application Server instances with an Install component.

       domainName

       The domain name in which this cluster will be located

       targetName

       The name of the cluster.

       portRangePrefix

       The HTTP port range prefix. For example, a value of 100 means the HTTP port range begin with 10000. The default value is 100.

       httpListenerPort

       The HTTP listener port, used with portRangePrefix. The valid range is 1–65553. For port numbers 1–1024, superuser permissions are required. The default is portRangePrefix plus 00. If portRangePrefix is set to 100, the HTTP listener port is 10000.

       httpsListenerPort

       The HTTPS listener port, used with portRangePrefix. The valid range is 1–65553. For port numbers 1–1024, superuser permissions are required. The default is portRangePrefix plus 05. If portRangePrefix is set to 100, the HTTPS listener port is 10005.

       iiopListenerPort

       The Internet Inter-Orb Protocol (IIOP) listener port, used with portRangePrefix. The valid range is 1–65553. For port numbers 1–1024, superuser permissions are required. The default is portRangePrefix plus 10. If portRangePrefix is set to 100, the IIOP listener port is 10010.

       iiopsslListenerPort

       The SSL-enabled Internet Inter-Orb Protocol (IIOP) listener port, used with portRangePrefix. The valid range is 1–65553. For port numbers 1–1024, superuser permissions are required. The default is portRangePrefix plus 15. If portRangePrefix is set to 100, the secure IIOP listener port is 10015.

       iiopsslmutualauthPort

       The SSL-enabled Internet Inter-Orb Protocol (IIOP) listener port for mutual authorization, used with portRangePrefix. The valid range is 1–65553. For port numbers 1–1024, superuser permissions are required. The default is portRangePrefix plus 20. If portRangePrefix is set to 100, the mutual authorization secure IIOP listener port is 10020.

       jmsConnectorPort

       The port on which the Java Messaging Service (JMS) connector listens. The valid range is 1–65553. For port numbers 1–1024, superuser permissions are required. The default is portRangePrefix plus 25. If portRangePrefix is set to 100, the JMS connector port is 10025.

       httpLoadBalancer

       If true, applications deployed to this cluster will be load balanced. The default is false.

       httpsLoadBalancer

       If true, applications responding to HTTPS requests will be load balanced. This variable has no effect if httpLoadBalancer is false. The default is false.

       routeCookie

       If true, the load balancer will route cookies. This variable has no effect if httpLoadBalancer is false. The default is false.

     • To use variable components from another component, click Import Set.

       For more information about importing variable sets, see “How to Run a Plan” in N1 Grid Service Provisioning System 5.0 Operation and Provisioning Guide.

5. Select the target host.

   Install the cluster on the Remote Agent.

6. Deselect the Target Host Set checkbox.

7. If you want to run a detailed check (preflight) before installing, select Perform Detailed Preflight.

8. Click Run Plan (includes preflight).