Runtime Management

In Runtime Management, you can review and modify the properties and settings for runtimes and environments.

You can also review and modify some properties and settings for runtime cloud clusters and cloud attachments.

To modify the properties and settings on this page (Manage > Runtime Management), you must have the Runtime Management privilege. If you have the Runtime Management Read Access privilege, you can review the properties and settings but not modify them.

note

Runtime Management panels that are not yet available to users with the Read Access privilege are not enabled in the UI.

Depending on which Runtime Management privilege you have, you can do some or all of the following for a basic runtime, runtime cluster, runtime cloud cluster, or cloud attachment in the basic runtimes list:

• Monitor its status.

• View its installation date.

• Review its startup properties.

• Change some of its properties, download logs, view and update counters, and subscribe to notifications.

• Access web server, queue server, and MLLP server settings (if these features are enabled in the account).

• Check the status of individual nodes, head node, or delete nodes in a runtime cluster or runtime cloud (runtime cloud cluster or cloud attachment) on the Cluster Status panel.

• Get pending updates to basic runtimes, runtime clusters, cloud attachments, runtime cloud clusters, and connectors prior to the full release. If you change your mind, you can roll back the updates prior to the full release.

• Set a schedule for receiving updates (if this feature is enabled in the account).

• Review the release status of integration packs to which the basic runtime, runtime cluster, cloud attachment, or runtime cloud cluster is attached and, if needed, apply updates (if this feature is enabled in the account).

• Review a list of deployed processes, and stop, add, edit, or resume deployed process schedules.

• Review information about deployed certificates, including certificates that have expired or are about to expire.

• Review the status of listeners and, if needed, pause, resume, or restart all or selected listeners.

• Review a list of installed JAR files.

• Check the status of a runtime cloud’s execution workers and stop an execution worker on the Worker panel.

You can also do some or all of the following for an environment in the Environments list:

• Review the environment’s properties and, if needed, change some of them.

• Set environment extensions.

• Attach runtimes.

• Assign user roles.

• Review the release status of integration packs to which the environment is attached and, if needed, apply updates.