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:
Cleanup Delay (seconds)
. This delay is the amount of time a node waits on startup before attempting to recover work from another engine. The default is 300 seconds.
You can increase this value if you notice that the startup of a cluster node is particularly slow. The slowness may be due to contention between nodes for recovering work. A larger value gives a node a chance to startup before another node contends for its recovery work.
Time Difference Tolerance Warning (seconds)
: The difference in seconds that nodes within a cluster can be out-of-sync with one another before a warning state is set. This lets you detect if the time setting is not in sync between cluster members.
Failover Delay (seconds)
. This delay is the amount of time Process Server waits before triggering failover after a node leaves the cluster. (
Failover
means that work that was in process when the node failed needs to be completed by another server that is currently online.)
After the timeout, Process Server confirms that the node did not rejoin the cluster and still needs failover. Additionally, Process Server issues a warning regarding a likely glitch in cluster communications if a node leaves and rejoins the cluster but the engine itself remained running the whole time. The default delay is 30 seconds.
Automatic Failover Enabled
: When communications to a node are lost, failover occurs automatically.
Log Inbound Cluster Communication
: The server logs all inbound cluster calls, along with relevant data it receives. This information is extremely useful when you are debugging cluster configurations issues.
Log Outbound Cluster Communication
: The server logs all outbound cluster calls, along with relevant data being sent to nodes in cluster. This information is extremely useful when you are debugging cluster configurations issues.
Membership Update Interval
: Indicates how often you want to poll engines in the cluster to ensure they are active. The default value is 30 seconds.
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:
ActiveVOSProvidedUser
. JAAS user created with Monitor rights
ActiveVOSIdentityAssertion
. JAAS user created with Monitor rights and uses the user name and password of the requester to reassert the credentials
JAAS Custom Login
. JAAS user that is available on the WebSphere application server that has at least Monitor rights
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.