on 12-14-2011 3:47 PM
Hello,
Our PI production server is processing close to 10000 to 15000 messages / day . I would like to know how to archive these and what should be the duration of archival activity normally in Production system.
Normally in PI archiving should be done or should be delete the message after certain time ? Kindly suggest the best practice steps how to handle the message archiving/deletion.
Also normally how many messages usually PI server would be able to withstand in production. What happens if we do not delete for certain period.
Thanks.
Message archiving is easy in PI and good to handle. Thanks guys
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Here are answers to your questions
1.I would like to know how to archive these and what should be the duration of archival activity normally in Production system?
Ans) You can schedule archiving activity to happen everyday. You should have external hard drive to store the archived file.
After archival process is completed per day, the files will get saved in the external folder.
2) Normally in PI archiving should be done or should be delete the message after certain time ? Kindly suggest the best practice steps how to handle the message archiving/deletion.?
ans) you can choose the interfaces whose messages you want to archive. Before that you need to mark whether you want to archive or delete -async, sync messages, async with error, sync wiith error and history entries of messages.
The steps in short are
1. configure paths and filename of archival file.
2. configure the archiving specific object details, retention period and message interface selection.
3. configure and activate archiving object infostructure for reading the archived file.
4.Schedule the archiving.
5. after archiving is complete, schedule the "DELETE" program.
The transactios reqd will be -SARA, aobj, SXMB_ADM
3) Also normally how many messages usually PI server would be able to withstand in production. What happens if we do not delete for certain period.
Ans) depends on buffer space available in PI server. If you do not delete old messages for very long time, first your server throughput will decrease( it will become slow in working) and in worst case all messages will start moving to scheduled state.
Regards
Anupam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
If you already working on production and you didn't set it yet this will be problem, because pi set some indicator when the message come to PI and you cannot delete/archive this messages easily.
On ABAP stuck please refer to those links
http://help.sap.com/saphelp_nwpi71/helpdata/en/0e/80553b4d53273de10000000a114084/content.htm
Also thae into account idoc archiving
tcode SARA
and bpm message archiving
http://help.sap.com/saphelp_nwpi71/helpdata/en/96/0a2441509fa831e10000000a1550b0/content.htm
And also data archiving on Java stuck
Usefull note
SAP Note 872388 - Troubleshooting Archiving and Deletion in PI
BR
Maciej
As mentioned earlier, most part of your questions can be searched easily on SCN.
>>Normally in PI archiving should be done or should be delete the message after certain time ? Kindly suggest the best practice steps how to handle the message archiving/deletion.
This is exitirely busines dependent. Different countries have different legal requirements and therefore have different need of archiving and storing the processed messages. Contact your business team for such confirmation.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check this link http://www.saptechnical .com/Tutorials/XI/Archiving/Index.htm
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
implement PI Archiving deletion process(search in sdn),retention period depending on your PI data base size and client.
if data base growing rapidly then use appropriate retention period. check with SAP net weaver admin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.