AS2Gateway Ingress Connector

In order to use the AS2Gateway Egress Connector you must first select the "AS2 Connector" dependency from the connector list when you are creating an empty Ultra project. If you have already created a project, you can add the "AS2 Connector" dependency via Component Registry. From Tools menu, select Ultra Studio → Component Registry and from the Connectors list, select the "AS2 Connector" dependency.

As a prerequisite to use the AS2Gateway Egress Connector it is required to prepare a resource configuration which contains required AS2 trading station/partner information.

To create a resource with required information, you should open the project.xpml file in Design mode. Then select AS2 Trading under Custom Templates menu. This will open a list of input parameter where you need to enter the relevant information in input fields inorder to configure the AS2 Trading information resource.

Following scenario is almost similar to the sample scenario that we have discussed under AS2 Ingress Connector. The only difference is now there are multiple AS2 trading stations and multiple trading partners for AS2Gateway. Here the received invoice file will be store into a local directory and send an Message Disposition Notification (MDN) to the trading partner. The MDN is the response to the trading partner which contains the processing status of the received AS2 message. The MDN can be sent as the response to the received AS2 message (sync MDN) or else it will be sent as a new AS2 message (Async MDN) to the trading partner. It will be decided on the preference of the trading partner which will be included in the receiving AS2 message.

For the above scenario it is required to have four elements for the AS2 message flow configuration of the UltraESB. The first element is a AS2Gateway Ingress Connector which is responsible for receiving the AS2 message, parsing it to extract the invoice file, set the extracted invoice as a attachment of the message and finally preparing the response for the message and add it as the response message payload. The second element is a Attachment Saver element which is responsible for saving the invoice file into a user defined local directory. The third element is a MDN Option Evaluator which will evaluate requested format of MDN. If the remote trading party has requested a synchronous MDN then it will invoke the response message which will contain the MDN message through its Sync MDN Requested out port. If the remote trading party has requested for a asynchronous MDN then the MDN Option Evaluator will forward the response message to the final element of the flow, which is an AS2 Async MDN Sender. It will prepare and send the MDN in a new HTTP request.

In-order to understand the functionality of Attachment Saver element, MDN Option Evaluator element and the AS2 Async MDN Egress Connector element please refer to their reference resources.

For this sample use case, configuration of the Attachment Saver element is as follows.

For the MDN Option Evaluator there are no any configuration parameters to be configures, you just need to place it in the flow.

For the AS2 Async MDN Egress Connector there are HTTP transport specific properties to be configuration. If required you can customize their default values.