B2B Gateway configuration

A B2B Gateway configuration defines the supported message types and local storage.

The configuration of a B2B Gateway defines the processing for the following types of messages.
AS messages
  • AS1 messages, the flow of inbound and outbound email messages
  • AS2 messages, the flow of inbound and outbound messages
  • AS3 message, the flow of inbound and outbound messages
  • Message Disposition Notification (MDN) to acknowledge the response from Applicability Statement (AS) messages
ebMS messages
ebMS2 messages, which includes the follow types.
  • User message
  • Acknowledgment message to acknowledge the receipt of ebMS2 messages
ebMS3 messages, which includes the following types.
  • User message
  • Signal messages
    • When the message exchange pattern is one-way pull, pull request signal message
    • Receipt signal message to acknowledge the receipt of ebMS3 messages
    • When error occurs in the process, error signal message
  • Notifications to send to the message producer or consumer when certain error occurs.
The B2B Gateway has the following types of local storage.
Metadata storage
All B2B Gateway configurations use the persistent store to store metadata about transactions, not the data used while processing transactions. This metadata is on the unencrypted partition on the RAID volume.
Document storage
Each B2B Gateway, on a service-by-service basis, can store copies of message documents. This space is shared across every B2B Gateway. By default, these documents are on the encrypted partition on the RAID volume.