This "How to" should provide you with the necessary steps to implement a working integration with US Xpress from scratch using Babelway.
Preferred Protocols and Message Formats. US Xpress uses IBM Sterling for all their EDI. We only have experience integrating with US Xpress using AS2 and X12 but knowing their EDI partner it's likely they support additional formats.
Contact and Resource information.
- EDI team contact: check our additional resources section for contact information.
In our exchanges with US Xpress we didn't check for multiple connection possibilities because we directly opted for an AS2 connection. However, knowing they work with IBM's Sterling solution it's likely they support additional integration methods. If you opt for AS2 you general channel construction should look like this:
Once you have indicated to US Xpress that you will be integrating using AS2 they will expect you to share your AS2 information (the US Xpress intake forme is available in the resources section). 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 US Xpress.
You will need to receive from US Xpress the following information to complete your configuration:
- The AS2 ID US Xpress will use to receive/send your content
- The address of the AS2 server US Xpress 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 (note that US Xpress requires you use SHA1 encryption - make sure to update it in the properties tab of your gateway):
And complete your gateway in:
You may wish to send or receive 997 functional acknowledgements for outgoing messages. If this is the case, read up Babelway's 997 implementation: