If a delivery receives both sequenced and non-sequenced messages, the non-sequenced messages are delivered immediately, and the sequenced messages are ordered according to their sequential IDs.If messages must be processed in sequence, the client must send them in sequence over a single session. The consummation order can only be fully controlled on the client side (and not by B2Bi).Messages are released one at a time by the delivery in sequential order.Д«2Bi reorders messages according to the order of message assigned by the pickup process for all deliveries. For all deliveries (partner and application), B2Bi orders messages according to the message order assigned by the pickup. Each delivery has one producer per cluster (no multiple parallel production) for sequentially delivered flows.In general, sequential delivery can only work if one and only one output message is generated for each input message. The sequential IDs that are assigned on consumption (pickup) are only taken into account at production (delivery). There is no sequential message handling during the processing phase. Such a limitation would otherwise result in connection errors for clients due to connection limitations. Note: B2Bi cannot limit the number of allowed sessions for a client.The order can only be fully controlled from the side of the client who is uploading the files (and not by B2Bi).The trading engine assigns the order (generating sequential IDs) once the payload starts to be received by the trading engine and the trading engine is ready to send the message for processing.No Axway B2Bi configuration options are available to change this behavior. The FTP LIST results can vary from one FTP server to another. For FTP and SFTP clients, the trading engine assigns the order (generating sequential IDs) according to the order of the files in the list returned by the FTP LIST command.The trading engine assigns the order (generating sequential IDs) based on this FIFO order. For MQ and POP3, messages are presented in a FIFO manner.Each pickup with the sequential message delivery option activated has a single consumer per cluster (no multiple parallel message consumption).Sequential delivery behavior Message consumption (as client)

The behavior of B2Bi for the sequential delivery of messages is determined by processes in both the trading engine and the integration engine. You can currently configure sequential message delivery on the following application and partner pickups: Sequential message delivery is implemented only for trading engine pickups, not for integration engine pickups (listed in the UIВ as 'application transports' in the lists of pickups). How B2Bi manages sequential deliveryДЄ B2Bi internal sequence manager ensures that messages are delivered in the order in which they are consumed, per pickup and per resolved destination partner or application delivery.

This is sometimes referred to as first-in-first-out (FIFO) behavior. Filtered for delivery by the resolved destination application or partner delivery.In the order they were originally consumed on a specific pickup,.In B2Bi message-handling, sequential delivery has the ability to deliver messages:

Sequential order meaning