Deployment configurations
You can create or edit a deployment configuration in Rule Designer or the Decision Center Business console. In the Business console, only configuration managers can create or edit a deployment configuration. When working within the governance framework, a deployment configuration can be created or edited only within a change activity.
A deployment configuration generates a RuleApp archive that contains rulesets. These rulesets are defined in the decision operations in the decision service. You can select one or more rules by applying either a custom validator or a query. Decision operations are defined in Rule Designer and cannot be changed in Decision Center.
You create deployment configurations for the development, testing, and production environments.
- Configuration type (production or nonproduction): Limits deployment to certain servers.
- RuleApp name: Used by the client application to request a decision.
- Decision operations: Lists the rules to be deployed.
- Target server: Runs the rule applications.
- Version information: Shows the ruleset base version number and versioning policy.
In the Business console, the target server of a deployment configuration determines which user groups can use the configuration. For example, the business user group can deploy a decision service to the development environment if the target server of the deployment configuration is the development server.
For each operation, the deployment configuration contains a base ruleset version number whose role depends on the version policy. In the increment version policy, it defines the minimal version, and in the base version policy, the deployed ruleset version. In the user-defined version policy, it is used to calculate a proposed ruleset version at deployment time.
- Enabled: You can enable execution of a ruleset in a decision service. When you disable a ruleset, this ruleset is not taken into account by the rule engine at execution time.
- Debug: You can enable debug mode on a ruleset in a decision service.
- Trace: You can monitor ruleset execution by generating execution traces.
- Bytecode generation: You can generate the ruleset with Java™ bytecode from the Business console.
Configuration type
You indicate whether a deployment configuration is for a production or nonproduction environment:
- Production
- When a release of a decision service completes its lifecycle in the governance framework, it can be deployed to a production server.
- Nonproduction
- When a release of a decision service is under development in the governance framework, it cannot be deployed to a production server.
Target servers
When deploying from a decision service, you choose the target Rule Execution Server that is defined in the deployment configuration.
The user role and the release state determine the servers to which a user can deploy. For example, if you are working in a change activity, you can deploy to a test environment but not to production. Typically, business users are limited to the development and test environments, while configuration managers can deploy to production.
Rule Execution Server Connections view
A deployment configuration specifies the target server for the deployment. Only a symbolic name for the target server is stored in the deployment configuration. The connection details for the server are defined in the Rule Execution Server Connections view of Rule Designer, which is separate from the deployment configuration.