Hi All,
I've done extensive reading regarding archiving / deleting in XI and am comfortable with the concept / implementation. We are currently archiving and deleting for interfaces at this point, but I have a unique client scenario that seems to fall outside the bounds of the ability of the standard processes that I'd like thoughts on.
Requirement:
The client has defined a requirement to address a situation where a message coming into the production environment has extremely sensitive or classified data (let's say, the SSN of the President of the USA for grins) and all traces of that needs to be wiped from the system immediately - not just secured via transactions for later deletion but immediately deleted from all data storage locations on the system (let's assume context of XI only for this discussion).
Questions Related to the Below:
1) Which of the below scenarios are the best one to look at implementing and why?
2) Has anyone done anything like this before and how did you approach it?
3) Instead of trying to delete the entire message, given the payload data is the biggest concern, perhaps focus on simply deleting the message specific entries from the SXMSCLUP, SXMSCLUR where the payloads and attachments are stored? Would this cause significant issues without touching the other tables like SXMSPMAST table?
4) Along those lines, I don't think I care about the history or performance data for this type of process, sound right?
Our XI Implementation:
- XI 7.0, Enhancement Pack 1, Service Pack 9
- Scenario would need to address Integration Asynch / Synch (we do log synch messages), Adapter Engine, and Process Engine
I've looked into the following options, and would like guidance on which may be the best route to pursue before investing more time at this point.
1) Standard XI Processes
- This would be preferred, as SAP handles the maintenance. However, after reading I can't see how to make this work, as it's all driven off of the 'Retention Periods' defined for all messages (or for an interface). I can't find anything in the standard process that allows doing this at a specific message ID level like I would need - am I missing something?
2) Custom development
- This is the other end of the spectrum and would allow doing exactly what is needed, but adds a significant risk for maintenance should SAP change anything in the persistence layer in regards to tables, etc. With this option I could use the RSXMB_DELETE_MESSAGES (for Integration Engine messages) as a guide and modify as needed, but would need to understand the relationship of the underlying tables very well to ensure referential integrity is maintained.
3) Hybrid Custom and Standard
- This combines the two options, providing a custom front end but attempting to leverage SAP supplied called functions / methods for easier maintenance. For example, class CL_XMS_PERSIST has a method MARK_MSG_FOR_DELETE that potentially allows me to set the SXMSPMAST status to 'DEL' and a subsequent execution of the standard deletion program to delete it from the system - most likely not that simple but a starting point. Like Star Trek, it's theoretically possible....
4) Modify the Payload vs Deleting it
Instead of deleting the payload completely, either remove just the field data in question or replace it with all 'X's. Reference: http://wiki.sdn.sap.com/wiki/display/XI/Editing+message++Payload+in+XI. But is this Integration Engine Specific and would still require a solution for Process and Adapter Engine?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.