Starting and stopping a runtime

Safeguards and best practices are provided to help you safely start and stop runtimes.

You need to be on the machine where the runtime's runtime cloud cluster is installed to start or stop it.

As a safeguard to prevent execution conflicts, only one instance of a given basic runtime, runtime cluster node, or runtime cloud cluster is allowed to run on the same machine at one time. This means that if a basic runtime, runtime cluster node, or runtime cloud cluster is currently running as a service, you cannot also start it as a desktop application and vice versa. Similarly, you cannot start two desktop instances. However, you can have two different basic runtimes running on the same machine at the same time. For parallel processing and failover capabilities, see information about runtime clusters.

When you manually stop a runtime, it waits for currently running processes to complete before it actually stops. The node does not start any more processes while it waits to stop. On the Properties panel, you can specify the number of minutes that the Boomi Enterprise Platform will wait before it forces a restart.

You can cause a runtime cluster or runtime cloud to be restarted in one of two ways:

• Select the Restart Runtime option on the Runtime Information panel (Manage > Runtime Management).
• Use a Java monitoring tool for JMX management, such as Java VisualVM, to issue a JMX command.

When you restart a runtime cluster or runtime cloud, a rolling restart of all nodes is performed. Running processes are allowed to complete before the node they are running on is restarted. You can modify the rolling restart behavior by setting properties on the Properties panel.

Basic runtime, cluster node, or cloud cluster running on Windows

When you install a basic runtime, runtime cluster node, or runtime cloud cluster, it automatically starts as a Windows service. This is the preferred method for running because it does not require a Windows user to be logged onto the machine at all times.

When connecting to some client applications, such as QuickBooks, the basic runtime, runtime cluster node, or runtime cloud cluster must run as a desktop application under a given Windows user rather than run as a Windows service. Running as a desktop application requires the user to be logged into Windows at all times for the basic runtime, runtime cluster node, or runtime cloud cluster to run.

Basic runtime, cluster node, or cloud cluster running on Linux

After you install a basic runtime, runtime cluster node, or runtime cloud cluster on a Linux machine, configure it to run as a daemon thread. Doing this prevents the server from shutting down the basic runtime, runtime cluster node, or runtime cloud cluster when the user logs off the machine.