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.         http://help.sap.com/saphelp_nw04/helpdata/en/cd/20bc3ff6beeb0ce10000000a114084/frameset.htm 

3)      Fixing of all Archiving jobs suggested by SAP.

http://help.sap.com/saphelp_nw04/helpdata/en/8d/3e4f1d462a11d189000000e8323d3a/frameset.htm

         Mainly SAP_BC_XMB_DELETE_<client> (Deletion job for XML messages),SAP_BC_XMB_HIST_DELETE_<client> (Deletion job for history Entries), ARV_BC_XMB_WRP<date>, ARV_BC_XMB_DEL<date> must be there.

4)      Every end of week/month you need to  run report RSXMB_CANCEL_MESSAGES, RSXMB_CANCEL_NO_COMMIT_MSG and RSXMB_CANCEL_NOT_REST_MESSAGES. These reports used to cancel all type of error messages in bulk. Generally messages which were in error and no longer required need to cancel so that we can archive them. It’s very often in project that we take action on this kind of message but we forgot them to cancel.

     These reports cancel this kind of messages and also give opportunities to look again in these messages if you run these reports in test mode and this only why generally you should not try to schedule them in production environment. If you use it to cancel messages in productive environment you have to make sure that the messages to be cancelled have been resent or that it is fine for business to cancel them. Messages in error within the retention period should be dealt with manually as usual.

5)      Run RSXMB_CHECK_ITFACTION program on weekly basis to make the affected messages erasable and achievable again on every month.

6)      DELETION configuration strategy-

 Go to SXMB_ADM -> Configure Integration Engine -> Specific Configuration. Create an entry of category DELETION, parameter DROP_MAX_TABLE_LOAD, no sub parameter. (10-50% depending on you requirement or you can also calculate this value by giving formula in the information document ) and other entry for Persist Duration (Retention period of synchronous or asynchronous should be low i.e. if you are following 7 days  then value should be 7 days.

        "

7)      Activate SXMB_ADM -> Configure delete procedure activation.

      Generally we have Simple and Switch procedure for delete message.

            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:-

"

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".

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.

11)   Reduce LOGGING_SYNC to 0.

12)      Weekly Run RSWF_XI_INSTANCES_DELETE report.

   Finally you will get how many XML files are removed in status bar of the message.

Also 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.

""  

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

16)      Weekly Lookup into the system log (transaction SM21) generally in high environment it possible one day of processing fills up the log completely. You need to be careful for this.Also if any error is present they must be investigated and solved since this is only log else no use.

17)      Adapter engine: - Make sure if any error message present in the engine if it has to be resent or can be cancelled. Messages in error within the retention period should be dealt with manually as usual.

18) Also RSXMB_SHOW_STATUS report will gives you overall overview of the status of all messages. You can check details number status explanation from the SXMSMSTAT table.

In next I will continue with the strategy with Adapter engine/BPM and configuration in visual admin for same.