Important YAML Parameters

The YAML files provided are sample files designed to provide an example of a working Kubernetes network. You must update these files to meet the needs of your environment.

Parameter Description
spec: image: Defines the name of the Docker image that is loaded. The default image name is mftcc:8.3.0.
spec: ports Defines the ports that are used. In the service (_svc) yaml files, the ports are defined in two places.
Note: It is critical that the Command Center and Internet Server ports are different. Otherwise Internet Server requests may be incorrectly forwarded to the Command Center and vice versa. Ports should be the same across all TIBCO MFT Command Center containers. But the ports used by TIBCO MFT Internet Server cannot be used by TIBCO MFT Command Center.
spec: replicas Defines how many instances are started.
spec: env Defines environment variables that are set by Kubernetes. These environment variables provide the information for TIBCO MFT Internet Server and TIBCO MFT Command Center to connect to the database and define persistent storage that is used for log files. The following three environment parameters are supported: (These parameters only need to be updated if the persistent storage directory is changed.)
  • COM_TIBCO_MFT_CE_DBCFG: Defines the location of the file that defines the connectivity information to the MFT database. This file was created in "Step 10: Configure the TIBCO MFT Command Center Database" by executing "Generate Cloud Database XML file". This file must then be copied to persistent storage so that TIBCO MFT Command Center can access this file at initialization. This parameter must be defined if you want TIBCO MFT Command Center to connect the TIBCO MFT Command Center Server to a specific database. If this parameter is not defined, the database settings in the web.xml file is used.
  • COM_TIBCO_MFT_CE_TEMPLATENAME: Defines the name of the template used to create Internet Server FTP, Platform, AS2, and SFTP Services. If this parameter is not defined, the default template name is used: "*DefaultTemplate". If you want to have different settings for the Command Center containers, you can define a new template name. If the template name defined to Command Center is not in the database, it is created when TIBCO MFT Command Center starts.
  • COM_TIBCO_MFT_TRACEDIR: Defines the directory where all log files are saved. This is generally set to a directory in the persistent storage. TIBCO MFT Command Center attempts to create the directory. Make sure that TIBCO MFT Command Center has the necessary rights to create and update files in this directory.
  • COM_TIBCO_MFT_CE_DB_TYPE: Defines the type of cloud database used.
  • COM_TIBCO_MFT_CE_DB_URL: Defines the URL of the cloud database.
  • COM_TIBCO_MFT_CE_DB_USER: Defines the cloud database user.
  • COM_TIBCO_MFT_CE_DB_PWD: Defines the cloud database password.
  • COM_TIBCO_MFT_CE_DB_DRIVER: Defines the cloud database driver.
Note:

If the following 5 variables are defined, the COM_TIBCO_MFT_CE_DBCFG variable is ignored.

COM_TIBCO_MFT_CE_DB_TYPE; COM_TIBCO_MFT_CE_DB_URL; COM_TIBCO_MFT_CE_DB_USER; COM_TIBCO_MFT_CE_DB_PWD; COM_TIBCO_MFT_CE_DB_DRIVER

Use the clouddbconfig utility to generate these values. Or on the Server Detail Menu, enter 7 for the option Display Cloud Database Environment variables

These environment variables should be set in the Kubernetes YAML config file. See step 1 in Prepare the Kubernetes Environment.

spec: volumeMounts Defines the persistent storage directory that will be mounted.
spec: volumes Defines the information required to mount an NFS share.

External Ports

If you are using auto scaling, update file mftis-hpa.yaml to define the scaling values. The scaling values in the default file are very low to facilitate testing this feature.

The following list provides the external ports defined in the YAML files. If you want to use different ports, then you must update the ports in the YAML files.

Command Center
  • 31443 HTTPS
  • 31480 HTTP
  • 31464 Platform Server
  • 31465 Platform Server SSL
  • 31466 Platform Server Tunnel
Note: The ports should be the same across all TIBCO MFT Command Center instances.
Note: The ports defined as the FTP Data Ports must match the ports defined in the Admin System Configuration > Global FTP Settings > Starting Port and Number of Ports to Use.