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.

Note: Note: Sample Docker files are distributed in the following folder: PSU Install/cloud
    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 as required.
    • Update the SSLAuth.cfg files as required.
    • Update the SSL parameters for the client and the server in the config.txt file. The SSL parameters are defined as described in the table below:
    • Parameter Defined Section
      ClientVerification Server
      CertificateFileName Server and Client
      PrivateKeyFileName Server and Client
      PrivateKeyPwdFileName Server and Client
      TrustedAuthorityFileName Server and Client
    If you want the ability to update these files without rebuilding the Docker images, then you should consider saving these files to persistent storage. 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.
    Note: The values for these parameters should be used in Step 7: Creating Persistent Storage to Save Configuration and Audit Files.
    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 PQFDirectory 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 permissions in the $CFROOT directory.

    ConfigDirectory

    Defines the directory in persistent storage where configuration files are located.

    Note: The permissions for the ConfigDirectory must be the same as the permissions in the $CFROOT/config directory.
    LogMessageFileName

    Defines where message files are saved in persistent storage.

    Note: The permissions for the LogMessageFileName directory must be the same as the permissions in the $CFROOT/log directory.
    LogAdminFileName

    Defines where admin message files are saved in persistent storage.

    Note: The permissions for the LogAdminFileName directory must be the same as the permissions in the $CFROOT/log directory.
    Note: Unless running in HA mode, each Platform Server container should point to different persistent storage directories. 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 get corrupted.