Compress Data
Controls compression of data transmitted across the network. Select the checkbox to turn this option on.
 
Encrypt Data (Using option selected below)
Controls encryption of data transmitted across the network. Select the checkbox to turn this option on.
This option sets a default value that is used when the encrypt parameter of the open statement is omitted. The configured default may be overridden at any time from the open statement.
When this value is set to a specific SSL/TLS cipher, UDM always requests that cipher when encrypting data.
Note that if the target UDM Server does not support the selected cipher (as indicated by the Server's configured data SSL/TLS cipher list), the encryption request fails.
 
When this option is checked and no specific cipher is specified, UDM uses the Manager and Server's configured data SSL/TLS cipher list to negotiate the encryption method.
 
When the data encryption checkbox is selected, you may select an item in this list to set the UDM Manager's encrypt configuration option to an SSL/TLS cipher. UDM then requests this cipher whenever it encrypts the data it transfers. Note that if the target UDM Server does not support the selected cipher (as indicated by the Server's configured data SSL/TLS cipher list), the encryption request fails.
 
The following cipher suites are available:

When the data encryption option is checked and the (negotiate using data SSL/TLS cipher list) item is selected, the encrypt option is set to yes, which instructs UDM Manager to negotiate the encryption method with the Server, using their respective data SSL/TLS cipher lists.

Universal Data Mover uses the SSL/TLS protocol for internal communication between application components. A control session is established within the application that provides the connections necessary for this communication to take place. The SSL/TLS cipher suites available for communication across the control session are listed here.
 
The selected cipher suites will be forwarded to the Universal Data Mover Server. The Server will compare this list to its own list of ciphers it is capable of accepting. The result of the comparison will be an agreed-upon cipher used for communication over the control session. If you are unsure which ciphers will be accepted by the Server, it is best to leave them all selected. Use the up/down arrows on the right to sort the list and establish a priority for the selected ciphers. The first one in the list that is accepted by the Server will be the one used.
 
The following cipher suites are available:

To disable SSL/TLS encryption and message authentication for messages transmitted across the control session, select the NULL-NULL entry. Use of this cipher requires that the remote UDM Server's encrypt_control_session option be set to no. Otherwise, the UDM Server will issue a protocol error when the Manager tries to establish the control session with it.

<ul>
<li> RC4-SHA -- 128-bit RC4 encryption, SHA-1 message digest 
<li> RC4-MD5 -- 128-bit RC4 encryption, MD5 message digest 
<li> AES256-SHA -- 256-bit AES encryption, SHA-1 message digest 
<li> AES128-SHA -- 128-bit AES encryption, SHA-1 message digest 
<li> DES-CBC3-SHA -- 128-bit Triple-DES encryption, SHA-1 message digest 
<li> DES-CBC-SHA -- 128-bit DES encryption, SHA-1 message digest
<li> NULL-SHA -- No encryption, SHA-1 message digest 
<li> NULL-MD5 -- No encryption, MD5 message digest 
<li> NULL-NULL -- Disables the SSL protocol 
</ul>

When the data encryption option is checked and the (negotiate using data SSL/TLS cipher list) item is selected, the encrypt option is set to yes, which instructs UDM Manager to negotiate the encryption method with the Server, using their respective data SSL/TLS cipher lists.

Enable Network Fault Tolerance
When this option is selected, network fault tolerance will be requested for each instance of a Universal Data Mover Manager that is run from this location. This means that if the remote Universal Data Mover Server supports network fault tolerance, all lost network connections will be detected and recovered.

Network Delay
The number of seconds that can be attributed to network latency for any transmission of data among Universal components. This value is automatically added to any network operation where a time out condition is possible and needs to be handled.
 
Retry Count
The maximum number of reconnects that will be attempted if a network connection is lost and network fault tolerance is enabled.
 
Retry Interval
The number of seconds between each reconnect attempt.

Frame interval
The frame interval is the number of transmission blocks between synchronization points.
 
Acknowledge data transfer after every
Specifies the size of the Network Fault Tolerant (NFT) acknowledgement window. The NFT protocol requires an acknowledgement (ACK) message from the receiver to acknowledge the receipt of the data. The ACK window specifies the amount of data sent before an ACK is required. The larger the window the more data that is sent before waiting for an ACK message. A large ACK window can improve transfer performance over large bandwidth, high latency connections.
 
The format of the value is nnnnb, where 'nnnn' is a numeric value and 'b' is one of the following optional unit specifiers:

<ul>
<li> b - bytes (the default, used if no unit is specified)
<li> k - kilobytes, where 1 kb = 1024 bytes
<li> m - megabytes, where 1 mb = 1048576 bytes
</ul>

The maximum value permitted is 500M. A value of 0 (zero) causes every message that contains data for a file transfer to be acknowledged (default NFT behavior).

Allows the UDM manager to set the TCP receive buffer for a UDM server larger than the default maximum of 64k bytes. Setting this value enables RFC 1323 window scaling support, which can increase TCP buffer sizes over a fast, high-bandwidth network to almost 1 gigabyte (1,073,725,400 bytes).
 
When this option is not selected a UDM uses a default of 0 bytes, which disables RFC 1323 window scaling support. Note that even when a value is specified for this option, the TCP/IP stack ultimately decides the size of the transfer buffer. Specifies the TCP receive buffer size for the TCP socket connections from the UDM manager to the UDM server. The option has no effect for UDM three party transfers. The UDM server and Universal Broker configuration affects UDM three party transfers.
 
Refer to the Universal Broker tcp_recv_buffer option to set the TCP receive buffer for the other end of the socket connection.
 
The socket TCP receive buffer is used by TCP to determine the size of the TCP window it advertises to the sending TCP. If both TCP implemenations support window scaling (as defined in RFC 1323), buffer sizes greater then 65535 will be used for the TCP window size. Note that both the sending and receiving TCP implemenations must support window scaling for it to be used in the TCP connection.
 
Adjusting the TCP receive buffer size may improve bulk data transfer performance for certain types of transmission links when transfering data from the UDM server to the UDM manager. The format of the value is nnnnb, where 'nnnn' is a numeric value and 'b' is one of the following optional unit specifiers:

<ul>
<li> b - bytes (the default, used if no unit is specified)
<li> k - kilobytes, where 1 kb = 1024 bytes
<li> m - megabytes, where 1 mb = 1048576 bytes
<li> g - gigabytes, where 1 gb = 1073741824 bytes
</ul>

Note that the maximum allowable value for this option is 1073725440 bytes, which can be requested using a value of 1g.

Specifies the TCP send buffer size for the TCP socket connections from the UDM manager to the UDM server. The option has no effect for UDM three party transfers. The UDM server and Universal Broker configuration affects UDM three party transfers.
 
Refer to the Universal Broker tcp_send_buffer option to set the TCP send buffer for the other end of the socket connection.
 
Adjusting the TCP send buffer size may improve bulk data transfer performance for certain types of transmission links when transfering data from the UDM manager to UDM server.
 
The format of the value is nnnnb, where 'nnnn' is a numeric value and 'b' is one of the following optional unit specifiers:

<ul>
<li> b - bytes (the default, used if no unit is specified)
<li> k - kilobytes, where 1 kb = 1024 bytes
<li> m - megabytes, where 1 mb = 1048576 bytes
<li> g - gigabytes, where 1 gb = 1073741824 bytes
</ul>

Note that the maximum allowable value for this option is 1073725440 bytes, which can be requested using a value of 1g.

Universal Data Mover uses the SSL/TLS protocol for internal communication between application components. A control session is established within the application that provides the connections necessary for this communication to take place. The SSL/TLS cipher suites available for communication across the control session are listed here.
 
