KB Article #175928
sentinel events not sent in the correct order
Problem
* When using an MBC to send events to Sentinel in B2Bi, events may not be correctly ordered : older events may be sent after newer events* Exemple :
EVENTID EVENTDATE EVENTTIME STATE
------- ---------------------------- ------------ -------
183998701 08-05-13 14:51:34 Success
183999401 08-05-13 14:51:35 Ack
184000501 08-05-13 14:51:33 Success
184001101 08-05-13 14:51:34 Success
in such example, the ack should be received at the end. from a functional point of view, it causes the message be considered as non ack
Resolution
1- if the tracked objects is a native TA (XIBTransfer, XIBMessage...)
- set B2BI_SENTINEL_SEQUENTIAL_OBJECT_IDS=1 in Integrator profile
- a new filed called UserObjectId can now be used to sort events sequentially
- UserObjectId's will be automatically populated : hostname:ObjectId_seqnum
2- if the tracked objects is a custom TA
- set B2BI_SENTINEL_SEQUENTIAL_OBJECT_IDS=1 in Integrator profile
- in your MBC code
-> generate a unique id using the 4edi UNIQUE api using a file stored on the file system
-> set the UserObjectId with this unique id and use it to sort events sequentially