Maintaining transaction sequence when End system is down

[Former Member]

Dear All,

<b>Maintaining transaction sequence when systems are down.</b>

Scenario:

SAP(IDocs)--> XI --> DB

DB is up & running, so messages (msg1, msg2) sent by XI have been processed successfully by DB.

At a particular instance, DB is down and the messages (msg3, msg4) failed at receiver Adapter. With SP15, we got the feature of restarting these messages after a specific period of time. (Let’s say after every 1hour).

After 5 minutes the DB is up and messages (msg5, msg6) sent by XI have been successfully processed by DB.

After 1 hour, the receiver adapter restarts the failed messages (msg3, msg4) and they get processed successfully.

Now the order in which messages have been processed on the DB:

Msg1, Msg2, Msg5, Msg6, Msg3,Msg4

As messages have not been processed in the sequence they have come from the source system, this would lead to DB inconsistencies.

Kindly suggest how we can overcome this in XI. I don't want to use another Message Oriented Middlware(MOM) like MSMQ, MQSI for this.

Regards,

Siva M

[Former Member]

if you select the Qos as Exactly Once in Order , then you should not have any problem with data incosistancy.

[Former Member]

Hi Siva,

Please can you go through this blog which might help you resolve this issue

/people/vasanthakumar.balasubramani2/blog/2005/12/21/complete-reference-for-idoc-queuing-and-monitoring

Regards

Vijaya