
This function enables you to define jobs for scheduling the processing of messages or message packages that have been sorted by a filter and not processed immediately.
Together with the functions for defining the required senders and receivers and the corresponding message filters , this function gives you the option of event-controlled message processing . You can stop specific messages and postpone processing until a later event occurs.
If the event-driven message processing functions of PI are not sufficient, you can use the more extensive job scheduling options provided by usage type AS-ABAP.
In this case you have to use the ABAP Editor (transaction SE38) and program SXMS_START_JOBS to schedule a job whose name corresponds to the job ID.
Before scheduling, the status of the job is To Be Scheduled; after scheduling, the status is Scheduled Externally.
You have chosen Configuration → Configure Event-Driven MessageProcessing from the Integration Engine menu and then Jobs. You are on the Schedule Message Processing screen.
A job starts as soon as
A traffic light above the job list shows the status of the scheduler job:
| Traffic Light | Status |
|---|---|
|
Green |
The scheduler job is scheduled and is running |
|
Yellow |
The scheduler job is scheduled but overdue. |
|
Red |
The scheduler job is not scheduled. |
If necessary, you can reschedule the scheduler. Choose Scheduler Overview.
The Number column in the job list shows how many messages have been stopped by message filters and assigned to the job. You can display these messages individually.
You can add, change, delete, update, and reset jobs. You can also (de)activate jobs and execute them immediately. You can display details for a job.
To execute a job immediately, you require special authorization. The job is executed immediately in the background with the name of the job ID.
Adding a Job
When adding a new job, specify the following criteria:
S
The specified start time and date are recalculated after each period.
All entries are optional except for the job ID.
Changing a Job
You can change all the criteria except for the job ID by using change mode.
If a job ID was created when the message filter was defined, you can add further specifications for the job in change mode.
(De)activating a Job
There are two ways to (de)activate a job:
In this case we recommend that you do not make any time specifications during job definition, so that the chronological sequence can be driven by an external event.
Scheduling a Scheduler Job
To start the periodic scheduler job that performs a client-specific check of the criteria that are used to start a job for event-driven message processing, choose Schedule Scheduler.
When you schedule the scheduler job (for example, if the traffic light for the scheduler status is red) you can enter the corresponding data in the dialog box.
If the scheduler job is already scheduled (the traffic light for the scheduler status is green), a corresponding message appears.
Displaying the Scheduler Log
To display the entire scheduler log, choose Display Scheduler Logs. This takes you to a standard application log, where you can search in the message texts for errors or for IDs of processed messages, for example.
Displaying Messages
If the number of messages stopped by a message filter and assigned to the job is greater than 0, you can list the messages individually by double-clicking the number displayed under Messages per Job. This displays the message ID and the quality of service (QoS). You can display each message in detail.
You can also navigate to message monitoring and Display All Messages (
) or display individual messages in detail (by selecting the message ID).