Configuration of AsAbapWorkTest

Work processes execute the individual dialog steps in SAP ABAP applications. For each type of work process, this test reports the numerical statistics of the work processes in various states. In addition, this test helps administrators in analyzing the CPU utilization of the work processes so that resource intensive work processes can be identified. This way, administrators may figure out how well the work processes are utilized in the target environment and what is really causing the slowdown of the environment - is it due to the unavailability of free work processes? or are too many work processes on hold or in PRIV mode?

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.

• Specify the the host name of the server for which the test is to be configured in the HOST text box.

• Specify the port number at which the specified HOST listens in the PORT text box.

• Set the USE SAPCONTROL flag to Yes if you want the test to use the SAPControl web service for collecting metrics. Set this flag to No if you want the test to use the SAPJCO to report metrics. By default, this flag is set to Yes.

• The WSDL PORT parameter appears only if the USE SAPCONTROL flag is set to Yes – i.e., if the test uses the SAPControl web service for collecting measures. In this text box, specify the port number of the SAPControl web service. To determine the exact port number of the SAPControl web service, you can look up the etc/services file on the SAP ABAP system being monitored. If the port number is not declared in the etc/services file, you can specify the default port number of the web service against WSDL PORT. If the web service is not SSL-enabled, then the default port number of the web service will be: 5<NR>13. Similarly, if the web service is SSL-enabled, then the default port number of the web service will be: 5<NR>14. <NR> in the port number refers to the system number of the SAP server being monitored. The system number 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 system number will be ‘00’. Similarly, if the SAP server port is 3201, the system number will have to be specified as ‘01’. Accordingly, the default port number of an SSL-enabled SAPControl web service will be 50014, if the system number is 00, or 50114, if the system number is 01.

• The OS USERNAME and OS PASSWORD parameters appear only if the USE SAPCONTROL flag is set to Yes – i.e., if the test uses the SAPControl web service for collecting measures. To enable the test to access the SAPControl web service, you need to configure the OS USERNAME and OS PASSWORD parameters of the test with the credentials (i.e., name and password) of an OS user, who fulfills one of the following conditions:

  • The name of the OS user should be declared using the service\admin_users profile parameter; (OR)

  • The name of the user group to which the OS user belongs should be declared using the service\admin_groups profile parameter; (OR)

  • The OS user should have the permission to execute the sapstartsrv executable

• The CONFIRM PASSWORD parameter appears only if the USE SAPCONTROL flag is set to Yes – i.e., if the test uses the SAPControl web service for collecting measures. Confirm the OS PASSWORD by retyping it here.

• The SSL parameter appears only if the USE SAPCONTROL flag is set to Yes – i.e., if the test uses the SAPControl web service for collecting measures. Set this flag to Yes, if the SAPControl web service is SSL-enabled. Set this flag to No, if the SAPControl web service is not SSL-enabled.

• The CLIENTNAME parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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, Click Here.

• The INSTANCENAME parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. In the INSTANCENAME text box, specify the name of the SAP ABAP instance to be monitored. To figure out the name of the monitored instance, Click Here.

• The TIMEOUT parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. In the TIMEOUT text box, indicate the duration (in seconds) for which this test should wait for a response from the SAP ABAP instance. By default, this is set to 120 seconds.

• The SAPUSER parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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 the following privileges: S_RFC, S_TABU_DIS, S_XMI_PROD, S_TOOLS_EX, 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 privileges with that role, and assign the new role to an existing SAP user. To know how to create the SAP user, Click Here. Once the new role is assigned to a SAP user, specify the name of this user against SAPUSER.

• The PASSWORD parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. The PASSWORD text box indicates the password of the specified SAPUSER.

• The CONFIRM PASSWORD parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• The SYSNO parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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, Click Here.

• The ROUTER parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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, Click Here.

• The JCO VERSION parameter appears only if the USE SAPCONTROL flag is set to No – i.e., if the test uses SAPJCO to collect measures. 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 API files for SAP JCO version 3 from the SAP market place, then the JCO VERSION configuration should be 3.x.

• Specify the time duration in minutes beyond which a dialog work process is classified as a long running work process in the LONG RUNNING DIA STEP(MINS) text box. By default, this value is 10 minutes. If the dialog work process is running beyond the specified cutoff duration, the details about the long running dialog work process will be displayed in detailed diagnosis of the longrunning measure.

• Specify the time duration in hours beyond which a background work process is classified as a long running work process in the LONG RUNNING BGD STEP(HRS) text box. By default, this value is 24 hours. If the background work process is running for a duration longer than the specified cutoff time, the details about the long running background work process will be displayed in detailed diagnosis of the longrunning measure.

• Specify the time duration in minutes beyond which a enqeue work process is identified as a long running work process in the LONG RUNNING ENQ STEP(MINS) text box. By default, this value is 60 minutes. If the enqueue work process is running for a duration longer than the specified cutoff time, the details about the long running enqueue work process will be displayed in detailed diagnosis of the longrunning measure.

• Specify the time duration in minutes beyond which a spool work process is classified as a long running work process in the LONG RUNNING SPO STEP(MINS) text box. By default, this value is 5 minutes. If the spool work process is running for a duration longer than the specified cutoff time, the details about the long running spool work process will be displayed in detailed diagnosis of the longrunning measure.

• Specify the time duration in minutes beyond which a update work process is classified as a long running work process in the LONG RUNNING UPD STEP(MINS) text box. By default, this value is 5 minutes. If the update work process is running for a duration longer than the specified cutoff time, the details about the long running update work process will be displayed in detailed diagnosis of the longrunning measure.

• Specify the time duration in minutes beyond which a update type 2 work process is classified as a long running work process in the LONG RUNNING UP2 STEP(MINS) text box. By default, this value is 5 minutes. If the update type 2 work process is running for a duration longer than the specified cutoff time, the details about the long running update type 2 work process will be displayed in detailed diagnosis of the Long running work processes measure.

• 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, the eG Enterprise suite 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 for a particular server, choose the On option. 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 normal and abnormal 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.