Skip to main content
Feedback

Installing the initial runtime cloud cluster node on Linux

Install the downloaded Linux version of the initial runtime cloud cluster by running the executable file.

Before you begin

Runtime cloud clusters require either the Java 8 JRE or Java 11 JDK. Boomi recommends Java 11. Boomi internally tested Amazon Corretto OpenJDK Java 1.8.0_382 and Amazon Corretto Open JDK 11.0.20.8.1.

Before completing these steps, download the runtime cloud cluster installer and set up Linux shared directories.

The installer gives you the option to select local directories for storing working data and temporary data.

  • Boomi strongly recommends that you select the Use Local Storage for Runtime Assets setting. If you select local directories, ensure that these directories exist before you run the installer. The installer does not create the directories for you. For new runtimes, you can enable local storage during installation.

  • Do not select a local directory for storing your runtime cloud cluster's temporary data. Configuring a custom temporary directory on Linux interferes with the runtime cloud cluster's operation.

If you do not have Java 11 installed on your machine, you can download the installer file that includes a private copy of Java 11 (11.0.20.8.1) from the Runtime Management page. You can alternatively manage your own distribution of the Java 11 JDK by downloading the JDK from Amazon prior to installing the runtime cloud cluster.

note

Ensure that you use the Java binary to run the installer comes from the <jdk>/jre/bin directory and not the <jdk>/bin directory.

If you choose not to use the user interface to install the initial runtime cloud cluster, use the console mode option (-c) of the install4j installer.

Procedure

  1. Locate the runtime cloud cluster installer file that you saved on your machine.

    After the file is downloaded, the installation wizard can be run using a command line, which recommends, or with the user interface.

  2. Do one of the following:

    • To run the installer in console mode from a command line, run the file with the -c flag, such as:

      sh /<path>/cloud_install64.sh -c

    • If you use the user interface, double-click the install file (you might need to change the properties to allow the file to run: chmod +x cloud_install64.sh) or run the file from the command line without the command-only flag:

      sh /<path>/cloud_install64.sh

  3. On the Welcome page, click Next.

  4. On the User Information page:

    1. Select User Name and Password or Token, depending on how you want to authenticate the runtime cloud cluster.

    2. Enter one of the following, depending on the selected option:

      • Type your user name and password

      • Type a valid installer token ID

      You can create installer tokens when you download the runtime cloud cluster installer from the Cloud Setup dialog. After generating tokens, they are valid only for the specific account and runtime clouds. Tokens expire after a set amount of time ranging from 30 minutes to 24 hours.

    3. Type a name for the runtime cloud cluster.

      The runtime cloud cluster name is what you see following the runtime cloud name when you go to Manage > Runtime Management. The name defaults to the local host name, but you can change it to something more familiar.

    4. Click Next.

    You connect to the Boomi Enterprise Platform and it authenticates your credentials.

    If you specified a user name and password, the Accounts page appears followed by the Clouds page.

    If you specified an installer token, the Select Directory for Symlinks page appears and you can skip to step 7.

  5. (Optional) On the Accounts page:

    1. If your user name has access to multiple accounts, a list appears. Select the account to the associated runtime cloud cluster. This step typically applies only to partners.

      In the command line, each account name is followed by a number within square brackets, for example, [123]. To select an account, enter its number.

    2. Click Next.

  6. On the Clouds page, select the runtime cloud to associate with the runtime cloud cluster and click Next.

    This runtime cloud is the one that you added on the Runtime Management page prior to downloading the runtime cloud cluster installer.

  7. (Optional) On the Environment page:

    1. If your account created environments, you see a list of them. Select the one to which this runtime cloud cluster will be attached. If you do not select one, your new runtime cloud cluster will appear in the list of Unattached Runtimes on the Runtime Management page in the user interface.

    2. Click Next.

  8. On the Select Destination Directory page, select the folder where the runtime cloud cluster is installed and click Next.

  9. On the Select Local Cluster Node Directories page:

    1. Select a local directory for storing the runtime cluster node.

      The "Yes, store assets locally" is selected by default and strongly recommended. You must provide a local directory path with this option. If you select "No, use cluster shared storage instead (not recommended)" you will be directed to a new dialog box to create a symliks and provide a destination directory.

    2. Select a directory for storing the runtime cluster node’s temporary data. This value sets the -Djava.io.tmpdir property in the <runtime_install_directory>/bin/atom.vmoptions file.

    3. Click Next.

  10. On the Information page, review the installation settings and click Next.

  11. When the installation is complete, click Finish to start the runtime cloud cluster.

Results

You can view the runtime cloud cluster online by going to Manage > Runtime Management.

The installation log file is located in <cloud_installation_directory>tmp and its file name starts with i4j.

Next steps

Next you can install additional runtime cloud clusters.

On this Page