# Server Configuration Parameters

The following table lists parameters used to configure TIBCO MFT Platform Server as a responder.

Parameter Name | Description
--- | ---
ListenAdapterIP | Defines the IP address at which the responder listens for incoming connections. The default value for this parameter is All, which means connections can bind to any IP address. If a machine has more than one IP address, you can bind the connection to a particular one. It guarantees that all the transfers go only through this particular IP address.
ListenAdapterIPv6 | Defines the IPv6 address at which the responder listens for incoming connections. The default value for this parameter is All, which means connections can bind to any IP address. If a machine has more than one IPv6 address, you can bind the connection to a particular one. It guarantees that all the transfers go only through this particular IPv6 address.
Port | Defines the IP port on which TIBCO MFT Platform Server listens for incoming requests. The valid values are from 1024 to 65535, because lower ports are usually reserved for standard applications. The default value is 46464.
PortIPv6 | Defines the IPv6 port on which TIBCO MFT Platform Server listens for incoming requests. The valid values are N or a number ranging from 1024 to 65535, because lower ports are usually reserved for standard applications.
TraceLevel | Defines the level of tracing. The valid values are N, Low | L, Medium | M, or High | H. The default value is N. Usually tracing has only to be turned on at the request of TIBCO Support for troubleshooting purpose. Note: This parameter cannot be used within a transfer template. When the TraceLevel is used, the TraceSizeServer must be defined.
TracePath | Defines the name of the path that holds the responder trace file. A unique trace file is created for each file transfer. The file name contains the local transaction number and Process ID (PID). A global server trace file is created each time the cfstart command is used to start the TIBCO MFT Platform Server daemon, CyberResp. The file name is server name with the current time as an extension. This file contains the PIDs of all child processes that are started by TIBCO MFT Platform Server. Note: This parameter cannot be used within a transfer template.
TraceSizeServer | Defines the size limit of the trace file in kilobytes. The valid values are N or a number of kilobytes. The default value is N. The file name is the trace file name (local transaction number and PID) with a t1 extension. When the specified size limit has been reached, a second file with a t2 extension is created. When the second file is full, all data contained in the t1 file is deleted and it begins again from size 0. This process then repeats on the t2 file. This trace file swapping continues for the duration of the file transfer. Note: This parameter cannot be used within a transfer template. When TraceSizeServer is used, TraceLevel or SSLTraceLevel in the server part must be defined.
ConvTbl | Defines the path to the standard conversion table. It provides ASCII to EBCDIC conversion for any transactions to or from z/OS and AS/400 platforms. The default name of this file is Comtblg.dat which is located in the $CFROOT directory. For more information, see Conversion Tables.
ExitPrgm | Defines the path to the Exit program on the local machine. Using the Exit program, you can do customized post processing. For more information, see User Exits.
RequiredNodeDefinition | Defines whether a node definition is required for TIBCO MFT Platform Server to communicate with a remote system. Value Y means that the remote IP address requires a defined node. If the remote address is not defined in a node (in either the cfnode.cfg or cfprofile.cfg file), the responder rejects the initiator and sends back an error message.
AcceptVerifiedUser | Defines whether a remote verified user can log on to TIBCO MFT Platform Server using the remote user ID without a password. TIBCO MFT Platform Server recognizes the client as verified if the client sends an internal password inside the password field. To log on using only a user ID without a password, the initiator platform must provide the following for the remote user ID (this is case sensitive): Userid: *VER Password: (Password field must be left blank.) The initiator user ID can also be used as the responder user ID. This means that the same user ID has to exist on the responder as well as the initiator platforms.
ResponderProfile | Defines a local user name and password to substitute the incoming user name and password. By using responder profiles, a remote TIBCO MFT Platform Server does not have to get an actual user name and password from your local machine to initiate a transfer. Note: ResponderProfile checking routine is always done before AcceptVerifiedUser checking. So if both are set up, AcceptVerifiedUser takes precedence. ResponderProfile value D (Dual) means that the substitution of a real user ID occurs only if the cfrprofile file exists and a match is found. If there is no match found, then TIBCO MFT Platform Server tries to log on using the remote user ID and password, and no error message is generated.
AllowRoot | Defines whether the root account is considered as a valid user ID for transfers. If the responder profile defines the root account as the local user ID: When AllowRoot is set to password or all, the root account can be used as a valid user ID. When AllowRoot is set to no, the root account cannot be used as a valid user ID.
Umask_Default | Defines the UNIX umask applied to the newly created files on the server (responder). The valid values are N or a three digit number ranging from 000 to 777. You can use this parameter to modify the permissions for newly created files on the responder side, just as the UNIX umask sets the permissions on newly created files. If Umask_Default is set to N, then the file permission can be set according to the root user mask. On the initiator, the desired permission is modified according to the umask of the user that runs the cfsend or cfrecv command. Note: There is no command line or template option for Umask. This parameter is only contained in the config.txt file.
Uperm_Default | Defines the file permissions for newly created files on the server (responder). The valid values are N or a three digit number ranging from 000 to 777. The Uperm_Default parameter is used when a user sends a new file to the UNIX server and has not provided the uperm parameter. (This is not possible on a UNIX initiator, as the uperm parameter is set by default to the file permissions of the sending file). If the Uperm_Default is set to N, the file permissions for the newly created file are set according to the Umask_Default parameter. Note: For transfers between UNIX systems, if a file is not executable on the initiator, it cannot be changed to executable on the responder. This is a property of UNIX, not of TIBCO MFT Platform Server.
TimeOut | Defines the amount of time in minutes that a connection stays open when waiting for a response from the remote side. Note: Once the timeout value is reached, the connection ends.
RunCyberRespAsNonRoot | Defines whether you can run TIBCO MFT Platform Server as a non-root user. Note: When running CyberResp with a non-root user ID, you must use responder profiles. Therefore, when RunCyberRespAsNonRoot is set to Yes, ResponderProfile must be set to Yes too.
ClassOfService | Defines the buffer size for the server in a transfer. The valid values are the different levels of SBUFSIZE and RBUFSIZE specified in the configuration file named cfcos.cfg The transfer performance can be improved as server and client using different level of classes.
PamAuth | Defines the PAM service file name or the PAM service entry name. The valid values are N or the PAM service name. The PAM service defines the PAM parameters used for authentication. When this parameter is set to N, password or shadow password authentication is performed.

Copyright © 2022. TIBCO Software Inc. All Rights Reserved.