Archival Process implementation in PROD system for PI/PO messages

[former_member320305]

Hi All,

I am working in 7.31 single stack. As per the standard config in PROD system, we have only 2 days retention period and do not have any archival process.

I had seen many issue in past where I was not able to see any payload/log for 3-4 days old successful messages (if we want to verify the data) because of limited retention period.

Also I had a discussion with my Basis team, As per discussion, if we increase the retention period from 2 days to 7 or more and Turn on logging for synchronous messages then we may face the performance issue. Hence, we can not increase it.

So as part of solution, they agreed to put Archival Process for PI messages for 10-15 days but asked me to do R&D for this implementation.

I checked from my side & found XML DAS config as mention below:
http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/11/16/aae-archiving-in-sap-pi-711-with-...

However I can not implement it in NON PROD system by myself as dont have all info(user id , pw etc..)

Can anyone please share your experience if they had/have implemented Archival Process in their project?
I need to share demo on this so please help me asap.

Thanks & Regards,
Prabhat Singh

[nidhi_srivastava22]

Hi Prabhat,

Apologies for the delay in response. Let me know if you are still looking for screenshots, will mail.

PFB the inputs from my end -

1) Achieved in the directory in the same OS level server where PI is installed.There were no performance issues seen.

2) It is not recommended to save Sync messages until and unless there is some critical issues. You can use Logging & Stagging in ICO for synchronous messages if required for Sync messages. I have only configured for Async messages.

3) Yes, it was seen in the archive tab. You need to schedule/run the jobs in order to see that.

Thanks,

Nidhi Srivastava

[Muniyappan]

are you talking about synchronous messages archive? As far as i know archving will work only with ansynchronous. just curios to know about your findings.

[nidhi_srivastava22]

Hi Prabhat,

I have implemented using the same blog which you are referring and this works fine. The only change I did is, I scheduled a new archiving job instead of the default one. The default one was not working for me.

I have taken the screenshots when I implemented this, in case i find it I will share.

Thanks,

Nidhi Srivastava

[former_member320305]

Thanks Nidhi For reply.

It would be great if you can share the screenshot here or share with "rahul.jain894@gmail.com".

1. Did you archived the PI messages in Separate Database or in existing PI/PO Single stack Database? If it is same then, was there any Load issue/Performance impact?

2. What about the Sync Messages?

3. Are you able to see old messages under Message Monitoring Archive Tab with Payload & Log?

Thanks in advance.