# Server Connection: PR4

When configured on multiple STENG peers, the PR4 server provides active-passive High Availability. This implies that outbound and inbound jobs using the PR4 protocol will only run in one of the peers.

The first peer activated gets priority activation of the PR4 server.\
Peers activated later will remain in idle status.\
In case of deactivation or crash of the first peer, the system will assign activation priority to one of the other peers that are still active.

In mini systems (i.e. excluding zOS), idle servers are activated in mirror mode in order to redirect incoming traffic to the one and only active server.

{% hint style="info" %}
Intentionally stopping the PR4 server in the peer that holds the PR4 activation priority does not change the configuration of the priority assignment. So, PR4 jobs will not be executed until the server is started.
{% endhint %}

Fields with the asterisk \* are mandatory.

<table><thead><tr><th width="223.59991455078125">Value</th><th>Description</th></tr></thead><tbody><tr><td><strong>SERVER NAME *</strong></td><td>Enter a unique name for the server.</td></tr><tr><td><strong>DESCRIPTION *</strong> </td><td>Provide a brief description of the server.</td></tr><tr><td><strong>PORT *</strong></td><td>Enter the port to connect to the server. This is the TCP/IP port the server will listen to in the STENG node.</td></tr><tr><td><strong>NODE NAME *</strong></td><td>Enter the SPAZIO system local name.</td></tr><tr><td><strong>QMANAGER NAME *</strong></td><td>Enter the SPAZIO local Queue Manager.</td></tr><tr><td><strong>SERVER KEYLABEL</strong></td><td>Select the key identifier about keystore store to select Private Key and Certificate to create SSL connection.</td></tr><tr><td><strong>PPS COMPRESSION SUPPORT</strong></td><td>Enable if the server must accept compression using PPS.</td></tr><tr><td><strong>PPS HASH ALGORITHM</strong></td><td>Select the algorithm used by PPS for hashing. Possible values:<br><strong>NULLHASH</strong><br><strong>MD5</strong><br><strong>SHA1</strong><br><strong>SHA_256</strong><br><strong>SHA_384</strong><br><strong>SHA_512</strong></td></tr><tr><td><strong>PPS CRYPTO ALGORITHM</strong></td><td>Select the algorithm used by PPS for cryptography. Possible values:<br><strong>NULLCIPHER</strong><br><strong>DES_CBC</strong><br><strong>DES3_CBC</strong><br><strong>RC4</strong><br><strong>DES3_CBC_EDE2</strong><br><strong>AES256_CTR</strong><br><strong>AES192_CTR</strong><br><strong>AES128_CTR</strong></td></tr></tbody></table>

<table><thead><tr><th width="225.20001220703125">DMZ mode</th><th></th></tr></thead><tbody><tr><td><strong>NONE (default)</strong></td><td>No session proxying through DMZ Gateway applied.</td></tr><tr><td><strong>PORT_FORWARDING</strong></td><td>Incoming/Outgoing connections to/from STENG server will be proxied inside an SSL tunnel without being validated in advance.<br><strong>OUTGOING LINE IPADDR *</strong>: Enter the address used by outgoing connections via DMZ.<br><strong>OUTGOING LINE PORT *</strong>: Enter the port used by outgoing connections via DMZ.</td></tr><tr><td><strong>SESSION_TERMINATION</strong></td><td>The server session will be terminated inside the DMZ Gateway, before data is sent to STENG server.<br><strong>DMZ PROXY PORT *</strong>: This port represents the tunnel that is opened for connection with the STENG Server.<br><strong>SERVER PORT *</strong>: Enter the DMZ server port to be used for the connection.<br><strong>OUTGOING LINE IPADDR *</strong>: Enter the address used by outgoing connections via DMZ.<br><strong>OUTGOING LINE PORT *</strong>: Enter the port used by outgoing connections via DMZ.</td></tr></tbody></table>

To change any DMZ port of a PR4 server that belongs to a peer, select the server you want to update. Next, click the pencil icon in the top-right corner of the server card. Enter the new port or ports in the appropriate fields. Finally, click the **SAVE** button to confirm your changes. Remember that the new port number will only affect the peer's selected server.


---

# 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/server-connections/server-connection-pr4.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.