Problem

* sentinel events sent by a B2Bi using a custom MBC are not sent in the correct order : events newer than other events are received after in Sentinel

OK scenario :

EVENTID   EVENTDATE                    EVENTTIME    STATE
-------   ---------------------------- ------------ -------
183986001 08-05-13                     13:35:13     Success
183986301 08-05-13                     13:35:13     Success
183988701 08-05-13                     13:35:09     Success
183989401 08-05-13                     13:35:13     Ack

KO scenario :

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 to be considered as "non ack"

Resolution

* fields "EVENTDATE" and "EVENTTIME" are set by Integrator (and not by Sentinel), so it is a pure Integrator issue

* it is caused by the fact that there are actually 2 PE in the standard configuration of the Sentinel TA (B2BX PE Sentinel Task 1 and B2BX PE Sentinel Task 1).

* solution available in B2Bi 1.5 SP9 and later

- set the environment variable B2BI_SENTINEL_SEQUENTIAL_OBJECT_IDS to 1 in $CORE_LOCAl/config/environment.dat

- the event can now be sorted using an additionnal colum named UserObjectId's (format: hostname:ObjectId_seqnum).

* a more "native" solution will be implemented in 2.0.2