Basic runtimes within an environment

There are important limitations on attaching basic runtimes to environments.

Attaching basic runtimes to environments is controlled on the Environments page. The Unattached Runtimes list shows all basic runtimes that are not attached to any environment.

• For accounts with Basic environment support, each environment in the account can have a single basic runtime attached.

• For accounts with Unlimited environment support, each environment can have an unlimited number of basic runtimes attached.

If your account has Unlimited environment support and test connections are enabled, you can attach local basic runtimes to production or test environments. A runtime cloud can be attached only to an environment with the same classification. In other words, test runtime clouds can only be attached to test environments, and production runtime clouds can only be attached to production environments. If you set up additional basic runtimes in a runtime cloud, those basic runtimes can be attached only to an environment with the same classification.

When a local basic runtime or runtime cloud is attached to an environment, the connection licenses are calculated based on the classification of the environment. For example, when a basic runtime is attached to a test environment, the test connection licenses are recalculated. When a basic runtime or runtime cloud is moved from one environment classification to another, the connection licenses are recalculated. When a basic runtime is detached from a test environment and attached to a production environment, the test and production connection licenses are recalculated. See the topic about test connection licensing for more information.

Deployed processes to which an environment are already attached can execute in basic runtimes subsequently attached to that environment upon attachment. Execution occurs automatically for those processes for which a default schedule is enabled.

Attaching or detaching a runtime

You can attach or detach basic runtimes using the Manage > Runtime Management page. For accounts with Basic environment support, each environment in the account can have a single basic runtime attached. For accounts with Unlimited environment support, each environment can have an unlimited number of basic runtimes attached.

note

You must have the Runtime Management, Environment Management, and Packaged Component Deployment privileges to perform this task. If you have the Runtime Management Read Access privilege, you cannot perform the task.

When you add a basic runtime to an existing environment, all encrypted values must be re-entered in the Environment Extensions dialog after the runtime is added.

1. Go to Manage > Runtime Management.

2. To attach a basic runtime, do one of the following items:

   a. Click the Environment from the Environments list on the left.

   Under Configuration, click in the Attachments field and select a runtime from the list.

   b. In the Environments list on the left, click an unattached runtime.

   From Attach to Environment, select an Environment from the drop-down list.

   c. In the Environments list on the left, drag a runtime from the Unattached runtimes list to the Environment that you want to attach it to, and click OK.

3. To detach a basic runtime, do one of the following items:

   a. Click the Environment from the Environments list on the left.

   Under Configuration, click the X next to the runtime name from the Attachments list and then click OK.

   b. In the Environments list on the left, click an attached runtime.

   From Runtime Controls section of the Runtime Information panel, click Detach From Environment and then click OK.