AS2Gateway Egress 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 Egress Connector. The only difference is now there are multiple AS2 trading stations and multiple trading partners for AS2Gateway. Therefore when sending a message through AS2Gateway Egress Connector it is required to mark the using trading station and trading partner for each and every message. AS2Gateway Egress Connector expects them to be provided to it as transport headers of the message. Therefore before forwarding the message to the egress connector element it is require to add AS2-From transport header with trading station’s AS2 identifier and AS2-To transport header with trading partner’s AS2 identifier.

This is a simple use case of AS2Gateway Egress Connector simulating the use case of sending an invoice document to a remote partner over AS2 protocol. The invoice file that is going to be sent is stored inside a local directory. It will be injected to the UltraESB to send it to the remote trading partner over AS2 requesting a sync MDN. Upon the receipt of the AS2 message that contains the invoice file, the remote trading partner will send a sync MDN message which acknowledge the message receipt. The received MDN will be save into a defined local file to successfully end the AS2 message flow.

For the above scenario it is required to have five elements for the AS2 message flow which will be the configuration for the UltraESB. The first element is a File Ingress Connector which is responsible for picking up the invoice file from the local directory and injecting it to the UltraESB. The next two elements are Add Transport Header elements which will add the AS2-From and AS2-To headers with AS2 identifiers of relevant trading station and trading partner. The fourth element is the AS2Gateway Egress Connector element for send out the AS2 message containing the invoice file. The final element of the flow is a File Egress Connector which is responsible for saving the content of the receiving synchronous MDN into a local file.

In-order to understand the use of File Ingress Connector element, Add Transport Header element the File Egress Connector element please refer to their respective resources.

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

For this sample use case the configuration of the Add Transport Header elements are as follows.

For this sample use case the configuration of the File Egress Connector is as follows.