Central Management Server Status Test
The Central Management Server (CMS) provides and maintains security and configuration information, sends service requests to servers, manages auditing, and maintains the CMS system database. In the event of the failure of the CMS therefore, the operations of all components that make up the SAP BOBI platform can no longer be controlled or co-ordinated, resulting in total chaos! To ensure that the CMS is up and running 24 x 7 and provides uninterrupted security, request routing, and auditing services to the SAP BOBI components, administrators must run the Central Management Server Status test at frequent intervals. This test continuously monitors the availability and processing ability of the CMS and proactively alerts administrators of the probable slowdown/outage of the CMS. In the process, the test enables administrators to swiftly initiate preventive action, so that the potential performance anomalies are kept at bay.
Target of the test : A SAP BOBI Node
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for the CMS running in the node monitored.
Parameter | Description |
---|---|
Test period |
How often should the test be executed. |
Host |
Host name of the server for which the test is to be configured. |
Port |
Enter the port to which the specified host listens. This should be the port at which the web application server hosting SAP BOBI listens. |
JMX Remote Port |
Specify the RMI port number of the BOBI monitoring application. To know the RMI port number of the monitoring application, refer to Enabling the Monitoring Application of the SAP BOBI Platform. |
JNDI Name |
Specify the lookup name for connecting to the JMX connector of the BOBI monitoring application. To know the JNDI name, refer to Enabling the Monitoring Application of the SAP BOBI Platform. |
JMX User and JMX Password |
Enter the credentials of an enterprise authenticated BOBI user belonging to the default monitoring users group. |
Confirm Password |
Confirm the password by retyping it here. |
Node Name |
Specify the name of the BOBI node being monitored. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Health state |
Indicates the current health state of the CMS in the monitored node. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the health state of the server. In the graph of this measure however, the same is represented using the numeric values only. |
||||||||||||||||||
Server running state |
Indicates the current running state of the CMS. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the running state of the server. In the graph of this measure however, the same is represented using the numeric values only. |
||||||||||||||||||
Server enabled state |
Indicates whether/not the CMS is enabled. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not the server is enabled. In the graph of this measure however, the same is represented using the numeric values only. |
||||||||||||||||||
Busy server threads |
Indicates the number of server threads that are currently servicing requests. |
Number |
If this measure reaches the configured maximum thread pool size for the server, new requests to the server would have to wait until a server thread becomes free. If this happens often, it may significantly slowdown request processing by the server. In such a situation, you may want to consider resizing the thread pool. |