Skip to Content
avatar image
Former Member

Delete Archive Job in sap po 7.4 single stack

Hi Gurus,

In our landscape we have configured archival and deletion of messages referring the link https://blogs.sap.com/2011/11/16/aae-archiving-in-sap-pi-711-with-xmldas/.

Archival is running successful and archival files are stored in file system(NFS). When we list the messages in archive tab of component monitoring, the older archived messages are still visible. In checking the archived files(stored in NFS) we could find the older files are still residing(in NFS) Because of this the messages are still visible in PI(Please correct me if my understanding is wrong).

In referring various SAP help and SCN blog, we need to configure "Delete Archive Job" to delete the archived file from file system. But the Job type is not visible in "Background Job Scheduler" of NWA. Please suggest how to enable/configure the Job in PI NWA.

System Version : PO 7.4 SP 12

Thanks for your help in advance!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • Best Answer
    Dec 29, 2016 at 10:09 AM

    Baskar,

    this job seems only available from 7.4 SP 13 onwards, see here https://launchpad.support.sap.com/#/notes/2174022/E

    Many thanks and kind regards

    Jens

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 04, 2017 at 07:02 AM

    Hi Baskar,

    about alternatives: You could "just" upgrade the respective components, however keep in mind that there might be SCA dependencies which will make upgrading single components a pain in the neck. Besides that, my guts feeling is: When you upgrading such central components like "MESSAGING" or "XI_AF" you should anyway run tests to some extend.

    So to answer the first question: No, you don't have (real) alternatives.

    About the second question. Reading the note I would assume that this is possible out of the box with the new job then. You can use the following attributes within the job:

    • Sender Party
    • Sender Component
    • Receiver Party
    • Receiver Component
    • Interface Name
    • Interface Namespace

    I would assume setting up multiple instances of the job with different attributes to fit your needs should be supported. (However, we are also not yet up to snuff with our PI SP levels to have the said job available, so I cannot guarantee that and YMMV)

    Cheers

    Jens

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 03, 2017 at 06:46 AM

    Hi Jens,

    Thanks for your pointer to SAP note. Any alternatives before we going for SP upgrade ? Right now we are in migration phase and would like to propose SP upgarde post go-live and stabilization.

    In addition to above query, we have new requirement. We have to retain certain interface archived messages for quite longer days in archive directory(say 60 days and other interfaces to be same 30 days)

    Can you suggest how can we achieve this.

    Regards,

    Baskar

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 10, 2017 at 03:13 PM

    Hi Jens,

    Thanks for your response. I understand that one "Archive" job is enough to archive all the interface messages(Using XML DAS in ). We need to configure multiple "Delete Archive" jobs with interface attributes(Party, Component etc..) based on retention period(one job to retain messages for 30 days and another to retain for 60 days). Please correct me if I have missed any points.

    Any other suggestion to remove the archived files from Archive Store (Folder structure : //usr/sap/<SID>/SYS/global/Archive). As we are nearing our go-live date, we are not getting approvals for SP or component upgrade :(

    Regards,

    Baskar

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 19, 2017 at 04:27 PM

    I don't know, frankly speaking. I would assume that you cannot just delete any of the archive files manually as that would lead to inconsistencies with the XML DAS service schema.

    If you absolutely must (because your storage capacity is getting low, etc) you could try moving several files in another directory and see what happens within Message Monitoring and archive / deletion jobs. I would strongly advice to do this on a sanbox or maybe a dev system first.

    Sorry to be no more of a guidance here but since we do not have the said report ourselves I could only speculate about the outcome of any manual interference.

    Cheers

    Jens

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 30, 2017 at 02:06 PM

    Hi Jens,

    We have communicated the suggestion to our Basis team. Thanks for your prompt responses.

    Regards,

    Baskar

    Add comment
    10|10000 characters needed characters exceeded