|
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 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. |
|
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 |
|
Time out
|
During how much time the file will be kept available on the OFTP server.
After this timeout, the file will be automatically removed from the OFTP server (it you did not do it before). If the file was never downloaded, the file will also be marked in ERROR, because it has not reached its destination.
To be warned the soonest possible of errors, we recommend that you set here the lowest possible value. Example : if an automatic process polls the files from here every hour, a value of "3 hours" will allow you to be notified of the problem after just 2 or 3 failed/missing pollings, while a value of "30 days" would lead to files leaving there, without any automatic notification, until some user worries about lack of files.
|