Control-M MFT Enterprise Installation

Control-M MFT Enterprise System Requirements

This table lists the minimum system requirements for the Control-M MFT Enterprise Hub and Gateway.

Operating System

Specifications

Requirements

Windows

  • Up to 10,000 daily external file transfers.

  • Up to 20 GB of total volume per day.

  • Up to 50 concurrent sessions.

The Hub machine must meet the following minimum requirements:

  • CPUs: 4

  • RAM: 16 GB

  • Disk Space: 100 GB

The Gateway machine must have the following requirements:

  • CPUs: 4

  • RAM: 16 GB

  • Disk Space: 50 GB

  • Up to 150,000 daily external file transfers

  • Up to 250 GB of total volume per day

  • Up to 200 concurrent sessions

The Hub machine must meet the following minimum requirements:

  • CPUs: 8

  • RAM: 32 GB

  • Disk Space: 100 GB

The Gateway machine must meet the following minimum requirements:

  • CPUs: 8

  • RAM: 16 GB

  • Disk Space: 50 GB

  • Up to 1,000,000 daily external file transfers.

  • Up to 1 TB of total volume per day.

  • Up to 500 concurrent sessions.

You must set a High Availability environment with at least 3 Hubs and 3 Gateways to handle such loads. For higher loads, add additional Hubs and Gateways.

Each Hub machine must meet the following minimum requirements:

  • CPUs: 8

  • RAM: 32 GB

  • Disk Space: 100 GB

Each Gateway machine must meet the following minimum requirements:

  • CPUs: 8

  • RAM: 16 GB

  • Disk Space: 50 GB

Linux

  • Up to 10,000 daily external file transfers.

  • Up to 20 GB of total volume per day.

  • Up to 50 concurrent sessions.

The Hub machine must meet the following requirements:

  • CPUs: 4

  • RAM: 16 GB

  • Disk Space: 100 GB

The Gateway machine must have the following requirements:

  • CPUs: 4

  • RAM: 16 GB

  • Disk Space: 50 GB

  • Up to 150,000 daily external file transfers.

  • Up to 250 GB of total volume per day.

  • Up to 200 concurrent sessions.

The Hub machine must meet the following requirements:

  • CPUs: 8

  • RAM: 32 GB

  • Disk Space: 100 GB

