This "How to" should provide you with the necessary steps to implement a working integration with MercuryGate from scratch using Babelway.
Preferred Protocols and Message Formats. When integrating with MercuryGate, you will be expected to send X12 (version 4010) messages through FTP.
MercuryGate uses FTP. Your channel will look something like this:
For FTP, create an "FTP Client" gateway IN as follows. Note that MercuryGate needs to share with you the information required to complete the highlighted section.
In order to send content to MercuryGate, you will need to complete the matching FTP client outgoing gateway:
Once again, you will need MercuryGate to share the highlighted information with you. Most likely, only the directory will differ between the two gateways and you will use the same credentials to log in to their FTP server.
Whether you begin with the incoming or outgoing flow, you can test your connection by creating a dummy channel using your newly created gateway, "Not defined" message definitions and a "no transform" transformation to just ensure that you can exchange content with MercuryGate correctly. Next, you will want to validate that you can correctly convert your format to theirs in a way that matches their requirements.
You can find all the samples for their messages in the resources bundle.
MercuryGate will send back 997 functional acknowledgements for each motor carrier freight details and invoice (210) you send out. If you wish to correlate incoming acknowledgements with the 210 messages you issue, you can have a look at Babelway's 997 implementation.