Created on 2021-01-26 14:55:20; Last updated on 2021-10-26 09:00:47
This "How to" should provide you with the necessary steps to implement a working integration with Oak Harbor from scratch using Babelway.
Preferred Protocols and Message Formats. When integrating with Oak Harbor, you will be expected to send X12 messages through FTP, AS2 or VAN.
Contact and Resource information.
Setting up your connection
You can set up your connection using FTP, AS2, or VAN. We recommend AS2 because it is simple to set up and the most secure. We also strongly discourage the use of VAN which is the lenghtiest setup and incurrs additional costs.
Once you have indicated to Oak Harbor 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 Oak Harbor. In the zip, you will find a .crt file. Note that Oak Harbor's EDI configuration tool requires .cer certificate file. These formats are interchangeable. You can rename the .crt file to .cer. Note that Babelway supports multiple signing and encryption algorithms.
You will need to receive from Oak Harbor the following information to complete your configuration:
- The AS2 ID Oak Harbor will use to receive/send your content
- The address of the AS2 server Oak Harbor will be expecting your content to reach
- The certificate you need to use to encrypt your content
You can get a head start using the configuration information we know of: Oak Harbor resources. You will use this information to create your gateway out:
Note that Oak Harbor sometimes tests the connection prior to configuring the certificate so you may have to leave that blank in the gateway out to send out test files. You can also use this information to complete your gateway in:
Configuring your messages
If you are required or opt to send and receive 997 acknowledgements you can configure this in your message definitions. See 997 implementation: