Step 2: Create a Base TIBCO MFT Platform Server for UNIX Installation

You can install TIBCO MFT Platform Server for UNIX in two ways: as a root user or as a non-root user.

Procedure

  1. Install TIBCO MFT Platform Server for UNIX. For installation instructions, see TIBCO Managed File Transfer Platform Server for UNIX Installation.
    Note: After installation, TIBCO MFT Platform Server for UNIX configuration files are saved in the $CFROOT/config directory.
  2. Before you create the Docker images, configure the following components.
    Component to be Configured Program Used
    Config.txt Using a text editor such as “vi”
    Nodes Using the cfnode program
    User profiles Using the cfprofile program
    Responder profiles Using the cfrprofile program
    Other config files, such as AccessControl.cfg, CfAlias.cfg, CfgPostProc.cfg, Cfcos.cfg, and Cflist.cfg Using a text editor such as “vi"
  3. Optional: If you use TLS or TLS Tunneling mode, you must do the following configurations also:
    • Create the necessary certificates, private keys, and private key passwords and configure the SSL/TLS parameters in the config.txt file in both Server and Client sections.
    • Update the trusted authority will as required.
    • Update the SSLAuth,cfg files as required.
    • Update the SSL parameters for the client and the server in the config.txt file.
    For information on these configurations, see TIBCO Managed File Transfer Platform Server for UNIX User's Guide.
  4. Configure the following parameters in the [ COMMON ] section of the config.txt file to use persistent storage when running in a production environment. This ensures that audit files are kept permanently, that there are no duplicate transaction ids, and that transfers can restart when the container is restarted.
    Parameter Description
    LogEventFileName

    		Defines where the Log.txt files are saved. Each completed file transfer is logged in the Log.txt file.
    Note: The permissions for the LogEventFileName directory must be the same as the permissions in the $CFROOT/log directory.
    PQFDirectory Defines where the PQF files are stored. PQF files save restart information about file transfers.
    Note: The permissions for the PQF directory must be the same as the permissions in the $CFROOT/PQF directory.
    TransnumFileName Defines the name of the Transaction Number file. This file is used to keep track of the current active transaction number. It is not recommended to save this file in the config directory. It is recommended to save the transnum file in the in the same directory as the Log.txt files. Optionally, the transnum file can be saved in its own directory.
    Note: The permissions for the TransnumFileName and the directory where this file is located must be the same as the the permissions in the $CFROOT directory.
    Note: Multiple Platform Server containers cannot point to the same persistent directories for the three parameter defined above, unless the server is a passive server running in an HA Active/Passive mode. If you point multiple Platform Server containers to the same directory, you will get duplicate transaction numbers and the Log.txt files that contain the audit records may be corrupted.