Agents Administration - Tests
 

Default Parameters for BobiCMSWLoadTest

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.

This page depicts the default parameters that need to be configured for the BobiCMSWLoadTest.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • Specify the RMI port number of the BOBI monitoring application in the JMX REMOTE PORT text box. To know the RMI port number of the monitoring application, refer to Monitoring SAP Business Objects document.

  • Specify the lookup name for connecting to the JMX connector of the BOBI monitoring application in the JNDI NAME text box. To know the JNDI name, refer to Monitoring SAP Business Objects document.

  • Enter the credentials of an enterprise authenticated BOBI user belonging to the default monitoring users group in the JMX USER and JMX PASSWORD text boxes.

  • Confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • Specify the name of the BOBI node being monitored in the NODE NAME text box. Note that the NODE NAME parameter is case-sensitive.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.