Administration Console > Admin > Cluster
  

Cluster

Process Server supports clusters of Process Servers operating with a single persistent process store. Multiple process servers share a set of process instances and their deployments.
Two main features of a clustered environment are load balancing and fail over. Load balancing allows processes to be routed to the server in the process cluster with the least load. Fail over allows servers to pick up the load of a failed server in the process cluster.
The following figure shows the Cluster page and the Detail page that is displayed if you click on a link in the Cluster page.
Cluster and Cluster Detail pages
Clicking either of an engine's links displays the Engine Detail page, which has the following information:
Field
Explanation
ID
ID assigned to the cluster node by the Process Server engine
Name
Computer IP address and port where the engine instance is running
Start Time
Date and time the engine started
Status
Statuses include Running and Stopped
No. CPUs
Number that is based on licenses. Select the number of CPUs to view the Engine Detail page, where you can update the number. Then view the Admin > License page to verify that the number of licenses matches the number of CPUs.
Process Server reports an estimated number of CPUs based on the information it gathers from the computer. The number may not be accurate if the computer is using CPU hyper-threading technology.
Stopping this Engine
Press the Stop Engine button to stop this engine. To stop all engines in the cluster, stop the cluster on the Home page. For details, see Server Status
Updating the CPU Count
  1. 1. Click on a link within the Cluster page for the engine being updated.
  2. 2. Stop the engine.
  3. 3. Update the number of CPUs in your cluster.
  4. 4. Select Update.
  5. 5. Restart the engine.

WebSphere Cluster Properties

If you are using WebSphere, use the Cluster Properties page to set WebSphere Cluster properties. (Other engines will show different properties.)
The following are WebSphere cluster properties:
You can add the name of the WebSphere application server JAAS login for cluster communications.
If your WebSphere application server is running with global security enabled, you can provide or update the JAAS username. Process Server uses this name when performing cluster communications. You can choose from the following:
In WebSphere, you can also set a Communications Time Out value for Process Server to send and receive communications to and from engines in the cluster. The default value is 180 seconds.

WebLogic Properties

You can set a Membership Update Interval to indicate how often you want to poll engines in the cluster to ensure they are active. The default value is 30 seconds.