Configuring the Display of DSRs of the Local System

Use

This procedure describes the configuration steps required to display Distributed Statistics Records (DSRs) of the local system in the global workload monitor (transaction ST03G). It is therefore clear that the system requires at least one ABAP instance. The DSR aggregates are physically stored in the local ABAP system.

The following instance types write DSRs that can be displayed in the local ABAP system:

Prerequisites

1. The DSR aggregates are transferred by the relevant sapstartsrv instance agent (more information: Infrastructure of the SAP NetWeaver Management Agents). So that the agent can transfer the data, it requires two profile parameters that you need to set in the profile of every instance that writes DSRs:
   1. Set the profile parameter dsr/loaddsrlib = YES. This instructs the instance agent to load the required program library.
   2. Set the profile parameter dsr/dsrroot = $DIR_LOGGING/dsr. This tells the agent where the instance stores the DSRs.
2. Restart the sapstartsrv of every instance. Depending on the platform, you do this as follows (more information: Restarting SAP NetWeaver Management Agents):
   • Under Microsoft Windows, you restart the agents by restarting the corresponding service SAP<SysID>_<instance number>.
   • Under UNIX, you use the following command:

     sapcontrol -nr <instance number> -function RestartService

3. So that the instance agent can transfer the desired data to the local ABAP Engine using a Web Service, a corresponding logical port must be created. This is done automatically during the run of the report SAPMSSYT. This report runs hourly in the context of background dispatching. Therefore ensure that background dispatching has been activated (more information: Activating and Deactivating Method Execution).
4. In the context of the job SAP_COLLECTOR_FOR_PERFMONITOR, all sapstartsrv instance agents are queried for active DSR components and the results are stored in the local System Component Repository (SCR). If the job has not yet been scheduled, schedule it as follows:
   1. Start transaction SM36.
   2. Choose Standard Jobs.
   3. In the SAP Component input field, select the BC Basis using the possible entries help.
   4. In the Job Name input field, select the entry SAP_COLLECTOR_FOR_PERFMONITOR using the possible entries help.
   5. For the Start Time, choose the radio button Immed., and for the Period, select the Hourly radio button.
   6. Save your settings.
5. The actual transfer of the DSR aggregates is performed during the job SAP_COLLECTOR_FOR_NONE_R3_STAT, which runs hourly. If the job has not yet been scheduled, schedule it in the same way as above.

Once you have restarted the agent, you therefore need to wait for the next runs of three jobs that run hourly before you can display the DSR aggregates in the global workload monitor. You must therefore wait for a maximum of three hours.

Procedure

1. In the local ABAP system, start the Global Workload Monitor in CEN by calling transaction ST03G.
2. In the navigation bar, expand the  Settings & Log tree and double-click the  System Selection entry (see Displaying ABAP Statistics Records for Remote Systems and DSRs).
3. Choose the Systems → Local button. All DSR components that exist in the local SCR are displayed.
4. Use copy and paste to transfer the entries for the components that you want to display in the Global Workload Monitor to your list of monitored systems, and save the list that you have extended in this way, by choosing  (Save) → <desired list>.
5. Ensure that the checkbox in the Activated column is checked for all components for which you wish to display statistical data, and choose the Apply button.

Checking the Entries (Optional)

1. To view the statistical data for one of the activated components, expand the path  Workload →  <component name> in the navigation bar.

More information:

Troubleshooting when Displaying DSRs

 Global Workload Monitor start page