Client Connection Tab - NEW! 🚀

Warning!

The search bar at the top of the result list does not support blanks and these special characters: ' " |

To configure a Client Connection, follow these steps:

1. Go to Actors → Edit Actor → Client Connection tab.
2. Click the New Client Connection button.
3. In the dialog window, select the protocol type.

4. The dialog window will load several new fields – refer to the following sections for a detailed explanation of each field.

Open protocols

• FTP
• FTPS
• SFTP
• HTTP
• HTTPS
• PESIT
• SMB v3 or later versions
• POP3 IMAP
• SMTP

Primeur protocols

• PR4/PR4S
• PR5
• PR5S

Cloud connectors

• HDFS
• HDFSS
• Amazon S3
• Google Storage
• Azure Blob Storage

Third party connectors

• IBM Sterling Connect:Direct

Client Connection Appendixes

IBM JCE FIPS v1.8 algorithms

The supported Fips Compliance algorithms are:

Ciphers

Signature

Signature verification

Key agreement

Key (pair) generation

Message authentication code (MAC)

The keys must be at least 112 bits.

Message digest

Algorithm parameters generator

Algorithm parameters

Key factory

Secret Key factory

Certificate

Random number generation

Key generation

Key agreement

Encryption and decryption

Signature generation

Signature verification

Message authentication

Message digest

Accepted Cipher Suites

List of cipherSuites accepted to establish a SSL connection. Possible values:

Default Charset

Default charset used to convert the received text external file. Possible Values:

Client Connection Retry Settings

FTP/FTPS/SFTP Client Connection Retry Settings

If a line error occurs during the connection phase, FAILED_RETRY is set and multiple retries are performed.

After a failed connection, FAILED_RETRY is set and several attempts are made.

In case of LS and MKDIR, the following exceptions apply:

• LS: if there are no files in the selected directory, no errors are generated and the operation terminates successfully.
• MKDIR: if the directory to create exists, no error is generated and the operation terminates successfully.

PR4 Client Connection Retry Settings

Errors setting FAILED_RETRY if the maximum number of attempts is not reached:

PRIMEUR SPAZIO Errors:

PRIMEUR Data One Errors:

PR5 Client Connection Retry Settings

Errors setting FAILED_RETRY if the maximum number of attempts is not reached:

PRIMEUR SPAZIO Errors:

PRIMEUR DATA ONE Errors:

Errors always setting FAILED_RETRY without checking the maximum number of attempts configured:

PRIMEUR Data One and PRIMEUR SPAZIO Errors: