Deploying rule applications
You use deployment configurations in decision services to deploy RuleApps. The deployment configurations apply decision operations that specify the rules to include in the rulesets of RuleApps. They also specify target execution servers, and the version policies for RuleApps and rulesets.
You also deploy the execution object model (XOM) that references the application objects and data on which you run your rules. You create and maintain the XOM in Rule Designer, and publish the XOM binary to Decision Center. You must keep the XOM synchronized in the components to ensure that the deployed RuleApps reference the correct XOM.
The following table summarizes the deployment tasks by user role:
| User role | Deployment tasks |
|---|---|
| Rule developer | Creates a decision service in Rule Designer and adds deployment configurations. Deploys a RuleApp for the decision service from Rule Designer or Decision Center to verify and troubleshoot the deployment process. Publishes the decision service, its deployment configurations, and the XOM to Decision Center. |
| Configuration manager | Deploys RuleApps for decision services to the development, test, and production execution servers. Can create deployment configurations in the Decision Center Business console. |
| Business user | To validate a decision service, deploys RuleApps from Decision Center to the development and test execution servers. |
| Integrator | Deploys RuleApps to the development and test execution servers. |