# Client Connection: PR5S

Fields with the asterisk **\*** are mandatory.

<table><thead><tr><th width="230.00006103515625">Properties</th><th>Description</th></tr></thead><tbody><tr><td><strong>STATUS</strong></td><td><p>Enable or disable the client connection. Possible values:</p><ul><li>Enabled (default)</li><li>Disabled</li></ul></td></tr><tr><td><strong>NAME *</strong></td><td>Name of the PR5S connection you are creating. The maximum number of characters is 128. Blanks and the ' " | special characters are not supported.</td></tr><tr><td><strong>DESCRIPTION</strong></td><td>Description of the PR5S connection you are creating. The maximum number of characters is 2048.</td></tr><tr><td><strong>HOST *</strong></td><td>Remote host IP Address or hostname.</td></tr><tr><td><strong>PORT *</strong></td><td>Port to connect to the remote host (1 to 65535).</td></tr><tr><td><strong>USERNAME</strong></td><td>Username to be used for the connection. The maximum number of characters is 320.</td></tr><tr><td><strong>PASSWORD</strong></td><td>User password.</td></tr><tr><td><strong>CONNECTION TIMEOUT *</strong></td><td>Number of seconds without network activity to wait before closing a session due to inactivity.<br>Default value: 60.</td></tr><tr><td><strong>CONNECT THROUGH DMZ</strong></td><td><p>Enable or disable DMZ proxy. Possible values:</p><ul><li>Enabled</li><li>Disabled (default)</li></ul></td></tr><tr><td><strong>SELECT DMZ CLUSTER</strong></td><td>When the <strong>Connect through DMZ toggle</strong> is enabled, this drop-down list displays all DMZ Clusters configured in <strong>Setup</strong> → <a href="/pages/4oSvqNmGyG9JKaK1PoxP">DMZ Clusters</a>. When you select one or more DMZ clusters, they will be applied to the client connection. If one of the selected DMZ clusters is unavailable, the remaining DMZ clusters will be used in <strong>RUNTIME</strong> or <strong>ROUNDROBIN</strong> mode. If no DMZ cluster is selected, all configured DMZ clusters will be used automatically.</td></tr><tr><td><strong>QMANAGER NAME *</strong></td><td>Name of the remote Queue Manager.</td></tr><tr><td><strong>CLIENT KEY LABEL</strong></td><td>Key identifier to create the SSL connection.</td></tr><tr><td><strong>USE EXTERNAL KEYSTORE</strong> *</td><td>Enable this toggle button if an external HSM is used. These fields will appear:<br>- <strong>tokenType</strong>: string provided by the HSM vendor.<br>- <strong>tokenName</strong>: string provided by the HSM vendor.</td></tr><tr><td><strong>SSL AUTHENTICATION PROTOCOL</strong></td><td><p>Select the SSL authentication protocol:</p><ul><li>ALL</li><li><p>ONLY SPECIFIC VALUES:</p><ul><li>SSLv3</li><li>TLSv1</li><li>TLSv1_1</li><li>TLSv1_2</li><li>TLSv1_3</li><li>SSLv2Hello</li></ul></li></ul></td></tr><tr><td><strong>ACCEPTED CIPHER SUITES</strong></td><td><p>Select the cipher suites. Possible values:</p><ul><li>ALL</li><li>ONLY SPECIFIC VALUES. See <a href="/pages/bXblCQPvaPonLHqKDwk2#accepted-cipher-suites">ACCEPTED CIPHER SUITES</a> for details.</li></ul></td></tr><tr><td><strong>SIZE OF SYNC POINT WINDOW</strong></td><td>This value is in bytes and sets when the client and the server must synchronize during the file transfer. This synchronization is important for the restart. The default is 10240000 bytes.</td></tr><tr><td><strong>LOCAL QMANAGER *</strong></td><td>Name of the first local directory in the Virtual Path. It can be found in <strong>Actor</strong> → <strong>Edit</strong> → <strong>VFS tab</strong> → <strong>Edit VFS</strong>.</td></tr><tr><td><strong>INTERNAL CONNECTION</strong></td><td>This parameter provides additional information to the PR5s client connection. It must be set only if the client connection is used to exchange files between clusters in the same installation.<br>The purpose of this parameter is to propagate the Dataflow Instance ID (DFIID) from the master transfer to the server transfer during file transfer operations. Without this parameter, the DFIID is no transmitted. By enabling it, both the master and the server transfer share the same DFIID value, allowing Data Watcher to correlate the master and slave transfers as part of the same dataflow.</td></tr><tr><td><strong>MATCH SERVER HOSTNAME</strong></td><td><p>Specify whether the client should verify that the server’s certificate matches the hostname (the <strong>HOST</strong> value) it is connecting to.</p><ul><li><strong>Enabled:</strong> the client checks that the server’s certificate Distinguished Name (DN) includes the IP address or hostname that was contacted.</li><li><strong>Disabled (default):</strong> no hostname verification is performed.</li></ul></td></tr><tr><td><strong>CONFIGURATION TEST</strong></td><td>Use this section to test that the <strong>Cluster</strong> and the <strong>STENG</strong> are connected correctly. Select a <strong>Cluster</strong> and a <strong>STENG</strong> you want to test and click the <strong>TEST</strong> button. Data One <strong>automatically</strong> selects a <strong>Cluster</strong> and a <strong>STENG</strong> to test the connection. Note that a Cluster will be selected only if it is the only one available.<br>A message with a green check will confirm a successful connection. A message with a red exclamation mark will warn about an unsuccessful connection. The message also details the reason why the connection fails.<br>The connection might not be successful for different reasons, each of them depending on the transfer type and the configuration.<br>The first time you try to test the connection, if trusting certificates are missing, an error message detailing the unsuccessful connection will appear. In this case, go to the <strong>Setup</strong> → <strong>Untrusted Cache</strong> → <strong>Certificates</strong> tab and trust the relevant certificates.<br>Note that trusting certificates in the Untrusted Cache page may not be sufficient to establish a successful connection. Refer to the <a href="/pages/riYYXT6YPDLkxQCEKrVk">Untrusted Cache</a> section of this documentation for all the details.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.primeur.com/data-mover-1.21/transfer-protocols-and-connectors/client-connections/client-connection-pr5s.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
