Configuration of BWWorkBkStatTest

This test auto-discovers the workbooks created on the target SAP Business Warehouse instance and for each workbook, this test reports the number of sessions that initiated the workbook. In addition, this test reports the number of times each workbook was executed and the time taken by each workbook for execution. Using this test, administrators can figure out the workbook that is the slowest to execute. The detailed diagnostics of this test provides in depth insights into the exact query / execution that was the reason behind the workbooks being slow to execute.

The default parameters associated with this test are:

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

• In the HOST text box, specify the HOST for which this test is to be configured.

• In the PORT text box, specify the PORT at which the specified HOST listens.

• In the CLIENTNAME text box, specify the ID of the client system as what the eG agent will be connecting to the SAP ABAP instance. To know how to determine the client ID to use, follow the instructions provided in Determining the Client ID/Name for the eG Agent to Connect to the SAP ABAP Instance.

• Typically, to connect to a SAP ABAP instance and run tests, the eG agent requires the permissions of a SAP user who has been assigned with certain authorization objects, the following authorization objects: S_BGRFC, S_RFC, S_RFC_ADM, S_RFCACL, S_TCODE, S_ADMI_FCD, S_TABU_DIS, S_TABU_NAM, S_USER_GRP, S_XMI_PROD, S_TOOLS_EX, S_APPL_LOG, S_RZL_ADM. Ideally, you will have to create a new user role on the SAP ABAP instance for this purpose, associate the above-mentioned authorization objects with that role, and assign the new role to an existing SAP user. The procedure for the same has been provided in Creating a New User Role for Monitoring and Assigning it to a SAP User. Once the new role is assigned to a SAP user, specify the name of this user against the SAPUSER text box.

• Specify the password of the specified SAPUSER in the PASSWORD text box.

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

• SYSNO is an indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the SysNo will be ‘00’. Similarly, if the SAP server port is 3201, the SYSNO will have to be specified as ‘01’. Therefore, in the SYSNO text box, specify the system number of the SAP server with which the specified client communicates. To know the system number for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number .

• If the SAP client with the specified ClientName exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the router string of the router in the ROUTER text box. If both the client and the server exist in the same network, then specify ‘none’ against the Router text box. To know what is the SAP Router string for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.

• The INSTANCENAME is set to default by default. This implies that the eG agent automatically discovers the instance name at run time. 

• In the TIMEOUT text box, indicate the duration (in seconds) for which this test should wait for a response from the SAP Business Warehouse Instance. By default, this is set to 120 seconds.

• The eG agent uses the SAP JCO library to connect to the SAP ABAP system and pull out metrics. To enable the eG agent to make this connection and query the metrics, you need to specify the version of the SAP JCO library that the agent needs to use. For instance, to instruct the eG agent to use JCO v2.1.19, it would suffice if you specify the ‘major version number’ alone against JCO VERSION - in the case of this example, this will be 2.x. Note that if you have downloaded the SAP JCO CONNECTOR files for SAP JCO version 3 from the SAP market place (as instructed by Downloading the SAP JCO Connector files Required for Monitoring section of the Monitoring SAP ABAP Instance document ), then the JCO VERSION configuration should be 3.x. 

• By default, the BW events related to BW objects such as queries, templates and workbooks will be stored in an event table within the target SAP Business Warehouse Instance. An event record may be logged in the event table upon execution of the query on the workbook either immediately or with a time delay. When the event record is logged with a time delay, eG Enterprise may sometimes miss the event completely from the scope of monitoring. This is because, the event record will display the time stamp at which the event was logged rather than the time stamp at which the event actually started. To ensure that all the events related to the workbooks are monitored, administrators can use the EVENT WINDOW parameter. By default, this is set to 90 minutes indicating that the eG agent will look for the event records in the last 90 minutes and fetch the relevant metrics. This will ensure that the events related to the workbooks are monitored round the clock without a miss!

• The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

• To make diagnosis more efficient and accurate, eG 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, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. 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:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.