Deployment configurations

You use deployment configuration in a decision service branch (release, change activity, or regular branch) to deploy sets of rules.

Each deployment configuration contains all the information required to deploy rulesets, including the target server. When working within the decision governance framework, creating and editing a deployment configuration must be done within an open change activity.

A deployment configuration is organized in five sections:

General

Contains the name and description of the deployment configuration, and indicates the project in which it is stored. Also contains the name and the base version number of the deployed RuleApp. Also contains properties for the RuleApp.

You set the configuration type to Nonproduction or Production. Typically, a nonproduction configuration is used in developing and testing a decision service. A production configuration is used to deploy a finished release to a production environment.

Operations

Lists the decision operations that are available in the decision service, and those selected for deployment.

With an initial deployment, you typically deploy the available decision operations. In updates, you might limit deployment to specific decision operations. Make sure that every ruleset name in the deployment configuration is unique.

Targets

Lists the Rule Execution Server instances that are available in Decision Center, and those selectable when deploying. The deployment process packages the rulesets in the decision service into a RuleApp archive that is sent to each selected server.

If no servers are available, you can still use the deployment configuration to create a RuleApp archive that can be saved locally.

Ruleset Properties

Contains the base version number to be used in the ruleset path. You also set the version policy for calculating the version numbers that are used on successive deployments.

You use the Advanced properties section to configure individual rulesets. You select a ruleset and choose options for enabling, debugging, and tracing the ruleset. You can also select and define properties that control in detail how the ruleset runs in Rule Execution Server.

Groups: You select which user groups can see this deployment configuration.