Overview
This page provides information on the Universal Data Mover (UDM) Server, specific to the Windows operating system.
Component Definition
All Universal Agent components managed by Universal Broker have a component definition. The component definition is a text file of options containing component-specific information required by Universal Broker. (For details on how Universal Broker manages components, see the Universal Broker 7.6.x Reference Guide.)
The syntax of a component definition file is the same as a configuration file.
Although component definition files can be edited with any text editor (for example, Notepad), the Universal Configuration Manager application is the recommended way to edit component definitions for Windows.
The component definitions for all Universal Agent components are identified in the Component Definitions property page of the Universal Broker.
The UDM Server component definition is located in the component definition directory of the Universal Broker.
The following table identifies all of the options that comprise the UDM for Windows component definition. Each Option Name is a link to detailed information about that component definition option.
Option Name | Description |
---|---|
Specification for whether or not UDM Server starts automatically when Universal Broker is started. | |
Name by which the clients know the UDM Server. | |
Full path name of the UDM Server configuration file. | |
Maximum number of UDM Servers that can run simultaneously. | |
Full path name of the UDM Server program. | |
Full path name of the UDM Server working directory. |
Configuration
Universal Data Mover Server configuration consists of defining runtime and default values. This section describes the UDM Server configuration options.
Configuration File
The configuration file provides a method of specifying configuration values that will not change with each command invocation.
The Universal Data Mover Server configuration file name (and directory) is specified in the Universal Data Mover Server component definition (see Universal Data Mover Component Definition Options). The default configuration file name is udms.conf.
Although configuration files can be edited manually with any text editor (for example, Notepad), the Universal Configuration Manager application is the recommended way to set configuration options in the configuration file.
The Universal Configuration Manager provides a graphical interface and context-sensitive help, and helps protect the integrity of the configuration file by validating all changes to configuration option values.
Configuration Options
The following table identifies all Universal Data Mover Server for Windows configuration options. Each Option Name is a link to detailed information about that configuration option.
Option | Description |
---|---|
Specification for whether or not product activity monitoring events are generated. | |
Character code page used to translate text data. | |
Specification for whether or not data is compressed on all standard I/O files. | |
SSL/TLS cipher suites to use for data session between UDM primary and secondary servers. | |
Events to be generated as persistent events. | |
Number of UDM transfer blocks transferred before a frame-sync message is sent with network fault tolerance turned on. | |
Directory on which UDM Server is installed. | |
Specification for how users are logged onto the system. | |
Level of messages that UDM will write to the Universal message Catalog (UMC) file. | |
Minimum SSL/TLS protocol level that will be negotiated and used for communications channels. | |
List of message IDs representing Universal messages to be suppressed. | |
Expected network latency (in seconds). | |
Directory where the UDM Manager message catalog and code page tables are located. | |
Host or IP address that UDM binds to when initiating outgoing connections to another UDM server. | |
Number of attempts that the UDM Manager will make to re-establish a transfer session when a network fault occurs. | |
Number of seconds that UDM will wait between each successive attempt to re-establish a transfer session when a network fault occurs. | |
Size (in bytes) of the application's incoming buffer for UDM. | |
Size (in bytes) of the application's outgoing buffer for UDM. | |
Specification for whether or not to use TCP packet coalescing. | |
TCP/IP buffer size of a secondary UDM Server that receives a file from a primary Server in a three-party transfer. | |
Directory that UDM Server uses for temporary files. | |
Directory name that UDM Server uses for its Trace files. | |
Maximum number of lines to write to the trace file. | |
Size of a wrap-around trace table maintained in memory. | |
User security option. | |
User security option. |
Universal Access Control List
UDM Server uses the Universal Access Control List (UACL) file as an extra layer of security. The UACL file contains UDM Server entries that contain Access Control List (ACL) rules that permit or deny access to the UDM Server.
UACL Entries
The syntax of a UACL entry file is the same as the UDM configuration file.
The following table identifies all Universal Data Mover Server for Windows UACL entries. Each UACL Entry Name is a link to detailed information about that UACL entry.
UACL Entry Name | Description |
---|---|
Allows or denies access to Universal Data Mover Server services | |
Allows or denies access based on the host name and/or user of the Manager trying to initiate a UDM session |