To archive messages that have been processed successfully or edited

You require two archiving sessions to archive messages:

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.

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

To delete 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.

To restart 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).

More information: Monitoring Messages

To reschedule 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.