AS2 Ingress Connector

In order to use the AS2 Ingress 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.

Also you need to have the AS2 Identifier of the remote AS2 trading partner in-order to configure the AS2 Ingress Connector properly. To obtain this you should contact your trading partner over a different medium.

This is a simple scenario which is simulating the use case of receiving an invoice document from a remote partner over AS2 protocol. Here the received invoice file will be store into a local directory and send a 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 AS2 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 AS2MDNCreator 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 AS2MDNCreator will forward the response message to the final element of the flow, which is an NIOHttpDynamicURLEgressConnector. It will send the MDN in a new HTTP request.

In-order to understand the functionality of Attachment Saver element please refer to the reference resource.

For this sample use case, configuration of the AS2 Ingress Connector is as follows.

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

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

For the NIOHttpDynamicURLEgressConnector there are HTTP transport specific properties to be configuration. If required you can customize their default values.