The selected cipher suites will be forwarded to the Universal Data Mover Server. The Server will compare this list to its own list of ciphers it is capable of accepting. The result of the comparison will be an agreed-upon cipher used for communication over the control session. If you are unsure which ciphers will be accepted by the Server, it is best to leave them all selected. Use the up/down arrows on the right to sort the list and establish a priority for the selected ciphers. The first one in the list that is accepted by the Server will be the one used.
 
The following cipher suites are available:

<ul>
<li> RC4-SHA -- 128-bit RC4 encryption, SHA-1 message digest 
<li> RC4-MD5 -- 128-bit RC4 encryption, MD5 message digest 
<li> AES256-SHA -- 256-bit AES encryption, SHA-1 message digest 
<li> AES128-SHA -- 128-bit AES encryption, SHA-1 message digest 
<li> DES-CBC3-SHA -- 128-bit Triple-DES encryption, SHA-1 message digest 
<li> DES-CBC-SHA -- 128-bit DES encryption, SHA-1 message digest
<li> NULL-SHA -- No encryption, SHA-1 message digest 
<li> NULL-MD5 -- No encryption, MD5 message digest 
<li> NULL-NULL -- Disables the SSL protocol 
</ul>

To disable SSL/TLS encryption and message authentication for messages transmitted across the control session, select the NULL-NULL entry. Use of this cipher requires that the remote UDM Server's encrypt_control_session option be set to no. Otherwise, the UDM Server will issue a protocol error when the Manager tries to establish the control session with it.

Universal Data Mover uses the SSL/TLS protocol for transmission of data across the network. A data session is established within the application that provides the connections necessary for the transfer of data to take place. The SSL/TLS cipher suites available for communication across the data session are listed here.
 
The selected cipher suites will be forwarded to the Universal Data Mover Server. The Server will compare this list to its own list of ciphers it is capable of accepting. The result of the comparison will be an agreed-upon cipher used for communication over the data session. If you are unsure which ciphers will be accepted by the Server, it is best to leave them all selected. Use the up/down arrows on the right to sort the list and establish a priority for the selected ciphers. The first one in the list that is accepted by the Server will be the one used.

<ul>
<li> RC4-SHA -- 128-bit RC4 encryption, SHA-1 message digest 
<li> RC4-MD5 -- 128-bit RC4 encryption, MD5 message digest 
<li> AES256-SHA -- 256-bit AES encryption, SHA-1 message digest 
<li> AES128-SHA -- 128-bit AES encryption, SHA-1 message digest 
<li> DES-CBC3-SHA -- 128-bit Triple-DES encryption, SHA-1 message digest 
<li> DES-CBC-SHA -- 128-bit DES encryption, SHA-1 message digest
<li> NULL-SHA -- No encryption, SHA-1 message digest 
<li> NULL-MD5 -- No encryption, MD5 message digest 
<li> NULL-NULL -- Disables the SSL/TLS protocol 
</ul>

Generate activity monitoring events
When this option is selected, the Universal Data Mover Manager will generate events that monitor product activity. This option is selected by default.
 
Persistent event list
Specifies which events are to be generated and processed as persistent events. A persistent event is saved in a Universal Enterprise Controller (UEC) event database for long-term storage.
 
Enter a list and/or range of numeric event types, separated by a comma. To exclude an event or range of events, precede the entry with an upper- or lower-case 'X'. Use an asterisk * to specify all event types.
 
For example:

<ul>
<li>x*<br>
Do not generate any events (this is the default)
<li>*<br>
Generate all event types 
<li>100<br>
Generate all event types except 100 
<li>100,200-205<br>
Generate event type 100 and 200 through 205
<li>100,200-205,x202<br>
Generate event types 100 and 200 thru 205, excluding event type 202 
</ul>

Entries are processed from left to right, and the list is order dependent. For example, an entry of x*,100 prevents generation of all event types except 100, while an entry of 100,x* prevents generation of all event types (the right-most entry takes precedence).