4.2.2.12. OFTP client Gateway In
With an OFTP Client In Gateway, incoming messages are transferred from an external OFTP server. The Babelway platform polls this server at regular intervals and retrieves files to process them.
The specific settings are:
| Partner SSID | The OFTP ID provided by your partner. |
| Partner SFID | The SFID provided by your partner. If none has been provided, this is probably the same as the SSID. |
| Partner password | The password of your partner. Provided by your partner. |
| My SSID | Babelway is providing an official Odette SSID : O01770000000000X0B5SHARED. Please call support if you want to use a different one. |
| My SFID | An SFID is automatically assigned to your Environment: O01770000000000X0B5xxxxxx. Please call support if you want to use a different one. |
| My password | The value of the password is 'BABELWAY'. |
| OFTP documentation | File containing instructions and certificates for the installation. You should download it and send it to your OFTP partner. |
| Server | The URL of the server of your partner. It is provided by your partner. |
| Port | The port to connect onto. It is provided by your partner. |
| Use TLS | Use TLS (SSL) for communication |
| Secure Authentication Certificate | Use this certificate to perform client side TLS (SSL) authentication. |
| Cron expression | Cron expression. Allows to define complex time expressions like every weekday night at 23:00 (0 0 23 ? * MON-FRI *) and the time zone for the polling. If left empty, the system will check at least once every 15 minutes. For easy creation of your cron expression, you can use the online cron maker tool available at http://www.cronmaker.com/. |
| Use compression | Compresses the messages. |
| Secure Authentication | Use OFTP2 'Secure Authentication'. This will use the certificates defined for encryption and signature. |
| Sign messages | Sign outgoing messages using the key selected in "Signature certificate". This allows your partner to verify that you are the one sending the message. This option is only available with OFTP 2.0. |
| Signature certificate | Select signature certificate or go to certificates store. These certificates are also used for decrypting incomming messages. Multiple certificates for decryption are possible, but only first one in the list is used for signing. This option is only available with OFTP 2.0. |
| Encrypt messages | Encrypt outgoing messages using the certificate selected in "Encryption certificate". This allows your partner to be the only one able to decrypt the messages sent. This option is only available with OFTP 2.0. |
| Encryption certificate | Select encryption certificate or go to certificates store. |
| Encryption algorithm | Select encryption algorithm or go to certificates store. |
| Receive signed messages | This allows you to verify that your partner is the one sending the message using the certificate selected in "Signature verification certificate". This option is only available with OFTP 2.0. |
| Signature verification certificate | Select certificate for data or go to certificates store. |
| Request signed ack (EERP) | Requests that incoming acknowledgments are signed. The signature will be verified using the Certificate selected in "EERP verification certificate". This allows you to be sure that only the partner could have signed the incoming messages. This option is only available with OFTP 2.0. |
| EERP verification certificate | Select certificate for EERP or go to certificates store. |
| Transfer mode | Advanced. Once the connection is open, the OFTP gateway will act as both sender and receiver by default. You can control this by setting the following values : BOTH / RECEIVER_ONLY / SENDER_ONLY |
| Version | Advanced. Babelway supports both OFTP1 and OFTP2. When a connection is open, Babelway uses the OFTP built-in mechanism to negotiate the protocol version. The protocol will be the highest possible. Valid values are : OFTP_V12 for version 1.2 / OFTP_V13 for version 1.3 / OFTP_V14 for version 1.4 / OFTP_V20 for version 2.0 |
| Credit count | Advanced. Control the OFTP "creditCount" parameter. This is the number of data command ( = CREDIT) that could be exchanged prior to an OFTP confirmation from the partner. Default is 64 |
| Data exchange buffer size | Advanced. Control the OFTP "dataExchangeBufferSize" parameter. This is the size of the OFTP data buffer. It should be smaller than the maxBDataLen for ISDN connection. The minimum is 128 bytes and the maximum is 4096 for ISDN and 65535 for TCP connections. Default is 1024 |
After channel deployment, your Oftp server will be available to send messages. You can access this oftp server using any Oftp client software set up with the previous account settings.
If you require a custom SSID / SFID / PASSWORD, please send a request to support@babelway.com .
When a message is transferred to the Oftp server, it is processed immediately then the original file is removed from the server.
Note:
- In the "General" page for this Gateway In you can see the "Poll now" button. When clicking on this button this will poll all of the messages immediately (and will not wait for the next defined moment).
- If there is a file name provided in the "Message In" or "Message Out" which contain ~ tilde character, All browser based on Chromium will replace the ~ tilde character by the _ underscore character when you try to download the file from the Babelway interface, For more details you can check this link https://bugs.chromium.org/p/chromium/issues/detail?id=479419
- You can check bunch of info like last success date, last message date …etc. by pressing on Run Info button.
- The maximum file size accepted by this gateway is 100 MB.