cancel
Showing results for 
Search instead for 
Did you mean: 

Archiving of messages in PO

hamsa_shree
Participant
0 Kudos

Hello,

I want to configure archiving of messages in PO.

Could anyone please let me know the steps to configure the same

Thanks

Hamsa Shree

Accepted Solutions (0)

Answers (1)

Answers (1)

vadimklimov
Active Contributor
0 Kudos

Hi Hamsa,

Following materials contain good explanation of technical aspects of messages archiving in PO:

Regards,

Vadim

hamsa_shree
Participant
0 Kudos

Hi Vadim,

Thanks for your reply. We have configured Message retention on PO but message older than 1 day are getting deleted.

Could you please let me know how to resolve this issue.

Thanks,

Hamsa Shree

martin_babayan
Employee
Employee
0 Kudos

Hi Hamsa,

What are the current values of xiadapter.outbound.persistDuration.default and xiadapter.inbound.persistDuration.default parameter of service XPI Adapter: XI?


Path to find these parameters: NetWeaver Administrator  > Configuration Management > Infrastructure > Java System Properties.

Also have you set any retention value per interface? PIMON > Configuration and Administration > Adapter Engine > Message Retention?

BR,

Martin

hamsa_shree
Participant
0 Kudos

Hi Martin,

Please find attachment for the inbound and outbound values.

Yes we have also set the retention value per interface to 30 days still the archiving is not working.

Thanks,

Hamsa

vadimklimov
Active Contributor
0 Kudos

Hello Hamsa,

In addition to recommendations provided by Martin above, please check which housekeeping jobs are scheduled and active in Advanced Adapter Engine (PIMON: Monitoring > Adapter Engine > Background Job Monitor)? Are jobs of both job types "Archive" and "Delete" are scheduled? If message deletion job is scheduled, please check if message archiving job has any rules configured for it. A reason for this is, message deletion job checks if any rules are configured in active message archiving jobs and doesn't deleted expired messages (message persistence expiration parameters - global and interface-specific - are provided in Martin's reply) if it finds out that message archiving job doesn't have any rules (which means, all relevant messages for all interfaces are subject for archiving). Otherwise, it performs cleanup logic of persisted expired messages.

As a temporary test, you may inactivate message deletion job and run message archiving job explicitly in Background Job Monitor - assuming there are relevant messages that reached retention period, you shall be able to see from a job log, if it succeeded in archiving them or not.

Regards,

Vadim

vadimklimov
Active Contributor
0 Kudos

Hamsa, just got an update and your recent reply already after posting mine.

First of all, is there any strong reason to increase retention period to such a high value as 14 days (especially assuming you are configuring message archiving - which means to me, you will anyway have access to archived messages later on)? If the PO system will be highly loaded, then high retention period will negatively impact database size and may have performance drawbacks.

Apart from that, it shall be noted that changes to values of properties xiadapter.outbound.persistDuration.default and xiadapter.inbound.persistDuration.default only take effect for newly processed messages. So, if the default value is 1 day and there were already some messages processed, they will be assigned retention period 1 day, even if you change values of mentioned properties afterwards. When the message gets processed in Advanced Adapter Engine, it gets assigned a time till which it shall be kept in database (persistence expiration time which is calculated based on retention period parameterization - corresponding value can be checked for every processed and persisted message in table BC_MSG, column PERSIST_UNTIL). If you adopted retention periods and if you would like to make amendment to persistence expiration time of already processed messages, this can still be done by navigating to http(s)://<host>:<http(s) port>/MessagingSystem/job/reorgdb.jsp and triggering forced overwriting of existing messages persistence expiration time (check SAP Note 1872758 for more details).

Regards,

Vadim