Log Files

TIBCO MFT Platform Server has comprehensive logging located in the $CFROOT/log directory. You can find records of all transfer requests performed on the server.

The cfinq utility provides two ways of viewing the audit information: the summary view and the detailed view. The summary view only consists of the following columns: Index, Transaction, Status, IP Address and Local File.

Note:

To obtain all transactions in the specified query, you must either use the root account, or a member of the cfbrowse group or cfadmin group as defined in the $CFROOT/config.txt file. Without this access, you can only view your own transactions.

The daily audit log is called Log.txt.yyyymmdd. Each day a new log is generated with the date appended to the end of the file name. You can change the path and log prefix by editing the LogEventFileName parameter in config.txt file. This log file is a standard ASCII text file which contains one record on each line.

The following sample Log.txt shows one transfer request log information:

VersionNumber=8.0. Maint build 4,Priority=N/A,LocalTranNumber=R829800336, RemoteTranNumber=1829800335, TransferStartTime=163525, TransferStartDate=20180829,
TransferCompletionTime=163525, TransferCompletionDate=20180829, TransferEndTime=163525 , TransferEndDate=20180829, TransferDirection=Receive, TransferWork=File, TransferCommand=N/A, 
TransferProcessName=N/A, TransferScheduleDate=N/A, TransferScheduleTime=N/A, TransferExpirationDate=N/A, TransferExpirationTime=N/A, CompressionType=Non e, CompressedBytes=N/A, 
ConvertCRLF=no, EBCDICTranslate=no, TLS=no, EncryptionType=N/A, RecordFormat=N/A, FileCreateOptions=Create, FileAttributes=N/A, UNIXFile Permissions=644, EmailSuccessAddr=N/A, 
EmailFailureAddr=N/A, Allocation Type=N/A,Allocatio nDirectory=N/A, AllocationPrimary=N/A, AllocationSecondary=N/A, Volume=N/A, Unit=N/A, Nodeclass=N/A, Storclass=N/A, Mgtclass=N/A, 
Dataclass=N/A, BlockSize=0, RecordLength=0, UserData=N/A, LogonDomain=N/A, LocalFileName=/root/vani/bulk_recv/sslkeysand certs, LocalUserid=root, RemoteFileName=/root/ravindra/sslkeysandcerts, 
RemoteUserid=root, RemoteNodeName=10.108.80.84, RemoteNodeType=IpName, Remote PortNumber=N/A, TryCount=0, TryMaxCount=0, ByteCount=32, RecordCount=N/A, MemberCount=N/A, CheckPoin tCount=0,
CheckPointRestart=no, CheckPointInterval=0, StatusMsg=Transfer Completed, CrlMsg=N/A, StatusDiagCode=00, StatusSeverity=00, StatusReturnCode=N/A, TransferStatus=Success, Localc File=N/A,
RemoteCTFile=N/A, TempError=No, PPA1Action=N/A, PPA1S ource=N/A, PPA1Status=N/A, PPA1Data=N/A, PPA1ReturnCode=N/A, PPA2Action=N/A, PPA2 Source=N/A, PPA2Status=N/A, PPA2Data=N/A,
PPA2ReturnCode=N/A, PPA3Action=N/A, PPA3Source=N/A, PPA3Status=N/A, PPA 3Data=N/A, PPA3ReturnCode=N/A, PPA4Action=N/A, PPA4Source= N/A, PPA4Status=N/A, PPA4Data=N/A, PPA4ReturnCode=N/A,
Accelerator=N/A, ACCProtocol=N/A, ACCEncryption=N/A, ACCCompression=N/A, ACCMaxSpeed=N/A, ACCHost=N/A, ACCPort=N/A, SecurityPolicy=None, RemoveTrailingSpaces=N, ScanSubDir=N/A,
ClassOfService=Defa ult, CRC=N/A, TLSProtocol=N/A, TLSCipher=N/A,LocalHostName=NYLinuxHost

From version 8.1.0, only cfroot (a user under whose account the product is installed ) and members of the cfadmin group have “write” access to the Log.txt file ( 664 ) and log folder ( 775 ). Other users have only “read” access, therefore they cannot modify information in this file.

However, file transfers initiated by non-privileged users still have to be logged via “RPC logging requests”. A new daemon, CyberMgr (an RPC Server) has been added to version 8.1.0. All other applications send messages to CyberMgr, and CyberMgr is solely responsible to perform the requested updates/changes. CyberMgr runs under the same account as CyberResp.

Note: Two log files, namely admin and message have been added. All important PSU calls are logged to one of these log files.
Note: CyberMgr.access is used to communicate between CyberMgr and RPC clients. This file should be the same on CyberMgr and all PSU instances in the cluster.
Note: If the connection to the local CyberMgr takes a long time to complete, you can set environment variable RPCMaxWaitConnectTimeLocal. This environment variable defines the maximum amount of time in seconds that rpc client will wait for a connection to the Local CyberMgr RPC Server. If the connection time exceeds the defined number of seconds, the RPC request will not be completed and the transfer might fail.