Creating Nodes

You can use the cfnode utility to add, update, and delete node definitions.

Note: Only the superuser (root) or members of the cfadmin group can create nodes.

Procedure

  1. Optional: On the command line, navigate to the $CFROOT/bin directory.
  2. Enter cfnode prompt:Yes.
    You are prompted for both the required and optional parameters to define a remote system (node).
    Note: Without the prompt:YES option (or with the prompt:NO option), you can define values for the required parameters and only the optional parameters you want to use. See the following sample command: 
    cfnode n:dataserverA s:Windows 
net:255.255.255.0 h:192.168.0.43 p:46464  
ssl:Y c:RLE e:NEVER security:Default v:Y r:D 
d:”This is a sample node definition” 
ccc:TRANSFER prompt:NO
  3. On the prompt, set the values for both the required and optional parameters.
    Note: If the node name you define already exists, you are prompted as to whether you want to edit the defined node.
    See the following sample of creating a Windows node with the cfnode prompt:YES command. 
    > cfnode prompt:YES
Enter a valid node name: dataServerB
Enter a System Type for Node[dataServerB]:
1: HPUX
2: SUNOS/SOLARIS
3: AIX
4: LINUX
5: Windows
6: IBMi
7: z/OS
8: Command_Center
9: Other
: 5
Enter a valid IP address for Node[dataServerB]: 192.168.0.44
Would you like to specify netmask for remote IpAddress:
1: Yes
2: No
: 2
Enter the port for which Node[dataServerB] is configured to use: 46464
Enter the Security Compliance level for file transfers:
1: Default ( use Security Policy setting from config.txt )
2: None
3: HIPAA
: 1
Should TLS/SSL be used:
1: NO
2: YES (TLS/SSL compatibility mode)
3: TLS TUNNEL
: 1
What should be the default encryption used:
1: DES
2: 3DES
3: BF
4: BFL
5: RIJN(AES)
6: AES128
7: No default encryption
8: Never use encryption
: 3
What should be the default compression used:
1: LZ
2: RLE
3: ZLIB
4: No default compression
5: Never use compression
: 2
Would you like to specify local translation file:
1: Yes
2: No
3: NONE (Caution! If uncertain, refer to User Guide.)
: 1
Please enter local translation file:
: MyComtblg.dat
Would you like to specify remote translation file:
1: Yes
2: No
: 2
Accept Verified Users from this node?
1: Yes
2: No
3: Do not define
: 1
Use Responder Profiles for this node?
1: Yes 
2: No 
3: Dual 
4: Do not define 
: 3 
Would you like to add a description: 
1: Yes 
2: No 
: 2 
Enter the MFT Command Center parameters this node will support: 
1: All 
2: None 
3: Audit 
4: Node 
5: Ping 
6: Profile 
7: Transfer 
: 1 
Do CRC checking for this node? 
1: Yes 
2: No 
3: Default 
: 2
A Node definition was created for: 
[new_1] 
SystemType = SUNOS/SOLARIS
Protocol =  tcpip
HostName = 10.102.52.14
Server = 46464
TLS = N
Compression = NO
Encryption = NO
Security Policy = None
AcceptVerifiedUser = N
ResponderProfile = D
CommandSupport = ALL
CRC = No 
[root@rkundu-xw6200 -] #

    Node definitions are stored in the cfnode.cfg file located in the $CFROOT/config directory. After a node definition is created, you can specify the name of the node you want to use for the transfer. In addition to working with a remote TIBCO MFT Platform Server, you can also conduct transfers for this server using TIBCO MFT Command Center. For more information, see TIBCO MFT Command Center documentation.