Adding Hubs and Gateways

This procedure describes how to add additional Hubs and Gateways to your Control-M MFT Enterprise environment. This ensures that file transfers between external and internal users are successful even if one Hub or Gateway is down.

BMC recommends to set up at least three Hubs and two Gateways.

Before You Begin

Ensure that you have completed all the setup procedures, as described in Setting Up the Control-M MFT Enterprise Environment.

Begin

  1. From the Environment tab, do one or more of the following:

    • To add a Hub, do the following:

      1. Click Add Hub.

      1. From the Add Agent drop-down list, select one of the available Agents to serve as a Hub, and then click Save.

      • All Agents must be installed on the same platform (Windows or Linux) and defined in the same host group.

      • After a new Hub is added to the environment, its connection profiles, PGP, and MVS templates are overwritten with the existing host data. BMC recommends that you add a new MFT host to the environment.

    • To add a Gateway, do the following:

      1. Click Add Gateway.

      1. Type the hostname and the port where the Gateway is installed, and then click Add.

  2. Repeat these steps to add additional Hubs and Gateways.

Connecting to a Centralized Database

This procedure describes how to connect an external centralized database to a Hub in a Control-M MFT Enterprise High Availability environment. You only need to perform this procedure when you add a second Hub, as described in Adding Hubs and Gateways.

You can connect to either a BMC-provided Control-M MFT Enterprise Database or an existing external PostgreSQL 15 or higher.

Before You Begin

Begin

  1. From the Environment tab, click Add Hub.

    The Connect External Database and Add Hub dialog box appears.

  2. Define the required parameters, as described in Centralized Database Parameters.

  3. Click Add.

Centralized Database Parameters

The following table describes the parameters that connect a Hub to a centralized database.

Parameter

Description

Database Type

Determines one of the following types of centralized databases:

  • MFT Enterprise Database: Connects the Hub to a dedicated, BMC-provided Control-M MFT Enterprise Database.

  • PostgreSQL: Connects the Hub to an existing external PostgreSQL database.

Database Name

Defines the name of the database where the Hubs store the shared configuration.

If you connect Control-M MFT Enterprise Database, you do not need to create the database manually since it is automatically created with this name when you add the Hub.

If you connect an external PostgreSQL database, you must provide the name of the database that you created manually before you connect it to the Hub.

Rules:

  • Number of characters: 1-255 characters

Database Host (PostgreSQL)

Defines the external PostgreSQL database server hostname.

Rules:

  • Number of characters: 1-255 characters

Port (PostgreSQL)

Determines the port number to connect to the external PostgreSQL database server.

Valid Values: 1-65535 (numeric values only)

Default: 5432

Primary Database Host (Control-M MFT Enterprise Database)

Defines the primary external Control-M MFT Enterprise Database server hostname.

Rules:

  • Number of characters: 1-255 characters

Port (Control-M MFT Enterprise Database)

Determines the port number to connect to the external primary Control-M MFT Enterprise Database server.

Valid Values: 1-65535 (numeric values only)

Default: 9092

Secondary Database Host (Control-M MFT Enterprise Database)

(Optional) Defines the secondary external Control-M MFT Enterprise Database server hostname.

Rules:

  • Number of characters: 1-255 characters

Port (Control-M MFT Enterprise Database)

(Optional) Determines the port number to connect to the external secondary Control-M MFT Enterprise Database server.

Valid Values: 1-65535 (numeric values only)

Default: 9092

Database Username

Defines the username to connect Control-M MFT Enterprise to the database.

If you connect the Control-M MFT Enterprise Database, you do not need to create the user manually since it is automatically created when you add the Hub.

If you connect an external PostgreSQL database, you must provide the username of the database that you created manually before you connect it to the Hub.

Rules:

  • Number of characters: 1-255 characters

Database Password

Defines the password to connect Control-M MFT Enterprise to the database.

If you connect the Control-M MFT Enterprise Database, you do not need to configure the password manually since it is automatically configured when you add the Hub.

If you connect an external PostgreSQL database, you must provide the password for the database that you created manually before you connect it to the Hub.

Rules:

  • Number of characters: 1-255 characters

Select Agent

Determines which available Agent is designated as a Hub.

Changing the Control-M MFT Enterprise Database Server Listening Port

This procedure describes how to change the listening port of the Control-M MFT Enterprise Database server.

Begin

  1. Stop the Control-M MFT Enterprise Database service, as follows:

    • Windows: Stop the Control-M Managed File Transfer Enterprise Database service.

    • Linux: Run the following command to stop the mftedb service:

      systemctl stop mftedb.service

  2. Open the mftedb_startup.properties configuration file as a user with administrator or root privileges from one of the following directories:

    • Windows: <local drive with Control-M MFT Enterprise Database>\Program Files\BMC Software\MFT Enterprise Database\data

    • Linux: /opt/bmc/mftedb/data

  3. Change the value of db_port parameter and save the change. The default port is 9092.

  4. Start the Control-M MFT Enterprise Database service, as follows:

    • Windows: Start the Control-M Managed File Transfer Enterprise Database service.

    • Linux: Run the following command to start the mftedb service:

      systemctl start mftedb.service