4.2.1. Creating Gateways
A channel always starts with a gateway in to receive an incoming message and sends it back out through a gateway out.
In both cases, you will have to choose the appropriate technology to connect to the target system. The list is vast and comprises many technologies. One of those may have prompted you to use Babelway in which case you know exactly which one you need. If not, here are some things to keep in mind when choosing your gateway.
Server vs Client Gateways
Security
Some protocols come with a built in security mechanism: AS2, Peppol, OFTP are some examples. Other protocols give you the choice of how you wish to authenticate. HTTP/REST, for instance, supports multiple authentication options. The latter are then only as secure as the security you configure in them. So watch out for this when selecting your gateway.
Simplicity of the Transformation
Many protocols don't enforce the message type that they exchange and this is easiest (email, FTP, etc). Others have preferred messages types (HTTP clients often consume APIs supporting only JSON or XML). Finally, some protocols impose the message formats you can use (Peppol works with UBL, VAN works with X12). You are then tied to that message definition. Thus, where it may be less straightforward to use Peppol than to use FTP, you may find that your transformation will be simpler going from a UBL to your homegrown XML than if you're converting complicated PDFs received by mail.
Cost
Babelway doesn't charge per channel or per gateway, so there aren't any specific costs incurred when choosing your protocol except for 2 technologies:
- VAN - value added network
- X400
Both gateways interact on private networks for which there is an additional per message fee. Reach out to Babelway billing for any additional information on what that could mean for you.