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.

  • In large SAP environments, SAP BOBI installations can have several BI platform server hosts working together in a cluster. A node is a collection of BI platform servers running on the same host and managed by the same Server Intelligence Agent (SIA). One or more nodes can be on a single host. An Adapative Processing Server hosts a lot of BI services and processes non-Object/post processing requests. Multiple APSes may be defined on multiple nodes within a deployment. A single APS acts a primary server to process requests pertaining to the services hosted by the APS from the target SAP BOBI. In some environments, eG Enterprise failed to collect metrics from the target BOBI continuously. This was because, when the APSes failed over, the APS that was acting as a primary server corresponded to a different BOBI node and the eG agent failed to establish connection with the APS that was currently processing the service requests. To ensure that the metrics are collected seamlessly from the target BOBI, the eG agent should be equipped with the IP addresses of the target BOBI node as well as the IP addresses of all the Adaptive Processing Servers associated with the target BOBI node. For this purpose, specify a comma-separated list of IP addresses corresponding to the APSes in the MONITORING HOSTS text box.

  • 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.

  • PROVIDER parameter appears only if the Mode is set to JMX. This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the package name of this JMX Provider in the PROVIDER textbox. By default, this parameter is set to default indicating that this test automatically discovers the JMX provider and report metrics.

  • Specify the maximum duration (in seconds) for which the test will wait for a response from the server in the TIMEOUT textbox. The default TIMEOUT period is 30 seconds.

  • 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.