eAdaptor Relay for CargoWise
The eAdaptor Relay middleware service for CargoWise removes limitations and adds versatility when using the CargoWise eAdaptor Outbound Service.
CargoWise's eAdaptor Outbound Service only allows a single Outbound eAdaptor Service URL to be configured, limiting integration opportunities. The eAdaptor Relay middleware negates this limitation and introduces additional options, such as filtering and forwarding messages to different integrations, transforming the messages into different formats, and removing sensitive details, such as financial data.
Existing eAdaptor integrations can be preserved and continue to function with the eAdaptor Relay, forwarding the original eAdaptor Outbound SOAP messages to existing integrations.
Example
A popular 3rd party CargoWise integration is BravoTran. BravoTran would typically be setup directly using the Outbound eAdaptor Service URL System Registry setting in CargoWise:
Adding the eAdaptor Relay middleware service the setup becomes:
This allows any number of integrations to added side-by-side with BravoTran:
Prerequisites
Before the eAdaptor Relay can be used the following prerequisites are required:
- CargoWise eAdaptor Outbound Service setup.
- CargoWise Organization Proxy configuration.
- CargoWise Workflow Templates added.
You can reduce the amount of traffic you send to the eAdaptor Relay by setting up CargoWise Workflow Templates targeting the specific clients you wish to integrate with.
Functionality
The functionality provided by the eAdaptor Relay can be mixed and matched as required, coming under the following categories:
- Forwarding - Forward messages to other eAdaptor integrations, APIs, low code apps, message queues, storage, email, or anything else you'd like to integrate with.
- Filtering - Filter messages based on CargoWise module, organization, or anything else within the message for relaying to different systems.
- Transforming - Remove sensitive details, such as financial data, from a message before forwarding it on to a 3rd party. Transform messages for compatibility with other systems, using JSON / XML / CSV or any other format required.
When no catch-all functionality rules exist and messages don't match any filtering rules, those messages will be discarded by the eAdaptor Relay.