AAE Archiving in SAP PI 7.11 with XMLDAS
The latest releases (i.e.) PI 7.1, 7.11 and 7.3 of PI allows you to use only Java stack to achieve your integration requirements. But now the questions are, how do you archive the successfully processed messages in AAE? Can it be retrieved from Archive store whenever required? How do you configure XMLDAS and Java archiving cockpit? How do you use PI internal file system to store the archived messages?
I hope, this blog would answer all the above questions.
SAP documents answers most of these questions but i would like to have all the setting in one blog.
Here I am explaining to use the local PI UNIX file system as archive store. (Very easy one).
The steps are,
- Create HTTP destination to DAS (i.e.) DASdefault.
- Create a empty folder in the PI file system which will be used as Root.
- Set up a home path.
- Setting in Java archiving cockpit.
- Schedule the background processing jobs in PI RWB.
- Monitor the Archiving session in Java Archiving cockpit.
Let me explain the steps in detail
Login to NWA–>Configuration Management–>Destinations.
Please create a new destination with name as DASdefault. The URL should be http://localhost:<port>/DataArchivingService/DAS and select ignore certificates.
Now navigate to logon data in where you need to define the authentication details. A user should be created in J2ee with all required roles.
To successfully connect you need an SAP NW AS user that is assigned to the UME role SAP_ARCH_XMLDAS_VIEW (for viewing authorization) or SAP_ARCH_SUPERADMIN (for full authorization to execute actions).
Please enter the user and password details and ping the destination. The destination should work (i.e.) return code 200.
Please request your BASIS team to create a empty folder which will bed used as root folder to store all archive files.
In my case, I create a empty folder called XMLDAS under /usr/sap/SID/GLOBAL.
Please proceed to NWA–>Operation Management–>Data and Databases–>XML DAS Administration. And go to Archive store management and create a new archive store.
Archive Store : XI_AF_MSG
Description : < Description>
Default : Yes
Store Type : File System
Windows root: Empty (As i use UNIX file system)
UNIX root: //sapmnt/SID/global/DASXML (MAKE SURE YOU START WITH //. otherwise you will get a error message says Cannot resolve URI.)
You can test the Archive store which should return the message as
Archive store XI_AF_MSG is available
This is very important step as XMLDAS will try to access the folder through URI and the folder should be reached without any issues.
Please try to fix issues if you have any before proceed with further steps.
Please enter home path in the next step .The folder what you enter here will automatically get created in the file system.
If my case i use, /<SID>/xi_af_msg/ (make sure you have / at the start and at the end)
Select archive store which was created in STEP 2.
This is required to make sure we have correct home path.
NWA–>Operation Management–>Data and Databases–>Java Archiving cockpit
Go to Configure–>Archiving Set –>xi_af_msg.
Please make sure AHOME property is having the correct value here which is /<SID>/xi_af_msg/.
***If you modified the initial home path in step 3, please make sure you have changed the path in java Archiving cockpit as well***
Save the values.
Login to Runtime work bench–>Component monitoring –>Adapter Engine –>back ground processing.
And create/modify the archive job as per your requirement. You can also set up the rules for archiving.
To test your archive, you can run the job immediately
***If you don’t have any rules in the archiving job, all messages available in table BC_MSG will get archived in the file system and will get deleted from database**
And also check your retention period for AAE message. This can be Set/Modified in NWA
STEP 6 :
To monitor you archiving session please use Archiving monitor functionality available in
NWA–>Operation Management–>Data and Databases–>Java Archiving cockpit.
You can see all details about your archiving session here like No of message archived, deleted, Session status….etc…
So now you are done with XML archiving for AAE messages
Let me know your thoughts and suggestions.