Installing the initial runtime cluster node on Windows

Install the downloaded Windows version of the runtime cluster by running the executable file.

Before you begin

Runtime clusters require the Java 8 JRE or the 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.23.9.1.

Before completing these steps, download the runtime cluster installer and set up a Windows shared directory. Depending on the version of Windows you are running, you might require Administrator access to run the runtime cluster installer.

The installer installs a private copy of Java 11 for the runtime cluster to use. Alternatively, you can manage your own distribution of the Java 11 JDK by downloading the JDK from Amazon prior to installing the runtime cluster.

note

If you manage your own Java version instead of using the distribution provided by Boomi, Runtime cluster using forked execution require the Java 8 JDK rather than the JRE. Java 11 is distributed as a JDK by default, so no additional considerations are required when using this version.

The installer gives you an 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.

Warning

If there are Unicode characters in the directory path to where you intend to install the runtime cluster, the installation will fail.

Procedure

1. After downloading the runtime cluster installer, run the executable file.

2. If you see a security verification window, click Yes.

   The Cluster Setup Wizard opens.

3. If the installer cannot find the JRE on your machine, you receive a download prompt. Download the JRE to your machine.

4. On the Welcome page, click Next.

5. On the User Information page:

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

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

      • Your user name and password.

      • A valid installer token.

      You can generate installer tokens when you download the runtime cluster installer from the Cluster Setup dialog. When 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. Enter a name for the runtime cluster.

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

      note

      The following characters are reserved and cannot be used in the name: asterisk (*), backslash (\), caret (^), colon (:), dollar sign ($), greater than (>), less than (<), percent (%), pipe (|), question mark (?), quotation mark ("), slash mark (/), Yen sign (¥).

   4. (Optional) If the local machine uses an HTTP proxy to connect to the internet, select the Use Proxy Settings check box and enter the appropriate host, port, user name, and password for the proxy.

      If you do not fill out the proxy settings now, you can add them later.

   5. Click Next.

      You connect to and the platform authenticates your credentials.

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

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

6. (Optional) On the Accounts page:

   1. If your user name has access to multiple accounts, you see a list of accounts. Select the account to which this is associated. This step typically applies only to partners.

   2. Click Next.

7. (Optional) On the Environment page:

   1. (Optional) If you have created environments already, a list appears. Select the environment to which this runtime cluster is attached. If you do not select one, your new runtime cluster appears in the list of Unattached Runtimes on the Runtime Management page in the Integration user interface.

   2. Click Next.

8. On the Select Destination Directory page, select the installation directory and click Next.

   You must install the runtime cluster in the shared directory from the first machine. The directory name must look like this: //<host_name>/Share/<molecule_installation_directory>.

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 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 Select Start Menu Folder page, modify any Start Menu settings and shortcuts and click Next.

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

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

Results

The runtime cluster runs as a Windows service. You can view the runtime cluster online by going to Manage > Runtime Management.

Next steps

Next, you need to set up the Molecule’s Windows service.