Syntax

open [primary={*|local|host-name} [port=broker-port] [user=username [pwd=password]] [codepage=codepage] [{file=filename | xfile=filename [key=key]}] [verserial=serial number|no] [verhost=yes|no|host name]
secondary=host-name [port=broker-port] [user=username [pwd=password]] [codepage=codepage] [{file=filename | [xfile=filename [key=key]}] [verserial=serial number|no] [verhost=yes|no]
[encrypt=yes|no|cipher] [compress=compression-method] [nft=yes|no] [comment=text] [tt=direct|deferred] [minsslprotocol=tls1_0|tls1_2]

Description

The open command opens a UDM transfer session: two-party or three-party.
 

Each transfer session has a primary server and a secondary server. These servers are given logical names (primary and secondary) by the user.

For a two-party transfer session, a UDM Manager acts as the primary server, and its logical name (primary) is set to:

• * or local as the host name, if the logical name of the secondary server is specified.

Optionally, an open command can specify only a secondary server logical name (secondary), which implies a two-party transfer. In this case, the primary server (the UDM Manager) automatically is assigned local as the logical name.

For a three-party transfer session, a UDM Server is the primary server, and its logical name (primary) must be set to host name as the host name.

Each server parameter (primary and secondary) can be followed by one or more of the following parameters that further define the transfer set-up: port, user, pwd, codepage, file or xfile, key, verserial, and verhost. Each of these parameters applies to the server parameter (primary or secondary) that it immediately follows.

• port specifies the port that the broker is accepting requests on to start a UDM server.
• user specifies the user (local to the host on which the server will be running) under which the transfer operation is being carried out
• pwd is the password for the user.

codepage specifies the codepage that will be used for text translation of transferred data. In addition to codepage (.utt) files supplied by the Universal Agent install, UDM supports codepage values of UTF-8, UTF-16, UTF-16BE (except on AIX), and UTF-16LE.

When specified as the source codepage of a file transfer, the UTF-16 encodings describe the type of encoding - little endian or big endian - the conversion routines can expect to encounter in the input file. When a codepage of UTF-16 is specified the conversion routines will rely on the input file's byte order mark (BOM) or - if no BOM is present - the default encoding of the system on which the input file resides. When a codepage of UTF-16BE or UTF-16LE is specified, the conversion routines expect the input file to be encoded as big endian or little endian, respectively, regardless of what the file's actual encoding is.

When specified as the target codepage of a file transfer, the UTF-16 encodings specify the encoding - little endian or big endian - the output file receives. When a codepage of UTF-16 is specified, the output file receives the default encoding of the system upon which it is written. When a codepage of UTF-16BE or UTF-16LE is specified, the output file is encoded as big endian or little endian, respectively, regardless of the system's native encoding.

• file or xfile parameter specifies a file (plain text or Universal Encrypted text, respectively) that contain *port*, *user*, *pwd*, and/or *codepage* in the format of a UDM command file (see [#file / xfile Parameters Format]). If file or xfileis specified, its values apply to the server (primary or secondary) preceding it in the command. These file or xfilevalues override any values specified by the port, user, pwd, and /or codepage parameters following that server.
• key specifies the encryption key used to decrypt the encrypted file specified by xfile.
• verserial specifies either:
  • <serial number>
    • For a Two-Party Transfer Session: The secondary verserial <serial number> is verified by the UDM Manager (the primary server) against the serial number contained in the secondary UDM Server's Universal Broker X.509 certificate.
    • For a Three-Party Transfer Session: The primary verserial <serial number> is verified by the UDM Manager against the serial number contained in the primary UDM Server's Universal Broker X.509 certificate. The secondary verserial <serial number> is verified by the primary UDM Server against the serial number contained in the secondary UDM Server's Universal Broker X.509 certificate.
  • no
    • For a Two-Party Transfer Session: UDM Manager (the primary server) will not verify the serial number of the UDM Server (the secondary server).
    • For a Three-Party Transfer Session: If the primary verserial is no, the UDM Manager will not verify the serial number of the primary UDM Server. If the secondary verserial is no, the primary UDM Server will not verify the serial number of the secondary UDM Server.
• verhost specifies either:
  • yes
    • For a Two-Party Transfer Session: The secondary verhost <host name> is verified by the UDM Manager (the primary server) against the host name contained in the secondary UDM Server's Universal Broker X.509 certificate.
    • For a Three-Party Transfer Session: The primary verhost <host name> is verified by the UDM Manager against the host names contained in the primary UDM Server's Universal Broker X.509 certificate. The secondary verhost <host name> is verified by the primary UDM Server against the host names contained in the secondary UDM Server's Universal Broker X.509 certificate.
  • no
    
    • For a Two-Party Transfer Session: UDM Manager (the primary server) will not verify the host name of the UDM Server (the secondary server).
    • For a Three-Party Transfer Session: If the primary verhost is no, the UDM Manager will not verify the host name of the primary UDM Server. If the secondary verhost is no, the primary UDM Server will not verify the host name of the secondary UDM Server.
  • <host name>
    • For a Two-Party Transfer Session: The secondary verhost <host name> is verified by the UDM Manager (the primary server) against the host names contained in the secondary UDM Server's Universal Broker X.509 certificate.
    • For a Three-Party Transfer Session: The primary verhost <host name> is verified by the UDM Manager against the host names contained in the primary UDM Server's Universal Broker X.509 certificate. The secondary verhost cannot use <host name>.

The encrypt parameter specifies either:

• yes
  An agreed-upon cipher will be negotiated based on the components data_ssl_cipher_list configuration value.
• no
  NULL-MD5 is used as the encryption method.
• cipher
  Specific cipher to use as encryption method: AES256-GCM-SHA384,AES256-SHA,AES128-GCM-SHA256,AES128-SHA,RC4-SHA,RC4-MD5,DES-CBC3-SHA,NULL-SHA,NULL-SHA256,NULL-MD5. Specifying NULL-NULL as the cipher completely disables SSL/TLS when NULL-NULL also is specified in the UDM Server Data Cipher Lists associated with a transfer.

The compress parameter can have either of the following values:

• yes
  Compression option in the UDM Manager's configuration file is used.
• no
  No compression is required when transferring data. However, compression will be used if the UDM Server DATA_COMPRESSION configuration option is set to yes.
• force
  No compression is used when transferring data, even if the UDM Server DATA_COMPRESSION option is set to yes.
• zlib
  Forces the transfer servers to use ZLIB compression when transferring files.
• hasp
  Forces the transfer servers to use HASP compression.

If compress is not specified, a default value of no is used.
 

The nft parameter specifies whether or not the UDM sessions will be network fault tolerant.
 

The comment parameter specifies a comment for a single session (or overrides a comment specified by the COMMENT option.)

For example: open s