Report Application Server Test
The Report Application Server provides ad-hoc reporting capabilities that allow users to create and modify Crystal reports via the SAP Crystal Reports Server Embedded Software Development Kit (SDK). Users will not be able to customize existing reports or create new ones without this server process. Also, if this server is slow, user experience with reports will suffer terribly, destroying user confidence in the SAP BOBI platform. If such adversities are to be avoided, then administrators should be able to capture the failure or slowness of the Report Application server on-the-fly, investigate the reasons for the problem rapidly, and resolve them before end users notice and complain. The Report Application Server test makes this possible! This test keeps track of the health, status, and request processing ability of the Report Application server, and raises an alarm if the server suffers an outage or a slowdown, thus enabling administrators to initiate preventive measures.
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 Report Application server 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 Report Application server in the monitored node. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
If the server is not healthy, then the detailed diagnosis of this measure, if enabled, provides the process ID of the server. 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 Report Application server. |
|
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 Report Application server 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. |
||||||||||||||||||
Current number of auditing events queued |
Indicates the number of auditing events that an auditee has recorded, but which have not yet been retrieved by the CMS Auditor. |
Number |
If this number increases without bound, it could indicate that auditing has not been configured properly or that the system is heavily loaded and generating auditing events faster than the auditor can retrieve them. When stopping servers, it is advisable to disable the servers first and wait for auditing events to be fully retrieved and this queue to become empty. Otherwise, they may be retrieved only when the server has been restarted and the CMS polls for them. |
||||||||||||||||||
Documents being processed |
Indicates the number of documents currently being processed. |
Number |
Document processing corresponds to memory consumption for the report document’s records and impacts sorting and filtering operation performance for the report. |
||||||||||||||||||
Documents processing rate |
Indicates the rate at which documents were processed by the Report application server. |
Docs/Sec |
This is a good indicator of the throughput of the server. A consistent drop in the value of this measure could indicate a processing bottleneck on the server. |
||||||||||||||||||
Threads being processed |
Indicates the number of threads currently being processed by the server. |
Number |
This measure provides an indication of the current load on the server. |
||||||||||||||||||
Thread processing rate |
Indicates the rate of threads processed by the server. |
Threads/Sec |
This is a good indicator of the throughput of the server. A consistent drop in the value of this measure could indicate a processing bottleneck on the server. |