Task

Recommended Frequency

Detailed Description

Archiving messages:

SAP_BC_XMB_ARCHIVE<client>

Once a day

This job moves messages to be archived to the archive and deletes archived messages from the database.

Schedule this job with transaction SXMB_ADM (Schedule Archive Jobs).

See Defining Interfaces and Retention Periods for Archiving and Archiving and Deleting.

Alternatively, you can schedule job SAP_SOA_ARCHIVE_PLAN using transaction SM36.

Note that only one of the two alternative jobs, SAP_BC_XMB_ARCHIVE<client> (transaction SXMB_ADM) or SAP_SOA_ARCHIVE_PLAN (transaction SM36), needs to be scheduled.

Deletion of messages and message table:

SAP_BC_XMB_DELETE_<client>

Once a day

This job is used to delete individual messages. It can also be used to delete all messages from a table by deleting the whole table and creating it again. Individual messages that cannot be deleted are saved in a temporary table in the meantime.

Schedule this job with transaction SXMB_ADM (Schedule Deletion Jobs).

See Archiving and Deleting.

Alternatively, you can schedule job SAP_SOA_DELETE_MESSAGES or SAP_SOA_TABLE_SWITCH using transaction SM36.

Either schedule job SAP_BC_XMB_DELETE_<client> (transaction SXMB_ADM) or the two jobs SAP_SOA_DELETE_MESSAGES (transaction SM36) and SAP_SOA_TABLE_SWITCH (transaction SM36).

Deletion of history data:

SAP_BC_XMB_HIST_DELETE_<client>

Once a week

This job is used to delete history data.

History data consists of a small amount of header information from deleted messages. It is stored in a separate table with a minimum retention period of seven days.

Schedule this job with transaction SXMB_ADM (Schedule Deletion Jobs).

See Archiving and Deleting.

Alternatively, you can schedule job SAP_SOA_DELETE_HISTORY using transaction SM36.

Note that only one of the two alternative jobs, SAP_BC_XMB_HIST_DELETE_<client> (transaction SXMB_ADM) or SAP_SOA_DELETE_HISTORY (transaction SM36), needs to be scheduled.

Cache update/refresh

With the release of change lists, a cache update job is automatically started in a background task.

Message queue processing

Is automatically started by the qRFC scheduler. Standard procedures regarding housekeeping of qRFC tables apply.

Monitoring error situations of processes:

SWWERRE

Every 3 minutes

This job is automatically scheduled by transaction SWF_XI_CUSTOMIZING.

It is very important that this task is scheduled for the Business Process Engine (BPE). The frequency can be changed by using transaction SWWD.

Monitoring of deadlines for processes:

SWWDHEX

Every 3 minutes

This job is automatically scheduled by transaction SWF_XI_CUSTOMIZING.

It is very important that this task is scheduled for the BPE. The frequency can be changed by using transaction SWWA.

Managing the correct processing of the event queue:

SWEQSRV

Every minute

This job is automatically scheduled by transaction SWF_XI_CUSTOMIZING.

This is an optional periodical task for the BPE. The frequency can be changed by using transaction SWEQADM.

Clean-up of workflow system:

SWWCLEAR

Every few minutes

This job is automatically scheduled by transaction SWF_XI_CUSTOMIZING.

It deletes the job logs for SWWDHEX and SWWERRE.

Processing of delayed messages:

SXMS_DELAYED_MSG_PROC<client>

Every 5 minutes

Schedule this job with transaction SXMSJOBS.

It tests (for a given client) the conditions for time and event-controlled processing of messages.

Check status of IDoc adapter:

SXMS_REFRESH_ADAPTER_STATUS

Between 1 hour and 1 day, depending on the intensity of the usage of the IDoc adapter

Use transaction SM36 to schedule this job on your Integration Server.

This job checks the status of messages that were sent to the IDoc adapter. Since the IDoc adapter does not send response messages, it is not automatically known whether a message was processed or not.

Performance monitoring, PMI:

SAP_XMB_EXTRACT_PMI_DATA

Every 15 minutes

Use transaction SM36 to schedule this optional job.

It extracts runtime data collected by the Process Monitoring Infrastructure (PMI).

If you want to display performance data from PMI in Performance Monitoring, you must schedule this job on your monitoring server.

Performance monitoring, PMI:

SAP_XMB_GET_PMI_DATA

Every 15 minutes

Use transaction SM36 to schedule this optional job on your Integration Server.

It retrieves runtime data collected by PMI and previously extracted by SAP_XMB_EXTRACT_PMI_DATA.

Performance monitoring, aggregation:

SAP_XMB_PERF_AGGREGATE

Every hour

Use transaction SM36 to schedule this job on your Integration Server.

It reads and aggregates auditing data and runtime data.

Performance monitoring, reorganization:

SAP_XMB_PERF_REORG

Every hour

Use transaction SM36 to schedule this job on your Integration Server.

It deletes aggregated runtime data after a time period specified with configuration parameter DAYS_TO_KEEP_DATA.

Schedule this job half an hour later than  SAP_XMB_PERF_AGGREGATE.

Find and restart failed messages:

RSXMB_RESTART_MESSAGES

Every 5 minutes (10 times)

This program searches for failed (could not be processed correctly) or missing (were deleted manually from the queue) messages and tries to restart these messages automatically. The maximum number of restart attempts and the interval between these attempts is set with the qRFC scheduler. After the maximum number of restarts, the restart is canceled if it was not successful.