About Orchestration Settings

Orchestration settings allow you to configure properties for individual orchestrations in a project configuration. For each orchestration you can specify whether the orchestration is enabled, the logging levels, logging behavior, and the maximum number of jobs that the orchestration can simultaneously run.

When a project configuration is undeployed you can edit the following orchestration settings:

Orchestration Settings Description
Enabled Indicates whether an orchestration is enabled and can be deployed. At least one orchestration in a project configuration must be enabled to deploy a project configuration. By default, all orchestrations in a project configuration are enabled.
Logging Level Allows you to specify the level of orchestration details that are logged in the System Logs.
  • None - Orchestration status and activity are not logged.
  • Initial Values - Only the initial values of orchestration variables are logged.
  • Initial and Error Values- Both the initial values of orchestration variables and orchestration errors are logged.
  • Error Values- Only orchestration errors are logged.
  • Inline - Orchestration job details are logged for suborchestrations inline with the job details of the calling orchestration.
  • All- The highest level of logging. All orchestration activity is logged.
Log Synchronously Allows the runtime to synchronize the writing of orchestration events to the orchestration monitoring logs as the orchestration is running.

By default, this orchestration setting is disabled and orchestration jobs are not synchronously logged.

Note: When you enable this orchestration setting, the time it takes to process an orchestration job increases.
Max Simultaneous Jobs Allows you to specify the number of orchestration jobs that can run simultaneously.

If you set this property to 1, there will be only 1 job in running state. Any new job coming in will go to the waiting queue for the orchestration and stay there until the running job has completed. This waiting queue is FIFO (First In, First Out) and can hold up to 50 waiting jobs. More than 50 waiting jobs will raise errors.

The waiting queue has no timeout or expiration for waiting jobs, but the jobs in the queue will be deleted if the associated project is stopped.




Feedback | Notices


Timestamp icon Last updated: Thursday, 27 September 2018


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.live.doc/CloudHelp/Managing_Orchestrations/aboutOrchestrationSettings.html