cancel
Showing results for 
Search instead for 
Did you mean: 

Synchronous message persistance in single stack PO7.4

PavanKumar
Active Contributor
0 Kudos

Hi,

We are in process of migrating synchronous scenarios from 7.0 to 7.4. In 7.0 we are able to persist sync message for many days while in 7.4 single stack we are not able to persist the message more than 7 days

1) We want to persist the Synchronous messages for long duration i.e like as we did in 7.0. Please suggest

As we have seen in the blogs the below parameter can persist for default 7Days

messaging.log.retainTime:7


If this parameter if we increase will it cause any problems?

Kindly suggest to persist sync message for long duration.

Regards

Pavan







Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182412
Active Contributor
0 Kudos

Hi Pavan,

If you have requirement to keep the synchronous messages more than 7 days you can change it to longer than 7 days as per this note section 3g 872388 - Troubleshooting Archiving and Deletion in PI



g) In case you have configured additional staging and logging steps as described in Note 1760915 message information will also be persisted in BC_MSG_LOG table. The number of entries directly correlates to the number of logging/staging steps you configured and the volume of messages for those interfaces. For asynchronous messages the logged or staged message versions will be deleted automatically when the message from BC_MSG table will be deleted. Synchronous messages are only logged in BC_MSG_LOG without a corresponding entry in BC_MSG table. Therefore these entries have their own retention period specified in parameter "messaging.log.retainTime" under service XPI Service: Messaging System. The value specified here is in days and by default these logged message versions are persisted for 7 days. The logged versions of synchronous messages will also be deleted by the standard PI message deletion job and no additional job has to be scheduled.


There is no restriction for this value, better to keep the value as low as possible, it is completely depends on your requirement, it will occupy more space in the database and it will affect the system performance but if your server have capacity you can increase it.


Regards,

Praveen.

Former Member
0 Kudos

Hi Praveen,

I'm also facing the same issue, for persisting the synchronous messages in our production environment,

where we need to persist messages for a period of 6 months same as what we have maintained for asynchronous messages.

Is it possible to increase the value of messaging.log.retainTime to 180 days period.

Will it be stored in database

And why I am seeing the persist date for some scenarios for successfully processed synchronous messages as 1/1/1970

PavanKumar
Active Contributor
0 Kudos

Hi Praveen,

Thanks for the notes.

We are doing some test case regarding the same for that we changed the parameter

messaging.log.retainTime to 1 day and logging enabled at ICO for sync message peristance.

But persist until date it is showing in different format Please find screen shot of the same and also we have given date for one day but message persisted more than one day. Did we have done any configuration wrong?

kindly suggest your earliest reply in this regard really helpful as we really stucked in this issue.

Regards

Pavan