AS4 use case: One-way push (MMD initiated)

About this use case

This use case describes a message exchange scenario in which Activator pushes an AS4 message to a remote trading partner and a receipt is returned from the receiving partner to the sending (push) partner. In this case, message delivery (push) is initiated by the consumption of an ebMS v3 MMD from a back-end file directory.

This topic describes the configuration of both the sending and receiving participants on Activator platforms.

Assumptions

• The sending and receiving partners have agreed on a common configuration for partition channel, security and acknowledgements.

Processing events

The following figure illustrates the sequence of transfer events.

In this figure the following events occur:

1. Activator consumes an ebMS V3 MMD from the back-end file system.
2. Activator message handler analyzes the MMD and detects that it is an AS4 type.
3. Activator applies AS4 collaboration settings and builds and packages the outbound AS4 user message. This includes any message payloads that are specified in the MMD.
4. Activator sends the AS4 user message using the partner AS4 delivery exchange.
5. The remote partner receives the AS4 message and returns a receipt in the form of an AS4 signal message.
6. Activator consumes the inbound receipt over the synchronous connection.

Configure the sending (push) participant

To configure the MMD-initiated push of an AS4 message to a remote partner (with return receipts activated), complete the following sequence of tasks. For additional information on completing each task, follow the links:

1. Create an MMD to use to initiate the AS4 push.
2. See AS4 metadata.
2. Add a Community to specify characteristics of Activator as the sending AS4 exchange participant.
3. See Add a community.
3. Add a Partner to specify the characteristics of the remote partner as the receiving participant.
4. See Add a partner.
4. Add a file system type Application Pickup to enable the Community to consume the AS4 MMD from the back end.
5. See Add an application pickup.
5. Configure Community AS4 collaboration settings to control the packaging of the AS4 outbound user message. In this case we select the option "Expect receipts from partners". When we do this, the push receiving partner must also activate receipts.
6. See AS4 default settings.
6. Add a Partner AS4 delivery to enable the connection to the receiving partner.
7. See Add an AS4 trading delivery.

Configure the push receiving participant

To configure the receiving participant of an AS4 push, and activate return receipts, complete the following sequence of tasks. For additional information on completing each task, follow the links:

1. Add a Community to specify characteristics of Activator as the receiving AS4 exchange participant.
2. See Add a community.
2. Add a community AS4 pickup to enable the reception of the pushed AS4 user message.
3. See Add an AS4 embedded server pickup.
3. Modify the AS4 pickup to enable receipts. On the maintenance page Advanced tab you must select the option: Generate receipt.
4. See Modify an AS4 embedded server pickup.
4. Configure Validation Rules to control how Activator consumes the AS4 pushed user message.
5. Add a Partner to specify the characteristics of the original sending participant in this exchange.
6. See Add a partner.

Related topics

• AS4
• AS4 messages
• AS4 metadata
• Message Partition Channels (MPC)
• AS4 user authentication
• Large message splitting and joining
• Enable handling of empty SOAP Body messages
• Configure a one-way client pull
• AS4 use case: One-way pull (MMD initiated)
• AS4 tasks