Performing Background Processing

You can schedule the background processing of routine tasks on the Advanced Adapter Engine. You can configure the following tasks:

• Archiving messages that have been processed successfully or edited.

  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. The system archives all information that is displayed for a message in message monitoring, in addition to the audit log for each message.

• Deleting messages that are not to be archived.

  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 messages with errors.

  Instead of restarting messages with errors manually in 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). For more information, see Monitoring Messages .

• Rescheduling lost messages.

  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.