The Gateway machine must meet the following minimum requirements:

  • CPUs: 8

  • RAM: 16 GB

  • Disk Space: 50 GB

  • Up to 1,000,000 daily external file transfers.

  • Up to 1 TB of total volume per day.

  • Up to 500 concurrent sessions.

  • You must set a High Availability environment with at least 3 Hubs and 3 Gateways to handle such loads. For higher loads, add additional Hubs and Gateways.

    		•

    Each Hub machine must meet the following minimum requirements:

    • CPUs: 8

    • RAM: 32 GB

    • Disk Space: 100 GB

    Each Gateway machine must meet the following minimum requirements:

    • CPUs: 8

    • RAM: 16 GB

    • Disk Space: 50 GB

    Installing the Control-M MFT Enterprise Gateway on Linux

    This procedure describes how to install Control-M MFT Enterprise Gateway on Linux in the demilitarized zone (DMZ), also known as a perimeter network. The Gateway is a proxy server used to transfer files to and from the Control-M MFT Enterprise Hub by external users.

    Before You Begin

    Begin

    1. Copy the installation files to the host where you want to install the Gateway.

      If you are using the GUI, set the environment variable DISPLAY to value <hostName>:0.0. It is not necessary to set DISPLAY for console mode or silent mode. For more information, see Setting Environment Variables in UNIX.

    2. From the MFT Gateway account home directory, run the following command:

      setup.sh

    3. Follow the on-screen instructions until the installation is complete.

      The MFT Enterprise Gateway automatically restarts after the installation is complete.

      To manually start the Gateway, run the following command:

      mft-proxy/exe/start-mft-proxy.sh

      To manually stop the Gateway, run the following command:

      mft-proxy/exe/shut-mft-proxy.sh

    Installing the Control-M MFT Enterprise Gateway on Windows

    This procedure describes how to install Control-M MFT Enterprise Gateway on Windows in the demilitarized zone (DMZ), also known as a perimeter network. The Gateway is a proxy server used to transfer files to and from the Control-M MFT Enterprise Hub by external users.

    Before You Begin

    Begin

    1. Copy the installation files to the host where you want to install the Gateway.

    2. From the MFT Gateway account home directory, run the following command:

      setup.exe

    3. Follow the on-screen instructions until the installation is complete.

      The MFT Enterprise Gateway automatically restarts after the installation is complete.

      • To manually start the Gateway, start the Control-M MFTE Gateway service.

      • To manually stop the Gateway, stop the Control-M MFTE Gateway service.

    Configuring the Control-M MFT Forward Proxy

    This procedure describes how to configure the Control-M MFT Forward Proxy that is included in the Control-M MFT Gateway installation. This proxy runs as a standalone process, separate from the Gateway, and you can use it to direct your file transfers via SFTP, FTPS, and S3 protocols.

    Begin

    1. Ensure that the data/forwardConfig.properties file contains the required settings (port and optional credentials).

    2. Run one of the following commands:

      • Linux: start-forward-proxy.sh

      • Windows: <MFTE Home>\ForwardProxy\exe\start_forward_proxy.cmd

    Configuring the Automatic Startup Procedure for Control-M MFT Enterprise Gateway

    This procedure describes how to configure the automatic startup procedure for Control-M MFT Enterprise Gateway on Linux.

    Begin

    1. Log in as root.

    2. Navigate to the following to location:

      /etc/systemd/system/

    3. Create a new unit service file with 644 permissions.

      The extension must be .service.

      b2b-gtw.service

    4. Open the file and type the following:

      Copy 
      [Unit]Description=B2B Gateway
      [Service]
      Type=forking
      RemainAfterExit=yes
      ExecStart=/[mft_proxy_exe_dir]/start-mft-proxy.sh
      ExecStop=/[mft_proxy_exe_dir]/shut-mft-proxy.sh
      User=[mft_proxy_user]
      Group=[mft_proxy_group]
      [Install]
      WantedBy=multi-user.target

    5. Save the file.

    6. From a command line, run the following commands:

      • systemctl daemon-reload

      • systemctl enable [unit service file].service

    7. Restart the Control-M MFT Enterprise Gateway host and check that the Gateway is up and running.

    Configuring the Control-M MFT Enterprise Gateway as a Windows Service

    This procedure describes how to configure the Control-M MFT Enterprise Gateway as a Windows service, which enables the Gateway to automatically start up after the machine restarts.

    Begin

    1. Navigate to the following directory:

      <Gateway>\exe\svc

    2. Run the following command:

      install_gateway_as_service.cmd

    3. Right click on the Gateway home directory and select Properties > security > Edit.

    4. Verify that the LOCAL SERVICE user has full control to the directory and all its sub-directories.

    5. Open the service Properties window, select Recovery, and then select to Restart the service on 1st, 2nd or any subsequent failure.

      This ensures that the service restarts after a failure.

    6. Start up the Control-M MFT Enterprise Gateway service.

    To remove the MFT Enterprise service, navigate to <Gateway>\exe\svc and run the following command:

    uninstall_gateway_as_service.cmd

    Uninstalling Control-M MFT Enterprise Gateway from Linux

    This procedure describes how to uninstall Control-M MFT Enterprise Gateway from Linux.

    Begin

    1. Navigate to the following directory:

      <InstallFolder>/BMCINSTALL/uninstall/DRM2B.8.0.00.100

    2. Do one of the following:

      • Interactively Uninstall: Run the following command:

        ./uninstall.sh

      • Automatically Uninstall: Run the following command:

        ./uninstall.sh -silent

      The Control-M MFT Enterprise Gateway is successfully removed from your host.