This guide walks you through how to connect your CargoWise Next EDI Client to Chain.io. You’ll learn how to:

• Set up your EDI Client in CargoWise

• Configure a host system in Chain.io

• Link outbound and inbound data flows

• Exchange security certificates for OAuth

• Finalize your OAuth setup

• Use the integration to send and receive data between CargoWise and Chain.io

By the end, you’ll have a fully configured integration that supports secure, bidirectional messaging—without the need for custom development or complex OAuth certificate management. 

Key Terminology

Key Terminology

EDI Client (CargoWise)
A setup inside CargoWise that manages how messages are sent and received through electronic data interchange (EDI). Think of it as the bridge between CargoWise and external systems.

Chain.io Host System
This is the digital handshake point inside Chain.io. It defines how we connect to your CargoWise EDI Client and manage the data exchange.

Outbound (CargoWise → Chain.io)
Settings for sending messages from CargoWise to Chain.io. This includes authentication credentials and endpoint URLs.

Inbound (Chain.io → CargoWise)
Settings for receiving messages from Chain.io into CargoWise. You’ll configure server info and certificates here.

Authentication Types

• Basic Authentication: Username and password-based. Used for outbound messages.

• OAuth Authentication: Certificate-based. Required for inbound messages from Chain.io to CargoWise.

CSR (Certificate Signing Request)
A file generated in Chain.io used to request a digital certificate from CargoWise. It ensures secure communication using OAuth.

Certificates
Digital credentials used for secure communication. CargoWise certificates must be updated annually and prioritized (Primary or Secondary).

Endpoint
The specific URL that tells CargoWise where to send messages. You’ll copy this from Chain.io into your EDI Client settings.

Step By Step

1. Create or Update the EDI Client in CargoWise

1. Navigate to the EDI Client Details
   • In CargoWise, go to Maintain > EDI Messaging > EDI Details.
   • Open your existing EDI Client or create a new one.
2. Configure Basic Details Settings
   • Select the Basic tab
   • Connection Type: Set to EAN - eAdaptorNext.
   • Client Name: Enter a name. Recommendation: Use the same name you’ll use in Chain.io for easier tracking.
   • Enabled: Check this box.
3. Outbound Tab (CargoWise → Chain.io)
   • Authorization Type: Select Basic Authentication.
   • Active: Check the box.
   • Save your changes.

2. Create the Host System in Chain.io

1. In your Chain.io workspace, go to: Workspace Settings > Host Systems > Add Host System.
2. From the dropdown, select CargoWise Next EDI Client.
3. Host System Name: Use the same name as in CargoWise (recommended for easy identification).
4. Hosting Style:
   • If your CargoWise is run on your own servers: select Self-Hosted.
   • Otherwise (most cases): select WiseCloud Hosted.
5. Save to create the host system.

3. Link CargoWise Outbound to Chain.io

In order to allow your CargoWise Next EDI Client to send data to the Chain.io platform, follow these steps:

1. Open your new host system in Chain.io.
2. Go to the Send Messages to Chain.io tab.
3. Status: Set to Active.
4. Authorization Type: Select Basic Authentication.
5. Username and Password: Create credentials here. These must exactly match what you’ll enter in CargoWise. We recommend using strong passwords that are at least 15 characters.
6. Save.
7. In CargoWise, make sure you are still showing the EDI Client's Outboundb tab:
   • Enter the Username and Password you created in Chain.io.
   • Copy the Endpoint from the Chain.io host system (format: https://data-api.chain.io/cargowise-next/...) into CargoWise’s Endpoint field.
8. Save in CargoWise.

4. Link CargoWise Inbound to Chain.io

In order to allow the Chain.io platform to send data to your CargoWise Next EDI Client:

1. In your Chain.io host system, go to the Send Messages to CargoWise tab.
2. Status: Set to Active.
3. Enter your Enterprise Code and Server Code:
   • Enterprise Code = first three characters of your CargoWise license.
   • Server Code = last three characters of your CargoWise license.
   • Choose the correct server for production, staging, or testing.
4. Authorization Type:
   • For WiseCloud Hosted: select OAuth Authentication.

5. Exchange Certificates

CargoWise Next uses an OAuth authorization strategy that requires both systems to exchange security certificates.

1. In the Chain.io host system:
   • Click Add Certificate.
   • Common Name: Set to Chain.io or another name that will help identify the certificate in Cargowise.
     • Once you generate the CSR the Common Name cannot by modified.
   • Click Generate CSR.
   • Download the CSR file.
   • Save the host system.
2. In CargoWise:
   • Go to your EDI Client’s Inbound Tab.
   • Authorization Type: OAuth Authentication.
   • Active: Check the box.
   • Set your default Branch and Department.
   • Save the EDI Client.
   • In the text box, next to Certificate Request File, click the three dots and upload the CSR file you downloaded from Chain.io.
   • To verify Cargowise can utilize the CSR, click the Verify button.
   • Click Generate Certificate.
   • Click the Refresh Certificates button until the certificate appears in the list.
     • CargoWise may take several minutes to process the certificate.
   • When the new certificate appears in the list, select it and download it to your computer.
   • Save the EDI Client.
3. In your Chain.io Host System:
   • Drag and drop the downloaded CargoWise certificate into the CargoWise Client Certificate box.
   • Verify the Valid From and Valid To dates.
     • CargoWise client certificates are currently valid only for one year.
   • Certificate Priority For production, set this certificate as Primary.
     • The Priority is utilized by flows to determine which certificate to use to communicate with your CargoWise system.

To prevent communication interruptions, new certificates must be added before the existing certificate's Valid To date. Follow the instructions in this section to add the new certificate. When configuration in both systems is complete and the new certificate is ready for use, set its priority to Primary and change the old certificate's priority to Secondary.

After the Chain.io host system is saved, the new Primary certificate will be pushed to all flows configured to use the primary certificate.

6. Final OAuth Setup

1. In CargoWise EDI Client, note the generated:
   • OAuth Authority URL
   • Client ID
   • Scope
2. Copy these into the corresponding fields in Chain.io.
3. Save the host system.

7. Use the Host System

• Sending data from Cargowise to Chain.io
  • In Chain.io, use your new the Host System as a Source System in a Send Flow
  • In CargoWise, associate the EDI Client in the appropriate Organization's EDI Communications tab.
• Sending data from Chain.io to Cargowise
  • In Chain.io, set the Host System as a Destination System in a Receive Flow.
    • For production workflows, the Always use Primary certificate option in the Destination System flow configuration should be enabled. This ensures the flow always uses the certificate marked as Primary on the host system page, allowing new certificates to be added before the old ones expire without requiring updates to the flow configuration.

Frequently Asked Questions

• This seems a lot more complicated than the legacy eAdaptor setup. Why?
  With eAdaptor next, CargoWise implemented a more secure way to connect to your eAdaptor using a standard called OAuth and a technology called signed certificates.  This sacrifices some convenience for additional security.  With Chain.io, you get the benefit of having all of the certificate details managed for you which is a lot more simple than doing it yourself.
• eAdaptor Next supports additional authentication methods for outbound connections, but Chain.io only supports Basic.  Is this a problem?
  "Basic Authentication" is a commonly used standard across the internet and is a well accepted methodology for authentication when you are working within an already encrypted channel (like the HTTPs protocol used by eAdaptor).  We are confident that this provides the best balance of security and usability for our customers and their data.
• Do I have to migrate all of my existing connections to eAdaptor Next?
  Chain.io will not require you to migrate away from Legacy eAdaptor as long as it remains a Cargowise feature.