Start of Content Area

Procedure documentation Data Request Settings  Locate the document in its SAP Library structure

Use

The server overview displays the host names of the servers available for the Service Data Control Center. You can select servers from which data is to be collected. You can also specify a different server name. This can be useful, for example during a migration, if a server name has changed, and you need to collect data for the old server name.

The data request settings are the default settings for periodic and non-periodic request session data tasks.

 

Procedure

Note

Changing the settings here can cause problems, such as servers not being recognized. You should only make changes here that are strictly necessary.

 

To make changes to the server overview:

       1.      Choose Goto Settings Task-specific.

A hierarchy of task-specific settings is displayed.

       2.      Choose Task-specific Settings Session Data Collection Data request Server overview.

       3.      To display the server overview, click the Settings icon.

A dialog box is displayed, showing the host names of the servers available for the Service Data Control Center.

       4.      To change the settings, choose Display <-> Change.

New Host Name: You can specify a different server name, under which to collect data.

Current Host Name: Displays the real server name.

       5.      Select the servers from which data is to be collected by marking the relevant column.

By default, all servers are selected.

       6.      To save your changes, choose Continue.

 

To change other settings for request session data tasks:

...

       1.      Choose Goto Settings Task-specific.

A hierarchy of task-specific settings is displayed.

       2.      Choose Task-specific Settings Session Data Collection Data request Settings.

       3.      To display the settings for request session data tasks, click the Settings icon.

A dialog box is displayed, showing the settings for periodic and non-periodic request session data tasks.

       4.      To change the settings, choose Display <-> Change.

The task processor settings are described below.

To reapply the default settings, choose Set defaults.

       5.      To save your changes, choose Continue.

 

Scheduling

Repeat every: For periodic sessions, you can define the frequency with which the request session data tasks will be repeated.

Start time: Determines when the request session data task will run.

You can choose a start time that will not impede other system activities. For example, to avoid additional system workload during the day, you can set the task to run at night.

A task will only be processed if the task processor job runs after the start time specified. The task processor job will only process tasks with a start time in the past.

It is therefore recommended that you set the start time of the task processor job to shortly after the start time for request session data tasks.

 

Data Collection

Collect new data if requested data is older than: The length of time that data of a particular type will be retained after collection.

Data that has already been collected can be used for several request session data tasks. Instead of starting a new data collection, suitable existing data can be sent again. This reduces system load.

For periodic sessions, set the period that you require. The default is 3 days, as most of the data used by EarlyWatch Alert is from the previous week (Monday - Sunday).

 

Note

An EarlyWatch Alert can only be scheduled as a periodic session.

 

For non-periodic sessions, use the default setting (3 days).

 

Data request to be performed: Allows a data request to take place a specified number of days before the session.

For example, a session is scheduled to be performed on July 30. The request to collect the system data for that session should be performed 3 days before. Here, the task date will be July 27.

The start time will be taken from the scheduling settings.

To ensure that the correct time frame is analyzed, data is always collected in the calendar week in which the session is scheduled.

This means that if the ‘Data request to be performed’ setting would put the task date before Monday, the task will be performed on the Monday, not earlier.

 

Exception Handling

You can define the number of repeat attempts if an error occurs while processing the task. You can also define the delay between each repeat attempt.

Note that the sum of the repeat intervals must be smaller than the normal scheduled interval. The reason for this is to prevent repeat attempts for failed tasks being made concurrently with normal scheduled tasks. If the cause for a task’s failure is not resolved, every task run will fail, and the task will continue to be scheduled, resulting in an increasing number of failing tasks.

To prevent this issue, the system will not accept repeat attempts that are too frequent.

 

Attributes for Session Data Collection

By default, the option allow approximate session data collection is active.

When data is collected, if the interfaces of the function modules do not match exactly as defined in the service definitions, it is possible to collect data for the parts of the interface that do match. In most cases, this so-called approximate data collection is sufficient for an analysis of the system.

If the option allow approximate session data collection is not active, and the interface does not match exactly, no data at all will be collected by the function module called, and an error message will be written to the log.

Example

Assume that you have an SAP Solution Manager that schedules an EarlyWatch Alert for an SAP Solution Manager session every 7 days. In your managed system, you want the data for this session to be collected at 2 a.m. If any errors occur during data collection, you want to retry 3 times at intervals of 1 hour.

You want as much useful data as possible to be collected. If data is already available, it must not be more than 3 days old to be acceptable.

Proceed as follows:

...

       1.      Configure the exception handling.

Set the number of repeat attempts in the event of an error to 3 at intervals of 1 hour.

       2.      Check that the option allow approximate session data collection is active.

This will ensure that data is collected where matching data exists.

       3.      Set the option Collect new data if requested data is older than to three days.

This will ensure that data will only be collected if existing data is more than 3 days old.

       4.      Set the option Data request to be performed to three days before the session is performed.

       5.      Ensure that the task processor is scheduled to run at least once after 2 a.m.

The task processor will only process tasks that are scheduled in the past.

       6.      Schedule your Maintenance package task before 2 a.m.

This ensures that the Maintenance package task will identify new, scheduled sessions before 2 a.m. The Maintenance package task then schedules the Request session data task to collect data at 2 a.m. The Request session data tasks are already scheduled in the past when the task processor job runs after 2 a.m. The task processor job will then process the Request session data tasks immediately after the 'Maintenance package' task has been processed.

 

See also:

Task Processor Settings

 

End of Content Area