Web Intelligence Server Activity Test
By observing the level of activity on the Web Intelligence Server over time and by monitoring how the server handles the workload generated by these activities, administrators can quickly figure out whether/not the server possesses the processing power required to service the load. Such useful insights on workload and throughput is provided by the Web Intelligence Server Activity test. This test closely tracks the clients calls made to and sessions created on the Web Intelligence server, reports the rate at which the server executes tasks in response to these calls, and thus indicates how quickly/slowly the server is executing these tasks. Processing bottlenecks on the server can be identified in the process.
Target of the test : A SAP BOBI Node
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of measures for the Web Intelligence Server on the monitored node.
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. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Current number of client calls |
Indicates the current number of CORBA calls that the server is processing. |
Number |
This is a good indicator of the level of client activity on the server. |
Client call rate |
Indicates the rate at which the CORBA calls were received by the server in the last measure period. |
Calls/Sec |
A consistent increase in the value of this measure is indicative of a steady rise in server workload. |
Current number of tasks executed |
Indicates the number of tasks that are currently executed by the server. |
Number |
|
Task execution rate |
Indicates the rate at which the server executes tasks. |
Executions/Sec |
A steady drop in the value of this measure is a cause for concern as it indicates that the server is unable to process tasks as quickly as it receives client calls/requests. This is a sign of a processing bottleneck on the server and requires further investigation. |
Active sessions |
Indicates the number of sessions that are currently able to accept requests from clients. |
Number |
This is a good indicator of the current session load on the server. |
Created sessions |
Indicates the number of sessions that are currently created on the server. |
Number |
|
Session creation rate |
Indicates the rate at which sessions were created. |
Sessions/Sec |
|
Session timeout rate |
Indicates the rate at which sessions timed out. |
Sessions/Sec |
A high timeout rate indicates that sessions are getting timed out very often. You may want to consider changing the Timeout value for sessions to reduce the frequent session logouts. |
Number of users |
Indicates the number of users currently connected to the server. |
Number |
This is a good indicator of the user load on the server. |