Deploying from Decision Center

You can deploy any branch (release, change activity, or regular branch) of a decision service from the Decision Center Business console.

All the information required for deployment is contained in a deployment configuration. Deployment configurations can be synchronized with Rule Designer.

Only a configuration manager can create, edit, or delete deployment configurations in the Business console. This ensures a basic level of security on deployment. Deployment configurations contain information that includes the target servers, the decision operations that define the business rules, and settings for versioning of rulesets and RuleApps. The following aspects of a deployment configuration relate to making sure that deployment is secure:
  • The configuration type as Production or Nonproduction.
  • The target server where this deployment configuration can deploy to.
  • User groups that can deploy with the configuration depend on the selected server.
Any user who can access a decision service in the Business console can deploy its branches (release, change activity, or regular branch) from any deployment configuration available to that user in that branch. The deployment configurations that are available for a given user depend on this user's role (see Deploying rule applications). The following conditions apply:
  • In a change activity, you can deploy only with a deployment configuration whose type is Nonproduction.
  • In a release, you can deploy with a deployment configuration whose type is Production only if the release is completed.

When you deploy a decision service, the XOM is also deployed if the version of the XOM is not already present in the target Rule Execution Server.

When working within the governance framework, a deployment configuration can only be created or edited within a change activity.

Deployment snapshots can be found in the list of snapshots. You can then redeploy from the deployment snapshot or from the report of the deployment.

Note: You can also automate rule deployment by using the Decision Center REST API.