1. Babelway
  2. Babelway User Guide
  3. Chapter 4. Manage & Build

4.2.3.13. OFTP Client Gateway Out

With an OFTP Client out Gateway, outgoing messages are transferred to an external OFTP server.

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 : O01770000000000X0B5xxxxx where xxxxx is the ID of your Babelway environment. Please call support if you want to use a different one. 

 My password 

 The value of the password is 'BABELWAY'. 

 Filename 

 Filename of the outgoing message [with extension if applicable]. If empty, we will apply the default settings. 

 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 to. 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. 

 Skip EERP 

 Select this if your partner is not sending the mandatory EERP. The message will be set in SUCCESS directly after upload. 

 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. 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 is supporting both OFTP1 and OFTP2. When a connection is open, Babelway is using 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 

 File format 

 Advanced. Babelway is supporting all types of records. Valid values are : FIXED / TEXTFILE / UNSTRUCTURED / VARIABLE. Default is UNSTRUCTURED 

 Record max size 

 Advanced. You can specify the record size (only used for FIXED and VARIABLE) 

 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 

 Retry strategy 

 Allows you to determine what to do if call to remote server fails. If 'No retry' is chosen, the message will be put immediately in error. Other values allow to make some retries before setting the message in error. 

  • No retry
  • aggressive
  • Keep trying for 15 minutes
    • Will retries after 2, 4, 7, 10 and 15 minutes.
  • Keep trying for 1 hour 
    • Will retries after 2, 4, 8, 15, 30 and 60 minutes.
  • Keep trying for 3 hours 
    • Will do 6 retries in the first hour, then every hour.
  • Keep trying for 8 hours 
    • Will do 6 retries in the first hour, then every hour.
  • Keep trying for 1 day 
    • Will do 4 retries in the first hour, then every hour.
  • Keep trying for 3 days 
    • Will do 5 retries in the first 2 hours, then every 3 hours.
  • Keep trying for 5 days, once a day 
    • Will do One retry every day for 5 days at the same time as the first try.
  • Keep trying for 7 days 
    • Will do 5 retries in the first hour, then every 3 hours for 3 days, then every 6 hours.

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.

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: When sending the message through this "Gateway Out" and the message fell in error "Unable to establish TLS connection to remote OFTP server for SSID XXXXXXXXXXX due to : General SSLEngine problem", This error means that there is a problem occurred while building SSL connection with the remote server, In order to fix this issue we will need to trust the self-signed SSL certificate used in the remote server by following the below steps.

1-From the "certificates" page in the "Trusted certificates" tab click on the "Trust new certificate" button.

Provide the sever IP and Port or URL and Port in the "Trusted Url" field then click on the "Trust root certificate", as shown below.

2020-02-24_13_05_20-Babelway.png

Trusting URL

 

After that done forget to deploy the environment in order to push this changes to production, Then the messages should be processed successfully.

Note:

  • 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
  • The maximum file size accepted by this gateway is 100/250 MB.