Page Comparison

Specifies the TCP receive buffer size for TCP socket connections established from the UDM primary server to the UDM secondary server. The option has no effect for UDM two party transfers. The UDM manager and Universal Broker configuration affects UDM two 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 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 secondary server to the UDM primary server. The format of the value is nnnnb, where 'nnnn' is a numeric value and 'b' is one of the following optional unit specifiers:

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

<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 TCP socket connections established from the UDM primary server to the UDM secondary server. The option has no effect for UDM two party transfers. The UDM manager and Universal Broker configuration affects UDM two 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:

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

<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 Server 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 Server will compare the Manager's cipher list to its own list of ciphers. The result of the comparison will be an agreed-upon cipher used for communication over the data session. 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:
The Server will compare the Manager's cipher list to its own list of ciphers. The result of the comparison will be an agreed-upon cipher used for communication over the data session. 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/TLS protocol 
</ul>

Generate activity monitoring events
When this option is selected, the Universal Data Mover Serve 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:activity monitoring events
When this option is selected, the Universal Data Mover Serve 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).