This "How to" should provide you with the necessary steps to implement a working integration with Knight Transportation from scratch using Babelway.
Preferred Protocols and Message Formats. Knight transportation support multiple formats and protocols and are easy to integrate with. We recommend setting up an AS2 connection to send X12 messages and this is what we will document below.
Contact and Resource information.
- Phone number: (602) 606-6364
- EDI team contact: edi@knighttrans.com
Setting up your connection
You can set up a number of connections with Knight Transportation including 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:
Once you have indicated to Knight 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:
Download the AS2 specifications ZIP in the properties tab of your newly created gateway. It contains all you will need to provide Knight Transportation. Note that Babelway supports multiple signing and encryption algorithms.
Knight Transportation will have to send you the following information to complete your configuration:
- The AS2 ID Knight Transportation will use to receive/send your content
- The address of the AS2 server Knight Transportation will be expecting your content to reach
- The certificate you need to use to encrypt your content
You will use this information to create your gateway out:
And complete your gateway in:
Configuring your messages
You may be required to issue functional acknowledgements and you may wish to receive some aswell. If so, check out our 997 implementation:
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.