Configuring the J2EE Engine
Cluster
Purpose
Typically, after installing the necessary cluster configuration and after applying the appropriate template for that configuration (using the Configuration Wizard), you should configure the J2EE Engine cluster optimally for your scenario, hardware resources, and workload.
The additional cluster configuration that you can perform can be divided into two types of configuration:
● Required cluster configuration – this includes the configuration of some additional parameters depending on the size of the J2EE Engine cluster, the expected workload, and so on. Although referred to as “required configuration”, we recommend that you maintain these settings only after careful consideration and testing.
● Optional cluster configuration – perform the procedures described in this section only in case there are some problems within the cluster operation. Otherwise, we recommend that you do not reconfigure the default settings.
Process Flow
Required Cluster Configuration
● Configuring Cluster Elements – follow this procedure to configure the name of the cluster elements and the join port of the server processes.
● Connections Manipulation – follow these procedures to configure the maximum number of user connections that the dispatcher can handle simultaneously and a timeout for establishing these connections.
● Setting Service Load Timeout – follow this procedure to configure the maximum time for which the services on a cluster node have to be started.
Optional Cluster Configuration
● Thread system configuration – to optimize the reallocation of system resources, we recommend that you closely monitor and if necessary, reconfigure the J2EE Engine thread system. For more information, see Thread System.
● Managing the Cluster Elements Startup and Shutdown – use this procedure to configure manner in which the cluster elements will be started up and shut down.
● Configuring the cluster communication mechanisms:
○ Configuring the Message Server Communication
○ Configuring the Session Communication
○ Configuring the Lazy Communication
● Configuring the services stop and event timeouts:
○ Setting Service Stop Timeout