Migrating Log.txt and transnum Files from the Old Version to the New Version
TIBCO MFT Platform Server for UNIX writes an audit record for each completed transfer to the following file:
$CFROOT/log/Log.txt.yyyymmdd
Each transfer, whether successful or unsuccessful, is written to this log file. There are two ways to inquire on this log file:
- Platform Server
cfinq
Utility - Command Center Audit Poll or Collection
When you install TIBCO MFT Platform Server for UNIX over an existing installation
When you install the new version of TIBCO MFT Platform Server for UNIX in an existing installation directory, the Log.txt
files will remain; you do not need to do anything.
When TIBCO MFT Platform Server for UNIX is installed in a new directory
When you install the new version of TIBCO MFT Platform Server for UNIX in a new installation directory, there are no log files in the log directory. This causes two problems:
-
The
cfinq
utility is not be able to view any transfers from the old installation directory. -
Command Center Collection fails. This is a more serious issue because many companies use Collection as a critical part of the process flow.
There are two approaches to resolving the collection problem:
-
Approach 1: Copying Log and Transaction Number files
-
Approach 2: Resetting the Collection History
Approach 1: Copying Log.txt
and transnum
Files
Before starting the new TIBCO MFT Platform Server CyberResp
daemon, perform the following procedure:
1. | Stop the CyberResp daemon on the old TIBCO MFT Platform Server version. (You must not use this version anymore). |
2. | Copy the transnum file from the old TIBCO MFT Platform Server to the new TIBCO MFT Platform Server to ensure that there are no duplicate transaction numbers. |
3. | Copy or move the Log.txt files from the log directory of the old version to the log directory of the new version. You can copy/move all of the files, or you can copy/move only the last few days. |
-
The
cfinq
utility is able to view the audit records from previous versions of TIBCO MFT Platform Server. -
Command Center Collections continues to work and no audit records is lost. This assumes that Command Center Collection is configured for the IP port of the new TIBCO MFT Platform Server.
Approach 2: Resetting the Collection History
Before upgrading the TIBCO MFT Platform Server, you can perform the following procedure:
-
Make sure that all platform transfer records have been collected by the Command Center. (If you are migrating to HA mode, make sure that all audit records have been collected on both Platform Servers).
-
Stop the old version of TIBCO MFT Platform Server.
-
Copy the
transnum
file from the old version to the new version of TIBCO MFT Platform Server to ensure that there are no duplicate transaction numbers. -
Stop the Collector.
- Go to the Command Center Update Server page for the new TIBCO MFT Platform Server.
- Click the Management Options tab.
- Select the Reset Collection History check box.
- Click Update to update the server definition.
- Start the Collector.
Collection is then started for all transfers completed by the new TIBCO MFT Platform Server.