Default Parameters for BWOHDStatTest

This test reports the total requests sent to the open hub destination and the count of lines read by the open hub destination per request. Using this test, administrators can figure out the response time of the open hub destination for each request. Administrators are also pointed to error prone requests so that they can figure out such requests and identify problematic conditions before end users start complaining.

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

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

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

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

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