Background Processing 

Use

Using this function, you can schedule jobs for various background processing:

●      To archive messages processed successfully or edited messages

●      To delete messages that are not to be archived

●      To restart messages with errors

●      To reschedule lost messages

These processing options are only available if you chose an Adapter Engine as the component for monitoring. Otherwise, you can use the Integration Engine archiving, for example.

Prerequisites

●      You have started the Runtime Workbench, are in component monitoring, and have selected an Adapter Engine as your component.

●      You have configured message archiving for the selected Adapter Engine

Features

Archive

You require two archiving sessions to archive messages:

●      One session to write the messages to the archive

●      One session to delete the persisted messages that have been archived

A standard job is automatically created for archiving edited messages. It runs once a day and ensures that messages that were edited are archived. Before you can use this job you must first activate it. You cannot define rules for this job.

To archive correctly processed messages, you must schedule an archiving job that in turn implicitly schedules the runs for writing the archives and for deleting the archived messages.

You can define one or more rules for each archiving job; these rules contain the conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.

All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.

Delete

A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.

Restarting

Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).

You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.

Rescheduling

A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.

 Activities

Scheduling Jobs

To schedule jobs, choose Background Processing on the Status tab page. A list of all existing jobs is displayed.

Information in the Job List

Column	Meaning
Status	Status of the job. The following are possible statuses: ●      Red (): Job processing contained errors. ●      Yellow (): Job processing partly successful. ●      Green (): Job processing successful. ●      Gray (): Job has not been run.  Error statuses for red or yellow statuses are listed in the job log.
Job Name	Name of the job.
Job Type	Type of job (archiving job or delete job).
Next Run	Date and time of the next scheduled execution of the job

You can either create a new job or select and edit an existing job. Enter the following:

Specifications for Configuring a Job

Specification	Description
Active	Activates (or deactivates) the job.
Job Name	Name of the job that you want to create or change
Job Type	Type of job (archiving job or delete job).
Start Date/Time	Date and time when the job is first to be started
Frequency	Frequency in days or hours with which the job is to be started

As soon as you have saved a new job, it appears in the list of existing jobs and can be changed or deleted.

If the job already existed, it appears with the changed values after it is saved. The name of the person who last changed the job is displayed along with the date and time of the last change.

You cannot delete the standard delete jobs; you can only deactivate them.

You can start a job at any time, irrespective of when the next execution is scheduled, by choosing Execute. The job log provides the following additional information relating to the execution of a job:

●      Date and time of the last scheduled execution of the job

●      Number of messages processed when the last job was run

●      Total number of jobs run

●      Total number of messages processed to date by this job

If you want to define rules for a job, select the respective job and choose Rules.

You can only define rules for jobs to delete and restart messages.

Defining Rules

There are three input fields that you use to formulate conditions in order to define a rule for jobs.

Input Fields for Conditions

Entry	Meaning
Field	Field of the message header
<Operator>	Available operators are Equals and Contains
Value	Values that the content of the field must correspond to, or that the content of the field must contain

Once you have chosen Add to confirm your entries, the rule appears in the Current Rule field. You can now add additional conditions. All conditions of a rule must be met in order for messages to be selected based on this rule.

Once you have finished defining your rule, choose Save. The rule appears in the list of rules defined for this job. You can add additional rules or delete existing rules as you require.

If no rules are defined, the job archives all messages for which the retention period has been exceeded.