Node Parameters
If you do not specify the required parameters, and the prompt:YES parameter is specified in the cfnode command line, you are prompted for all information required to successfully execute the cfnode utility.
See the following table for the required node parameters.
See the following table for the optional node parameters.
Optional Parameter (Shortcut) | Description |
---|---|
Action (a) | The action parameter is used to specify the action to be taken. The valid values are : Delete, List, and Add.
Example: action:delete n:NYNode |
netmask (net) | This is the netMask for the remote I Pv4 address.
Examples: netMask:255.255.255.0 net:255.255.255.128 |
netMask6 (net6) | This is the netMask for the remote I Pv6 address . This is a number between 8 and 128 and a multiple of 8. |
ssl | The ssl parameter is used to specify whether SSL/TLS is used for TCP/IP communications.
Example: ssl:Y |
compress (c) | The compress parameter is used to specify the default compression type for all transfers with this node. The valid values are as follows:
Examples: compress:LZ c:NEVER |
encrypt (e) | The encrypt parameter is used to specify the default encryption type to use for all transfers with this node. The valid values are as follows:
Examples: encrypt:DES e:NEVER |
security (sl) | This parameter determine s whether the node is HIPAA or FIPS-140 compliant. If set, only HIPAA or FIPS-140 compliant encryption types are listed. See
General Tab, System Configurations: Security Policy for more information.
Example: security:HIPAA |
lct | The name of the Local Conversion Table (also referred to as the Local Translation File), which is used to translate the data on the local side.
Example: lct:convert.txt |
rct | The name of the Remote Conversion Table (also referred to as the Remote Translation File), which is used to translate the data on the remote side.
Example: rct:convert.txt |
responder (r) | This parameter defines whether a responder profile is used for this node. The valid values are Yes, No, and Dual. The value D (Dual) means that the substitution of a real user ID occurs only if the responder profile exists and a match is found. If no match is found, the platform server attempts to log in with the remote user ID and password, rather than generate an error message that responder profile does not exist or the information does not match. On the other hand, a value of Yes means that the platform server does not try to log in with the remote user ID and password, and a value of No means that the platform server does not check the responder profiles.
Example: responder:Yes r:Y |
description (d) | The description parameter is used to specify a text description of the node definition. The description can be up to 256 characters and can contain spaces. If the description contains spaces, it must be enclosed in double quotation marks. The cfnode command does not require the description parameter defined if the prompt:NO parameter is supplied.
Examples: description:"This is a sample description" d:"This is a sample description" |
commandsupport (ccc) | It defines the actions that Command Center can perform on this node. The valid values are as follows:
Examples: ccc:PING commandsupport:TRANSFER |
winners (win) | The Winners parameter is used to specify the maximum number of initiator transfers for the node. The valid values are from 1 to 50. If the Winners parameter is not defined in the node definition, the default value 5 is used.
This parameter only works for transfers submitted to the platform server. It does not work for command line transfers. Example: Winners:2 |
prompt | The prompt parameter is used to put cfnode into an interactive mode. If prompt:YES is supplied, cfnode prompts you for all information required to create a node. You will also be prompted whether you want to create cfnode.cfg if it cannot be found. Prompt is turned on by default. If you do not want to be prompted, use prompt:NO. |
-? | The -? parameter is used to display the online help for cfnode. |
usage: cfnode [required-parameters] [optional-parameters] [required-parameters]: n: or node: - Name of Node s: or systemType: - Type of system (ie. Windows, UNIX, SUN, etc.) h: or hostName: - Network address of remote node. This may be host name or a dotted IP address. (This parameter is only required for TCP/IP transfers.) p: or port: - Port number that remote node is listening on. (This parameter is only required for TCP/IP transfers.) [optional-parameters]: a: or action: - Following values are allowed: : Delete (Nodename is required) : List (Nodename is optional) : Add (Default value) net: or netMask: - NetMask for remote IpAddress. Valid value: netmask. net6: or netMask6: - NetMask for remote IpV6 Address. Valid value: A number between 8 and 128 and a multiple of 8. ssl: - Either Yes or No depending on whether remote node requires an ssl connection. c: or compress: - Type of default compression to use during transfers. Valid compression types: (LZ | RLE | NO | NEVER | ZLIB1 - ZLIB9) e: or encrypt: - Type of default encryption to use during transfers. Valid encryption types: (DES | 3DES | BF | BFL | RIJN(AES) | NO | NEVER) sl: or security: - Security Compliance level to use during transfers. Valid security types: (Default | None | HIPAA) lct: - Local translation file. Valid value: file path. rct: - Remote translation file. Valid value: file path. r: or responder: - Either Yes, No or Dual depending on whether or not to use ResponderProfiles with this node. If responder profiles are to be allowed as well as regular logins, enter Dual. d: or description: - Text description of the following node definition. Note: the definition must be encapsulated in " ". ccc: or commandsupport: - The actions this node will allow MFT Command Center to perform: (ALL, NONE, NODE, PROFILE, AUDIT, PING, TRANSFER) win: or winners: - Max Initiator Transfers per node. Default value is 5 prompt: - Prompts the user for corrections when errors are found. Valid values: (YES | NO). Default is YES. -? - Online help.