Cluster Manager enables the communication between nodes in the cluster. It integrates new nodes and notifies the modules installed on each node when a node is removed. It runs on both dispatchers and servers.
|
|
Dispatcher |
|
|
Property |
Description |
Default Value |
|
|
|
|
|
JoinPort |
The dispatcher listens for connections on this port. |
2077 |
|
TcpNoDelay |
This property takes a Boolean value that specifies if Nagle’s algorithm is disabled or enabled for this socket. Setting TcpNoDelay to “true” improves system performance especially when multiple small portions of data are sent through the socket. |
True |
|
MemoryElement |
This property specifies the way of saving information. If set to “true,” the information about service processes is not written in files and saved on the hard disk; it is available only at the current moment and when server is stopped, this information is lost. |
False |
|
ClusterHosts |
This parameter specifies the SAP J2EE Engine 6.20 Cluster hosts to which the dispatcher must try to connect, and the corresponding ports on which these hosts listen for connections. 2078 is the default JoinPort for Server One. Ports 2062, 2063, 2064 and 2065 are specified as default JoinPorts for dispatcher2, dispatcher3, dispatcher4 and dispatcher5, which can be added to SAP J2EE Engine 6.20 Cluster with the Config Tool provided. |
localhost\:2078;localhost\:2062;localhost\:2063;localhost\:2064;localhost\:2065 |
|
ClusterElementId |
This parameter specifies the identification number of a cluster element (dispatcher). The ID is unique for the cluster. |
5001 |
|
ClusterElementName |
Specifies the name of a cluster element (dispatcher). |
Dispatcher One |
|
ClusterName |
Specifies the name of SAP J2EE Engine 6.20 Cluster. |
SAP J2EEngine Cluster |
|
OpenPort |
Through this port, connections between cluster elements are established. |
2055 |
|
Gateway |
This property has a boolean value. It is used when the dispatcher node runs in a SAP J2EE Engine box to specify if the node is a gateway. |
false |
|
RepeatToConnect |
This property has a boolean value that indicates if cluster element (dispatcher) must retry to connect to a specified host if the first attempt fails. If set to “true,” the cluster element retries until connection is established. |
false |
|
InfoLogFileName |
Specifies the filename to which info log messages for Cluster Manager are written. |
./managers/log
/cluster/INFO.log |
|
DebugLogFileName |
Specifies the filename to which debug log messages for Cluster Manager are written. |
./managers/log
/cluster/DEBUG.log |
|
NoticeLogFileName |
Specifies the filename to which notice log messages for Cluster Manager are written. |
./managers/log /cluster/NOTICE.log |
|
WarningLogFileName |
Specifies the filename to which warning log messages for Cluster Manager are written. |
./managers/log /cluster/WARNING.log |
|
NormalLogLevel |
Specifies the types of log messages that have normal priority. It is a number from 0 to 7 specifying that log messages within [0,NormalLogLevel] are written in the DefaultNormalFile. For example, if NormalLogLevel is set to 4, log messages that are in [0,4] are written to the DefaultNormalFile, and the rest to the DefaultCriticalFile. |
5 |
|
NormalLogFileName |
This parameter specifies the filename to which messages with normal priority are written. This file is used by the Log viewer of the system to display the messages. |
DEFAULT.log |
|
AlertLogFileName |
Specifies the filename to which alert log messages are written. |
./managers/log /ALERT.log |
|
CriticalLogLevel |
Specifies the types of log messages that have critical priority. It is a number from 0 to 7 specifying that log messages within [CriticalLogLevel,7] are written in the DefaultCriticalFile. |
3 |
|
CriticalLogFileName |
Specifies the filename to which critical log messages are written. |
./managers/log
/CRITICAL.log |
|
ErrorLogFileName |
Specifies the filename to which error log messages are written. |
./managers/log /ERROR.log |
|
EmergencyLogFileName |
Specifies the filename to which emergency log messages are written. |
./managers/log
/EMERGENCY.log |
|
|
|
|
|
|
Server |
|
|
Property |
Description |
Default Value |
|
|
|
|
|
JoinPort |
The server listens for connections on this port. |
2078 |
|
TcpNoDelay |
This property takes a Boolean value that specifies if Nagle’s algorithm is disabled or enabled for this socket. Setting TcpNoDelay to “true” improves system performance especially when multiple small portions of data are sent through the socket. |
True |
|
MemoryElement |
Specifies the way of saving information on the server. If set to “true” the information about service processes is not written in files and saved on the hard disk; it is available only at the current moment, and when server is stopped, this information is lost. |
false |
|
ClusterHosts |
This parameter specifies the SAP J2EE Engine 6.20 Cluster hosts to which the server mustl try to connect and the corresponding ports on which these hosts listen for connections. Port 2077 is the default JoinPort for Dispatcher One. Ports 2062, 2063, 2064 and 2065 are specified as default JoinPorts for dispatcher2, dispatcher3, dispatcher4 and dispatcher5, which can be added to SAP J2EE Engine 6.20 Cluster with the Configuration Tool provided. |
localhost\:2077; localhost\:2062; localhost\:2063; localhost\:2064; localhost\:2065 |
|
ClusterElementId |
This parameter specifies the identification number of a cluster element (server). The ID is unique for the cluster. |
4001 |
|
ClusterElementName |
Specifies the name of a cluster element (server). |
Server One |
|
ClusterName |
Specifies the name of SAP J2EE Engine 6.20 Cluster. |
SAP J2EEngine Cluster |
|
OpenPort |
Through this port, connections between cluster elements are established. |
2056 |
|
Gateway |
This property has a boolean value. It is used when the server node runs in a SAP J2EE Engine box to specify if the node is a gateway. |
false |
|
DependentElement |
This property has a boolean value that specifies if a particular server element is a primary or non-primary server. If the value is “false,” the element is primary storage server – that is, it stores the data to be replicated on other server nodes in the cluster. |
false |
|
RepeatToConnect |
This property has a boolean value that indicates if cluster element (server) must retry to connect to a specified host if the first attempt fails. If set to “true,” the cluster element retries until connection is established. |
false |
|
InfoLogFileName |
Specifies the filename to which info log messages for Cluster Manager are written |
./managers/log
/cluster/INFO.log |
|
DebugLogFileName |
Specifies the filename to which debug log messages for Cluster Manager are written. |
./managers/log
/cluster/DEBUG.log |
|
NoticeLogFileName |
Specifies the filename to which notice log messages for Cluster Manager are written. |
./managers/log /cluster/NOTICE.log |
|
WarningLogFileName |
Specifies the filename to which warning log messages for Cluster Manager are written. |
./managers/log /cluster/WARNING.log |
|
NormalLogLevel |
Specifies the types of log messages that have normal priority. It is a number from 0 to 7 specifying that log messages within [0,NormalLogLevel] are written in the DefaultNormalFile. For example, if NormalLogLevel is set to 4, log messages that are in [0,4] are written to the DefaultNormalFile, and the rest to the DefaultCriticalFile. |
5 |
|
NormalLogFileName |
This parameter specifies the filename to which messages with normal priority are written. This file is used by the Log viewer of the system to display the messages. |
DEFAULT.log |
|
AlertLogFileName |
Specifies the filename to which only alert log messages are written. |
./managers/log /ALERT.log |
|
CriticalLogLevel |
Specifies the types of log messages that have critical priority. It is a number from 0 to 7 specifying that log messages within [CriticalLogLevel,7] are written in the DefaultCriticalFile. |
3 |
|
CriticalLogFileName |
Specifies the filename to which critical log messages are written. |
./managers/log
/CRITICAL.log |
|
ErrorLogFileName |
Specifies the filename to which error log messages are written. |
./managers/log /ERROR.log |
|
EmergencyLogFileName |
Specifies the filename to which emergency log messages are written. |
./managers/log
/EMERGENCY.log |
|
|
|
|
|
|
Stand-Alone |
|
|
|
Property |
Description |
Default Value |
|
|
|
|
|
|
|
JoinAPort |
The stand-alone server part listens for connections on this port. |
2077 |
|
|
JoinCPort |
The stand-alone dispatcher part listens for connections on this port. |
1077 |
|
|
ClusterElementIdA |
This parameter specifies the identification number of the stand-alone Server part. The ID is unique for this configuration. |
1001 |
|
|
ClusterElementIdC |
This parameter specifies the identification number of the stand-alone dispatcher part. The ID is unique for this configuration. |
2001 |
|
|
ClusterElementNameA |
Specifies the name of stand-alone part responsible for requests processing. |
Server One |
|
|
ClusterElementNameC |
Specifies the name of stand-alone part responsible for requests accepting and delivering. |
Dispatcher One |
|
|
OpenAPort |
Through this port, connections between stand-alone parts are established. |
13550 |
|
|
OpenCPort |
Through this port, connections between stand-alone parts are established. |
12550 |
|
|
MemoryElement |
Specifies the way of saving information on the server. If set to “true,” the information about service processes is not written in files and saved on the hard disk; it is available only at the current moment, and when the server is stopped, this information is lost. |
false |
|
|
ClusterHostsA |
This parameter specifies the SAP J2EE Engine 6.20 stand-alone version host, to which stand-alone server module must try to connect, and the corresponding port on which this host listens for connections. |
127.0.0.1:1777 |
|
|
ClusterHostsC |
This parameter specifies the SAP J2EE Engine 6.20 stand-alone version host, to which the stand-alone dispatcher module must try to connect. |
|
|
|
RepeatToConnect |
This property has a boolean value that indicates if the stand-alone element must retry to connect to a specified host if the first attempt fails. If set to “true,” the stand-alone element retries until connection is established. |
false |
|
|
ConnectAttemptsCount |
If RepeatToConnect property is set to “true,” this paramater specifies the number of attempts to connect to the specified host that the stand-alone element makes if the first attempt has failed. |
0 |
|
|
ClusterName |
Specifies the name of the SAP J2EE Engine 6.20 Cluster. |
SAP J2EEngine Cluster |
|
|
InfoLogFileName |
Specifies the filename to which info log messages for Cluster Manager are written. |
./managers/log /cluster/INFO.log |
|
|
NoticeLogFileName |
Specifies the filename to which notice log messages for Cluster Manager are written. |
./managers/log /cluster/NOTICE.log |
|
|
WarningLogFileName |
Specifies the filename to which warning log messages for Cluster Manager are written.
|
./managers/log /cluster/WARNING.log |
|
|
DebugLogFileName |
Specifies the filename to which debug log messages for Cluster Manager are written. |
./managers/log /cluster/DEBUG.log |
|
|
NormalLogLevel |
Specifies the types of log messages that have normal priority. It is a number from 0 to 7 specifying that log messages within [0,NormalLogLevel] are written in the DefaultNormalFile. For example, if NormalLogLevel is set to 4, log messages that are in [0,4] are written to the DefaultNormalFile, and the rest to the DefaultCriticalFile. |
5 |
|
|
NormalLogFileName |
This parameter specifies the filename to which messages with normal priority are written. This file is used by the Log viewer of the system to display the messages. |
DEFAULT.log |
|
|
AlertLogFileName |
Specifies the filename to which alert log messages are written. |
./managers/log /ALERT.log |
|
|
CriticalLogLevel |
Specifies the types of log messages that have critical priority. It is a number from 0 to 7 specifying that log messages within [CriticalLogLevel,7] are written in the DefaultCriticalFile. |
3 |
|
|
CriticalLogFileName |
Specifies the filename to which critical log messages are written. |
./managers/log
/CRITICAL.log |
|
|
ErrorLogFileName |
Specifies the filename to which error log messages are written. |
./managers/log /ERROR.log |
|
|
EmergencyLogFileName |
Specifies the filename to which emergency log messages are written. |
./managers/log
/EMERGENCY.log |
|
../cluster/dispatcher/managers/settings/ClusterManager.properties
Cluster Manager properties specified in the
Visual Administration
section can be set from this file as well.
../cluster/server/managers/settings/ClusterManager.properties
Cluster Manager properties specified in the
Visual Administration
section can be set from this file as well.
../alone/managers/settings/ClusterManager.properties
Cluster Manager properties specified in the
Visual Administration
section can be set from this file as well.
You must configure Cluster Manager correctly for SAP J2EE Engine 6.20 to function properly.
When adding a new node, you must change its ID because the identification number must be unique for the cluster. If the new node is set with an existing ID, it cannot be added. It is also recommended, although not necessary, that you change the name of the added node to avoid confusion.
When starting a node, you must check if the ports specified as JoinPort and OpenPort are available. If they are already taken, the new node cannot connect to the dispatcher.