Skip to Content
Author's profile photo Former Member

High volume data : Archive strategy for SAP XI (Vol-1)

When we talk about Archiving and housekeeping and their roles in performance and in better running system SAP XI the archive strategy always play important roles. It’s really very important that housekeeping and archive strategy take on place with the right mythology.  Generally XI developers ignore this fact since they think it’s not relate to development part so they hardly look in this but this is an important task which need to designed and monitored well by XI developer. But before making any strategy it’s depending on client case that how much amount of data you are dealing daily and what quantity history data you like to be in your system for monitoring purpose. For dealing with small quaintly of production data it’s easy but dealing with 100 thousand (1, 00,000) – 1000 thousand + (10, 00,000) it’s very hard (I say tricky) to maintain the archive strategy because you have to always struggle with the high quantity/volume data v/s performance because of the increasing huge database tables and messages everyday.  7 days Archive strategy:- 1)      Generally in cases you need to maintain the monitoring data strategy first that how much history data you will required for monitoring. Ideally on average vase it should be 7 days, no older required i.e. you will only maintain the 7 days older data. (You can think/Plan even small history data i.e. 3 days/ 5days but I suggest making it 5-7 days only because if you will decrease you need to be very quicker in monitoring i.e. in issue fixes and error handing and other terms to make analysis but in end it depends on the requirement and on the strategy only).   2)   Follow the link and schedule all the housekeeping Jobs as per recommendation by SAP and be carefully in the monitoring of SM37 on daily basis as well because if any jobs get fails you need to reschedule it again.  (              The +simple deletion procedure+ is set as the default.It is easy to activate the+  switch procedure+. To do so, select the +Switch Procedure Active+ checkbox. You can do this at any time. The delete 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  8)      Archive parameter in SXMB_ADM -> Configure Integration Engine ->Archive should be as below:- image” Again you have to maintain the 7 days value as retain retention period for PERSIST DURATION and 1 for archive manually cancel and change message.  9)      To archive interfaces in the Integration Server, the interfaces have to be defined for archiving via transaction SXMB_ADM ->”Define Interfaces for Archiving and Retention Periods”.  image image 10)      Trace Log level on J2EE is always must be reduced to Error.  J2EE engine Trace and log leval should be reduced to Error oly.Check the Net weaver Administrator or the visual administrator to reduce log and trace level. How-to guide is also available on SDN for same. image 11)   Reduce LOGGING_SYNC to 0. image 12)      Weekly Run RSWF_XI_INSTANCES_DELETE report.image   Finally you will get how many XML files are removed in status bar of the message.      imageAlso you should have option to check these entries in test mode via RSWF_XI_INSTANCES_SHOW report before actual deleting them via delete report.In output/ as result you will get the total XML messages which need to be deleting. Here Example. “image”    13)  Check SXMS_REFRESH_ADAPTER_STATUS, SXMS_PF_REORG reports, they should be in the schedule jobs list since it’s already comes in the House keeping strategy.Point#1.   14)  Execute the RSXMB_DELETE_HISTORY to delete history entries from history table SXMSPHIST on weekly basis so that you can control the history. SAP notes *1113757* can be helpful in this.          15) Weekly Check the SM58 transaction. If you found any entries in error status due to technical reasons like users being locked or database errors. Each entry must be dealt with (either reprocessed or deleted). image

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      Thanks for consolidating, very informative and Great work!
      Author's profile photo Stefan Bosshard
      Stefan Bosshard
      Excellent work - well done!