Central Management Server Workload Test

The workload of a CMS is typically characterized by queries and user sessions. If a CMS is unable to handle this load, then administrators may have to consider adding more Central Management Servers, so that the workload can be uniformly distributed across all the CMSs. Before taking such strategic decisions however, an administrator should have a clear idea of the current workload of the CMS, should forecast future load trends, and should accurately judge whether/not the CMS can handle its current and future load.

Moreover, user load is also a key indicator of license consumption on the CMS. By measuring the number and nature of users logging into the CMS, administrators can track license usage and plan future license requirements.

Hence, to measure the workload of the CMS from time to time and to understand its many implications, administrators should take the help of the Central Management Server Workload test helps.

This test reports the number and type of sessions that are currently active on the CMS. This way, the test not only highlights the current session load on CMS, but also throws light on license usage. In addition, it reveals the rate at which queries are executed and users login to the CMS, thus enabling administrators to gauge how load will change in time to come. Moreover, the test also measures how quickly the CMS responds to queries and commit operations, thereby indicating how well the CMS is handling its workload. With the help of these metrics, administrators can do the following:

• Decide whether/not more licenses need to be purchased;
• Figure out whether additional CMSs are necessary for improved performance or whether it would suffice to tune the existing CMS and its database.

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.

Configurable parameters for the test

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.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Number of sessions established by concurrent users	Indicates the number of sessions established by users with concurrent user licensing.	Number	By setting appropriate thresholds as per purchased Concurrent Session Based Licenses(CSBL), administrators can detect if a large number of users have logged in and if there is a possibility for subsequent users to be denied system access. In this case, administrators can plan for procuring additional concurrent user licenses.
Number of sessions established by named users	Indicates the number of sessions established by users with named user licensing.	Number	By setting appropriate thresholds as per purchased named licenses, administrators can detect if a large number of users have logged in and if there is a possibility for subsequent users to be denied system access. In this case, administrators can plan for procuring additional named user licenses.
Number of sessions established by servers	Indicates the number of concurrent sessions that BI platform servers have created with the CMS.	Number	If more than 250 sessions have been created by these servers on an average, then an additional CMS may have to created.
Number of sessions established by all users	Indicates the total number of sessions established by users.	Number	This is a good indicator of the user load on the CMS.
Average commit response time since startup	Indicates the average time taken by the CMS to perform commit operations in the CMS system database since the server was started.	Milliseconds	The general rule of thumb is that further analysis and optimization is required if the commit response time starts to exceed 750 milliseconds.
Average query response time since startup	Indicates the average time taken by the CMS to perform query operations in the CMS system database since the server was started.	Milliseconds	The general rule of thumb is that further analysis and optimization is required if the query response time starts to exceed 120000 milliseconds.
Commit rate	Indicates the rate of commits to the CMS system database in the last measure period.	Commits/Sec
Query rate	Indicates the rate of queries executed in the CMS system database in the last measure period.	Queries/Sec	Query rate directly corresponds to the load on the CMS.
Logon rate	Indicates the rate of user logons to the CMS in the last measure period.	Logins/Sec	User logon rate directly corresponds to the load on the CMS.