# Client Configuration Parameters

The following table lists parameters used to configure TIBCO MFT Platform Server as an initiator.

Parameter | Description
--- | ---
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, the initiator rejects the transfer and displays an error message.
ConnectAdapterIP | Defines the IP address through which the initiator sends or receives data for outgoing 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, it is possible to bind the connection to a particular one. It guarantees that all the transfers only go through this particular IP address.
ConnectAdapterIPv6 | Defines the IPv6 address through which the initiator sends or receives data for outgoing connections . The default value for this parameter is ALL which means connections can bind to any IPv6 address. If a machine has more than one IPv6 address, it is possible to bind the connection to a particular one. It guarantees that all the transfers go only through this particular IPv6 address.
TraceLevelClient | Defines the level of tracing that occurs. The valid values are: N|No: no tracing takes place. This is the default value. L|Low: provides minimal information about the transfer, including local and remote transaction numbers, file names, the number of bytes transferred, fail or success status indicator, general message string, and the start and finish times of the transfer. M|Medium: includes all internal state messages. H|High : includes all networking data in addition to the information provided by the medium level trace. 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 TraceLevelClient is used, the TraceSizeClient must be defined.
TracePathClient | Defines the name of the path that holds the client trace file. A unique trace file is created for each file transfer. A 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 daemon, CyberResp. The file name is servername 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.
TraceSizeClient | Defines the size limit of the trace file in kilobytes. The file name is the trace file name (local transaction number and PID) with a t1 extension. When the specified size limit is 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 TraceSizeClient is used, TraceLevelClient or SSLTraceLevel in the client part must be defined.
Umask_User | Defines whether to apply the user's umask to the incoming files. Note: This parameter only applies to the initiator that is doing a receive transfer. If Umask_User is set to N, the user's umask is ignored on incoming files. If Umask_User is set to Y, the user's umask is applied to incoming files..
Timeout | Defines the amount of time in minutes that a connection stays open when waiting for a response from the remote side. The default value is 120 minutes. Once the timeout value is reached, the connection ends.
RunPPAEndDirTx | Defines whether to have the post processing action run after each file in a directory or a distribution list is transferred. The valid values are No or Yes. The default value is No. When this parameter is set to Yes , the following rules apply: StopOnFailure is automatically set to Yes. Transfers stop on the first failed transfer. Failure PPA runs on the first failed transfer. Successful PPA runs only on the last transfer (assuming it is successful). Note: Since this is a global parameter, it affects all transfers.
ACCHost | Defines the IP address or host name of the Accelerator server.
ACCPort | Defines the port number on which the Accelerator server listens for transfers using the Accelerator technology. The default number is 9099.
ClassOfService | Defines the buffer size for the client 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.
StopOnFailure | Defines the default value for StopOnFailure when this parameter is not specified by the cfsend or crfrecv commands. StopOnFailure defines whether a directory transfer or distribution list transfer should stop on the first failure (Y) or continue if a transfer fails.
DirTransfer0Files | Defines the status of the directory transfer when zero files are in the directory. The valid values are: F: When no files are transferred on a directory transfer, the transfer is a failed transfer. S: When no files are transferred on a directory transfer, the transfer is a successful transfer. The default value is F.

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