Process Integration
Page tree
Skip to end of metadata
Go to start of metadata

Purpose

In this WIKI Page you can find all of the useful information about the persist duration parameters at the Adapter Engine. Sometimes it is not fully clear how the system calculates the persist duration time or it seems to be wrong after the right configuration. I will show you which parameters have to configure, and what is the possible workaround if you don't find a quick solution for the wrong calculation.

Overview

There are some parameters at the Adapter Engine which have to be configured in order to the persist duration time calculates in the right way.

Parameters regarding asynchronous messages:

  • xiadapter.inbound.persistDuration.default
  • xiadapter.outbound.persistDuration.default

Parameter regarding synchronous messages:

  •  messaging.log.RetainTime

There are no other parameters which should be configured besides on the mentioned ones, but sometimes the system seems to not reflect to our configuration. I will show you the right way of the configuration step by step in the following sections.  

Persist duration time at the Adapter Engine for synchronous messages 

Go to NWA -> Configuration -> Infrastructure -> Java System Properties -> Services -> XPI Service: Messaging System -> messaging.log.RetainTime

Here you can configure the parameter in days, and you can add "Custom Calculated Value" also. However the parameter seems to be online modifiable, - the "Cangeable" checkbox has marked - it is not, unless you apply the code changes from SAP Note 2565934 - Service property messaging.log.retainTime requires system restart to become effective  . If you want the system reflects to the changes, but the code changes from mentioned SAP Note does not present in the system, you have to restart it.

The parameter has to be configured at instance level as well.

Define a parameter at instance level is a must, because the system is reading the value from here as well. Instance level is "stronger" than Template level.

If you don't want to, or not possible to restart the system (e.g.: It is productive.), than there is a possible workaround to configure the mentioned parameter as per interface, which is online modifiable. To do this, follow SAP Note 2218407 - Message Retention Per Interface for logged synchronous messages.

It is very important, that the system will calculate the new retention period for the newly sent messages only.

Persist duration time at the Adapter Engine for asynchronous messages

Go to NWA -> Configuration -> Infrastructure -> Java System Properties -> Services -> XPI Adapter: XI -> xiadapter.inbound.persistDuration.default, xiadapter.outbound.persistDuration.default

Both of the parameters have to be configured. Here the value is in milliseconds. 86400000 milliseconds mean 1 day.

The mentioned parameters are online modifiable, does not need to restart the system.

It is very important, that the system will calculate the new retention period for the newly sent messages only.

BC Adapter

 If you are using BC Adapter in some scenario, you might see, that some messages have their "own" (probably 30 days) retention period. It is because of you can set the retention period for this adapter type in the Integration Builder -> Communication Channel. Set the persist duration time here is scenario specific, so harder than sets it in NWA.

It is possible to set the retention period for Sender BC Adapter:

It is possible to set the retention period for Receiver BC Adapter:

Retention period per interface

As I mentioned earlier there is a possibility to use the new "retention period per interface" functionality. You can define retention periods for every single interface, separetly.

 Go to -> NWA -> SOA -> Monitoring -> Message Retention

When you configure the retention period per interfaces, you should use wild card ( * ).

In order to use this new feature you have to apply the patches from the following notes:

  • SAP Note  1960448 - Configure message retention period per interface
  • SAP Note  2218407 - Message Retention Per Interface for logged synchronous messages
  • SAP Note 2208282 - Retention period per interface does not consider receiver component

How do you know if the retention period calculate correctly?

 Go to -> NWA -> SOA -> Monitoring -> Message Monitor -> Database -> Select a message -> Message Details -> Persist Until

The "Persist Until" attribute shows the time, when the messages will be deleted.

Related Content

Related Documents

 

 

Related SAP Notes/KBAs

SAP Note  1960448 - Configure message retention period per interface

SAP Note  2218407 - Message Retention Per Interface for logged synchronous messages

SAP Note 2208282 - Retention period per interface does not consider receiver component


__________________________________________________________________________________________________________

Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.