6.8.25. How to Integrate with Swift Transportation?

This "How to" should provide you with the necessary steps to implement a working integration with Swift Transportation from scratch using Babelway.

Figure 6.145. 


Preferred Protocols and Message Formats. When integrating with Swift Transportation, you will be expected to send X12 messages through FTP, AS2, or VAN. They have a preferences for working with FTP and AS2.

Setting up your connection

You can set up a number of connections with Swift Transportation since they support FTP, AS2 and VAN. We discourage the use of VAN as it involves additional costs and is the least straightforward setup. We will describe the setup using an AS2 connection which is the most secure protocol. Your channel will look something like this:

Figure 6.146. 


Once you have indicated to Swift Transportation that you will be integrating using AS2 they will expect you to share your AS2 information. In order to provide this, you can begin by creating a dummy AS2 gateway in:

Figure 6.147. 


Download the AS2 specifications ZIP in the properties tab of your newly created gateway. It contains all you will need to provide Swift Transportation. Note that since Swift Transportation is already connected to us for other integration flows, Babelway's IP adresses are already white listed in their firewall.

You will need to receive from Swift Transportation the following information to complete your configuration:

  1. The AS2 ID Swift Transportation will use to receive/send your content
  2. The address of the AS2 server Swift Transportation will be expecting your content to reach
  3. The certificate you need to use to encrypt your content

You will use this information to create your gateway out:

Figure 6.148. 


And complete your gateway in:

Figure 6.149. 


This documentation is based on our integration projects but we'd love to enhance and update it with your own feedback and experience: support@babelway.com.

Last update: June 06 2018