| Accept Verified User
|
Accepts or rejects verified users for incoming MFT transfer requests for this node. Valid values are:
Y/N
|
| Command Center Support
|
The Command Center Support parameters are explained below. To turn on a parameter, enter a
Y next to the parameter.
- All - Allows the
TIBCO MFT Platform Server for IBM i to accept all MFT Command Center requests. All of the functions within node, profile (User, Responder), ping, transfer, and audit are allowed.
- None - Allows the
TIBCO MFT Platform Server for IBM i to accept no Command Center requests. This is the default if the parameter is not defined.
- Audit - Allows the
TIBCO MFT Platform Server for IBM i to accept Command Center requests to view and retrieve information in the
TIBCO MFT Platform Server for IBM i audit log. Command Center Collector and Audit Polling functions require this option to be set on the MFT Platform Server for IBM i node definition.
- Node - Allows the
TIBCO MFT Platform Server for IBM i to accept Command Center requests to Add, List, Update and Delete MFT Platform Server for IBM i node entries.
- Ping - Allows remote MFT Platform Servers to check if
TIBCO MFT Platform Server for IBM i is running.
- Profile - Allows the
TIBCO MFT Platform Server for IBM i to accept Command Center requests to add, list, update, or delete
TIBCO MFT Platform Server for IBM i user profile and responder user profile entries.
- Transfer - Allows
TIBCO MFT Platform Server for IBM i to accept Command Center requests to initiate a transfer on this
TIBCO MFT Platform Server for IBM i to send a file to a different MFT Platform Server system.
|
| CRC Check
|
Indicates whether the CRC Check validation method is used for all MFT Platform Server outgoing data transfer request transactions for this particular node. Valid values are:
Y/N
|
| Data Compression
|
Sets the data compression to be used for this transfer. Valid values are:
- 0
- None. No data compression.
- 1 - LZ. LZ provides better compression ratios and compresses a wider variety of different data types than RLE. Choose LZ if you need better compression ratios and can spare CPU cycles.
- 2 - RLE. RLE is more data-dependent than LZ. That is, the compression ratio may vary widely based upon the type of data being compressed. Choose RLE if you network bandwidth is not a critical bottleneck for your network and you need to save CPU cycles.
- 3 - ZLIB. ZLIB data compression method is used.
|
|
Encryption
|
Defines the encryption type to use for all outgoing transfer requests for this particular node. Valid values are:
- 0 - None
- 1 - DES
- 2 - TDES (Triple DES)
- 3 - Blowfish
- 4 - Blowfish Long
- 5 - AES/Rijndael
|
| Maintain by
|
Is automatically updated with the current user when they change, copy, or add a record to the MFT Platform Server Node Configuration file.
|
| Maintain Date
|
Is automatically updated with the current date when a user changes, copies, or adds a record to the MFT Platform Server Node Configuration file.
After entering the appropriate values, press Enter to process the node configuration record.
|
| Remote Link Type
|
Is automatically updated with the remote link type. The Remote Link Type value is
1 for TCPIP.
|
| Remote Node Name
|
Defines a remote system configuration for
TIBCO MFT Platform Server for IBM i. You can enter the remote node name on the selection field either to enter a new record or to update a node configuration record. This name gives the user the ability to associate a name with a remote location instead of just using an IP address.
The remote node entered by the user must be the name of an MFT Platform Server remote system configuration record, which is used by MFT Platform Server to connect to the remote Platform Server. MFT Platform Server only accepts
A-Z,
0-9,
@,
$,
#, and _
(underscore). The node name cannot begin with an underscore.
|
| Remote System Type
|
Defines one of four valid remote MFT Platform Server system types. Valid values are:
- 1 - z/OS
- 2 - Windows
- 3 - UNIX
- 4 - IBM i
|
| Remote TCP/IP Address/Host Name
|
Defines the remote TCP/IP address number or a remote host name for a particular remote system. MFT Platform Server uses this address/host name to locate that remote system for incoming and outgoing transfer request processing. This field also is used when the global required node initiator or responder parameters are set to
YES. The IP address/host name of the incoming and outgoing transfer requests is checked against this field to ensure that the remote system is defined to this MFT Platform Server system.
|
| Remote TCP/IP Port Number
|
Defines a remote TCP/IP port number between
1025 and
65535. This parameter must match the IP port that the remote MFT Platform Server is listening to connect. Default value is
46464.
|
| Responder User Profile
|
Defines whether or not to use a responder profile for the incoming request from this node. Valid values are:
- Y - Checks an existing responder user profile record with the user ID and password sent.
- N - Does not check for a responder user profile record at all.
- D - Dual option means that the substitution of a real user id occurs only if the responder user profile record exists and a match is found. If there is no match found, then MFT Platform Server attempts to log in the remote user with the user ID and password sent with the transfer request.
- Blank - Uses the Global Parameter File Responder User Profile field value.
|
| System Description
|
Defines the description of the MFT node configuration record setting. This field allows a user to attach a comment to a node configuration.
|
| Transport Security Layer
|
Defines the Transport Layer Security TCP/IP Protocol is used for all MFT Platform Server outgoing data transfer request transactions for a particular remote node. Valid values are:
- Y - Transport Layer Security encryption method is used for all MFT Platform Server outgoing data transfer request transactions.
- N - Non-Transport Layer Security encryption method is used for all MFT Platform Server outgoing data transfer request transactions.
- T - Transport Layer Security Tunnel encryption method is used for all Platform Server outgoing data transfer request transactions.
|
| ZLIB Compression Level
|
Defines the ZLIB data compression level from
0 to
9 controlling the level of compression that is used to process all MFT Platform Server outgoing data transfer request transactions for a particular remote node. 0 is no ZLIB compression level. Valid values are:
- 0 - No ZLIB data compression level
- 1 - ZLIB data compression level 1 method
- 2 - ZLIB data compression level 2 method
- 3 - ZLIB data compression level 3 method
- 4 - ZLIB data compression level 4 method
- 5 - ZLIB data compression level 5 method
- 6 - ZLIB data compression level 6 method
- 7 - ZLIB data compression level 7 method
- 8- ZLIB data compression level 8 method
- 9 - ZLIB data compression level 9 method
|
