Hi,
1. Tx SXMB_ADM, define interfaces for archiving/deletion - define retention time. Here you can sett 60 days (2 months) before messages should be deleted. Then you need to schedule your deletion job. Make sure you remove all interfaces from the archive-list to avoid these messages being marked for archiving instead of deletion if you want to delete all messages.
2. The report RSXMB_DELETE_ARCHIVED_MESSAGES will delete the messages that were already archived.
In addition to set up archiving and deletion as suggested above there are a few reports you can run (since archiving and deletion only considers messages in a final state).
To release messages in unarchivable statuses: http://host:port/MessagingSystem/archiving/reorgdb.jsp
Schedule following reports weekly (depending on your error handling and reporting procedures for your system this might not be possible in your production system):
RSXMB_CANCEL_MESSAGES
RSXMB_CANCEL_NO_COMMIT_MSG
RSXMB_CANCEL_NOT_REST_MESSAGES
RSXMB_CHECK_ITFACTION
RSWF_XI_INSTANCES_DELETE
SXMS_REFRESH_ADAPTER_STATUS
In addition you have the following reports dealing with enabling messages for archiving deletion
u2022 RSWI_REGENERATE_WI2OBJ (uncheck u201CDisplay modeu201D and set for relevant dates)
u2022 SXMS_REFRESH_ADAPTER_STATUS - Success: all msg with adapter status 001 changed to 006 (archivable)
u2022 RSWF_XI_UNUSED_MSGS (recommended not to run in production to avoid loosing data)
RSXMB_SHOW_REORG_STATUS shows number of messages scheduled for archiving/deletion
RSXMB_SHOW_STATUS shows number of messages per message status, and adapter status for messages with message status = 003 (Processed successfully)
RSXMB_CHECK_MSG_QUEUE fixes inconsistencies by changing the message statuses 001, 009, 012 and 016 to 014/021.
Hope this helps!
Br,
Kenneth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.