Archiving and Deletion in PI

...Previous

Now schedule delete jobs as per steps defined above.  

In above case switch procedure was not required as the tables were only 1% filled as against 90% configured in SXMB_ADM. You can reduce the table fill level as per your needs so that the switch process is carried out as shown below

Choosing a Deletion Procedure

The simple deletion procedure is set as the default. No steps are required to activate the deletion procedure. It is easy to activate the switch procedure.

To do so, select the Switch Procedure Active checkbox. You can do this at any point. The deletion jobs react automatically.

You can only deactivate the switch procedure when the original tables are active and the counter for the number of deleted records in the original tables is at zero. If this is not the case at the time of configuration, this is noted by the system and the switch procedure is deactivated the next time that table entries are copied from the table copies to the original table.

Archiving / Deletion of messages in the Adapter Framework  

1.) Only messages in a final status can be deleted or archived.  

2.) Messages with errors have to be cancelled first. Manually cancelled messages do not have to be archived but can also be directly deleted in the AFW. Canceling messages in the AFW is done in the RWB via "Message Monitoring". To find the messages in error choose your adapter engine and either select the Database Overview or the Database page (select status "All Containing errors"). If you have many messages in error you can use the "Multiple Selection" button to cancel messages.  

3.) Messages on the Java side are persisted in table XI_AF_MSG for PI 7.0 & table BC_MSG for PI 7.1). This table can not be monitored via transaction SE16. Therefore you have to use database tools. To analyze the overall number of messages you could use the following SQL statement: SELECT COUNT (*) FROM XI_AF_MSG.

4.) As a rule only those messages get archived, for which persist until date is expired. Persist until date gets calculated by the current send/receive time of a message, plus the configurable "persist duration" value. For the central and decentral Adapter Engine(s) "persist duration” value can be configured as two properties of the J2EE Service

1."SAP XI Adapter: XI" (value is in milliseconds): "xiadapter.outbound.persistDuration.default"

2. "xiadapter.inbound.persistDuration.default"

5.) Keep in mind that the default persist time for messages in the Adapter Framework is 30 days. This means that messages will be kept in the database for 30 days until the deletion job removes them. Changing the retention period in the AFW will only affect new messages that get processed by the adapter engine.  

6.)  As of XI 3.0,  SP11, a user interface is available that allows you to manually set the retention time for messages to expired so that you can remove these messages from the database immediately or archive them before deleting them.

For this purpose, call the following URL in a browser   

http://<host>:<port>/MessagingSystem/archiving/reorgdb.jsp

Enter a number of days. For the messages that were sent or received earlier than the number of days you have specified, the retention time is reset so that you can delete them immediately from the database.

Bear in mind that you can only delete or archive messages whose retention time has expired and at the same time, that have, a final status (successful or failed). In addition, only messages without any configured archiving rules can be removed manually from the database. If an archiving rule exists for a message to be deleted, it is deleted automatically after the scheduled (or manually started) archiving job was completed.

Click here to continue...

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image