Skip to Content

Hi all,

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

STEP 1

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.

STEP 2:

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.

STEP 3:

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.

STEP 4:

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.

STEP 5:

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.

To report this post you need to login first.

20 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member

    Hi Rajesh,

     

    Thanks for the informative blog. Just a question, can you tell me how to delete archived

    messages ? for example, delete the xml files in this location:/usr/sap/SID/GLOBAL

    Is there a way to control the retention period in the archive? Thanks

    (0) 
  2. Former Member

    Hi All,

     

    thanks for the informative blog Rajesh,
    can anyone of you who has setup archiving in PI 7.4 help me over my queries.

    1.if we use an file system to store the archived messages, how to delete the archived messages after some period of time if required. is there a job or do we require to delete them manually. what is the procedure?

    2.other than file system can we use any other source to store the archiving content. if yes what would be the procedure.

     

    many thanks for your replies.

     

    Regards

    Bala

    (0) 
    1. Ganesh G

      Dear Bala,

       

      I’m also working on how to archive and delete the messages in PI 7.4 single stack.

      Can you help me out if your issue is resolved.

       

      Regards,

      Ganesh

      (0) 
      1. Former Member

        Dear Ganesh,

         

        we are able to archive the messages successfully in PI 7.4 Single stack system. we are using local file system as the archive location. please let me know your questions specifically so that I can suggest if I am able to. I have followed the above mentioned procedure only. Just let me know support package also.

         

        regards,

        Bala.

        (0) 
        1. Ganesh G

          Hi Bala,

           

          Thanks for the prompt reply.

          We are also using the file system as archive location.

          My question is related to scheduling the jobs?

          Where and when we need to schedule the jobs for archiving and deleting.

          Any rules we need to mention while scheduling the jobs.

          In my case I need to archive the messages and retain it for 1 week and then delete it.

          Whether the above settings will archive successful messages or total all messages?

           

          System Info:-7.4 SP-12 Java stack.

           

           

          Regards,

          Ganesh

          (0) 
          1. Former Member

            Hi Ganesh,

             

            we need to schedule the jobs in NWA-SOA-Background job processing-adapter engine jobs. there you will have three jobs by default which are delete job, archive job and recover job. the default archive job will not archive the messages which are not edited in the message editor. so you need to create a new archive job. and coming to the rules it is up to your requirements whether to archive all the messages or messages from few interfaces. depending on that you can maintain rules. The archive job will archive messages which are successful and cancelled. error messages will stay in DB until and unless they are cancelled. for deletion on the archive a job is delivered by SAP but unfortunately from SP13. the job type is “Archive Delete”. that you can schedule when it is available. for now we are deleting the archived messages manually in java archiving cockpit by deleting the collections which are created by Archive job which is removing the archived messages from archive(file system) and making free space on file system.

             

            For any more info please feel free to contact me on 9959959359

             

            Regards,

            Bala.

            (0) 
            1. Rishi Das

              Hi Bala

               

              Thanks for your post .

              Can you please help to locate any standard SAP document for the Archiving of messages in the SAP PO 7.4 Environment .

               

              Thanks

               

              Rishi

              (0) 
              1. Former Member

                Hi Rishi,

                 

                I too did not find any SAP standard docs for this configuration. I just followed the above steps and started researching whenever I got stuck. Hence I am able to complete the setup. the above mentioned steps of this post are relevant and this seems to be a very useful blog. Feel free to contact me for any queries. I would help you if I can.

                 

                Regards,

                Bala

                (0) 
  3. Former Member

    Hi Bala,

    I have done the same configuration as mentioned in this blog.

    But the archiving set xi_af_msg is already assigned to the default atchiving test store present in the system and could not be unnassigned.We tried changing the test store configuration and made the newly created test store to default and also restarted the server instance.But still we are not able to unnassign this archiving set and assign it to new test store.Could you please advice on the same.

    (0) 
  4. Former Member

    Hi Bala,

    I have performed the same configuration as described above.

    But the archiving set xi_af_msg is still assigned to the old default archiving store in the system.

    We changed the default archiving store to the new one we created ,and took the restart of the system .But even then the this archiving set xi_af_msg could not be unassigned and reassigned to the new archive store.

    There was unassign button for all the other archive sets except for this one(xi_af_msg).

    Could you please advice on the same.

    (0) 
  5. Former Member

    Hello Bala , We do not have a permanent solution to this problem as the NW version does not fix this bug. How ever as consulted with SAP there is a work around for the same which is as below: 1. Take the backup of your data which is currently present in the physical location for archiving set xi_af_msg.(Very Imp) 2. Now Go to Java archiving Cockpit->Hierarchy and delete all the collections for folders 2014, 2015 and 2016 for archiving set xi_af_msg.(this step will delete the data from the physical location as well, that’s why step 1 is very important) 3. Since you have deleted all the data for archiving set xi_af_msg, now you can go to xml das administrator-> xi_af_msg this should be empty now 4. You will now get the assign option to assign the new archiving store, using which you can assign your TEST STORE to archiving set xi_af_msg. So we wouldn’t be able to view these old archive files (which were already archived ) from the GUI level.However these  files will be  placed in the backup at the OS level

    (0) 
  6. Former Member

    Hi Rajesh,

     

    Good blog, documentation, starting point for the configuration of Adapter Engine message archiving on PO 7.4 Single stack Java. Keep up the good work.

     

    Regards,

     

    Tom VdB

    (0) 
  7. Former Member

    Hi experts.

    I need your help with archiving in deleting messages in PO 7.4 (single stack).

    Firstly I need to tell you that I succesfully did all 6 step and now archiving works (1x per day) perfectly with Message Retention settings.
    I had defined “Default Delete Job” too and activated it (it runs 1x per day). I presume that this works with retention settings too (correct me if not, please).

    And now my questions:

    1. If Delete Job starts before Archive Job (no rules), then messages are deleted and Archive Job has nothing to archive?
    2. If Archive Job is first to start and while running it is somehow interrupted and stopped working in the middle of process and then Delete Job starts after that (schedule). What happens to those messages who aren’t archived yet?

    Thank you very much for answers.

    (0) 
  8. ramu mohan

    Hi Experts,

    I have one doubt, if I will do same configuration mentioned above  will it archive old messages also or from now onwards (after configuration)?

    Actually our Quality system OS memory reached 92%. So we need to delete or reduce that size. If we will configure like same it will reduce the size or not?

    Please help me on this.

    (0) 
  9. Karan Chowdhury

    Hi Experts,

    I followed the above steps properly .I am now facing the below issue in JAVA archieving cockpit.

    I have given all the required access and roles to the user for connecting to the HTTP destination.Even while pinging the destination ,it is returning message of 200.

    The background jobs which I scheduled are also not running properly

    .

    I don’t see any logs in any of the jobs.

    Can you please help in this matter.

    BR

    Karan

     

    (0) 

Leave a Reply