Contact Free trial Login

Install Runtime Fabric Manually

This topic describes how to install and register Anypoint Runtime Fabric on VMs hosted in your data center.

Ensure your infrastructure meets the minimum hardware, operating system, and networking requirements. These requirements should be reviewed by your organization’s operations, networking and security teams.

Before you Begin

Ensure the following criteria have been met before beginning the installation:

Operations Performed During Installation

The installation performs the following actions on each VM:

  • Formats the dedicated disks.

  • Mounts the dedicated disks to the appropriate path.

  • Sets iptable rules.

  • Enables the required kernel modules.

  • Enables and reloads system services.


First, download the scripts ZIP file on the controller VM which will act as the leader in the installation.

  1. Sign in to Anypoint platform and navigate to Runtime Manager.

  2. On the left navigation pane, select Runtime Fabrics.

  3. Click on the Runtime Fabric you created. It should be in the Activating state.

  4. Right-click the Download files button and select "Copy link location".

  5. Download the file to the controller VM.

    1. Open a shell (SSH session) to the controller VM.

    2. Download the file: curl {INSTALLER_URL} --output

  6. Once downloaded, unzip the file in a separate directory.

    mkdir -p ./rtf-install-scripts && unzip -d ./rtf-install-scripts

Inside the rtf-install-scripts/ directory, you’ll find a sub-directory named manual containing the following:

  • a script to help generate environment variables for each VM.

  • a markdown file containing instructions to aid with installation.

Variables to Define

Second, become familiar with the variables needed for installation. The value for the RTF_ACTIVATION_DATA variable can be found on the Runtime Fabric page on Runtime Manager.

Parameter Description Example


IP addresses of the controller VMs, separated by whitespace. The first IP address will need to be the leader of the installation.



IP addresses of the worker VMs, separated by whitespace.



The full block device path for the dedicated disk used for Docker, supporting 1000 provisioned IOPS.



The full block device path for the dedicated disk used for etcd, supporting 3000 provisioned IOPS.



The encoded Runtime Fabric activation data found in Runtime Manager.



The base64 encoded contents of your organization’s Mule Enterprise license key (license.lic).


To help identify the block device paths to your disks, use the lsblk command on the VMs. To base64 encode the Mule license key, use the base64 -w0 license.lic command. (base64 -b0 license.lic in OSX)

Optional Variables

The following variables can be defined based upon your organization’s requirements.

Parameter Description Example


A hostname and port for a HTTP proxy server to forward outbound HTTP requests.


A hostname and port for a TCP proxy server to forward outbound TCP requests.


A comma-separated list of hosts which should bypass the proxy.,


An integer representing the user ID to run each Runtime Fabric service. Overrides the default behavior of creating a user named "planet".



An integer representing the group ID used when running each Runtime Fabric service. Overrides the default behavior of creating a group named "planet".


To install a specific version of Runtime Fabric, transfer the installation package to this path on the controller VM acting as the leader during installation: /opt/anypoint/runtimefabric/installer.tar.gz. This will skip downloading the latest package from Anypoint control plane.

Third, use the ./ script to generate the environment variables for each VM.

  1. Copy the command below in a text editor and fill in the values of each variable inside the single quotes.

  2. Open a shell/SSH on the controller VM and navigate to the manual sub-directory from the unzipped directory.

  3. Copy the command from your text editor, paste it in the terminal, and run the command on the controller VM. The script should output a set of instructions and a script to run on each VM, categorized by the IP address of each VM.

    1. Execute the snippet on each VM based upon its IP address to apply the required environment variables.

    2. On each VM, copy the ./scripts/ file to /opt/anypoint/runtimefabric, and ensure the script is executable. The script below assumes the present working directory contains the unzipped directory rtf-install-scripts.

      mkdir -p /opt/anypoint/runtimefabric && cp ./rtf-install-scripts/scripts/ /opt/anypoint/runtimefabric/ && chmod +x /opt/anypoint/runtimefabric/
  4. Run the script in privileged mode on the controller VM.

    sudo /opt/anypoint/runtimefabric/ foreground
  5. Wait until the installation has successfully completed the pre-flight checks. The output should continue past the Execute preflight checks message to indicate the checks have passed:

    Tue Aug 14 02:28:54 UTC Starting the installation
    Tue Aug 14 02:28:56 UTC Operation has been created
    Tue Aug 14 02:28:57 UTC Execute preflight checks
    Tue Aug 14 02:29:48 UTC Configure packages for all nodes
    Tue Aug 14 02:29:59 UTC Bootstrap all nodes
  6. Execute the script in privileged mode on all the other VMs. This step can be performed on each VM concurrently.

    sudo /opt/anypoint/runtimefabric/ foreground
  7. If the installation process encounters an error, it’ll exit with a message to help indicate how to resolve the error. In most cases, errors can be resolved by updating one or more variables to a valid value, and re-running the script.

This step will install Runtime Fabric across all VMs to form a cluster. It may take 15-25 minutes or longer to complete.

When the installation completes successfully, the file /opt/anypoint/runtimefabric/.state/init-complete is created.

Access to Ops Center

  1. After the installation has completed, a host, username and password will be outputted to access the Ops Center. Copy these credentials and store them securely.

Common Errors

If the installation process encounters an error, it’ll exit with a message to help indicate how to resolve the error. In most cases, errors can be resolved by updating one or more values in the /opt/anypoint/runtimefabric/env file to the correct value, and re-running the script.

Next Steps

Before deploying applications on Anypoint Runtime Fabric, you’ll need to perform the following steps:

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub