Overview: Deployment options

You can deploy rules that were developed in Rule Designer to different rule execution environments. There are different ways of deploying a ruleset, and several options to consider.

You package your rulesets into a RuleApp for deployment to the execution environment. To generate RuleApps, you use deployment configurations and decision operations for decision services.

For classic rule projects, you use RuleApp projects. Regardless of how you generate them, the resulting RuleApps are equivalent.

You can also use Ant tasks to deploy and manage RuleApp archives.

You must also deploy the execution object model (XOM) that references the application objects and data against which you run your rules. There are several possibilities:
  • The XOM is based on Java™ classes.
    • You package the Java XOM in the calling Java or web application, if there is one.
    • If there is no calling Java or web application, you can use a managed Java XOM with your RuleApps.

      This is typically the case when you use Decision Validation Services (DVS) or Hosted Trasparent Decision Services (HTDS).

  • The XOM is based on an XML schema (.xsd file). In this case, the XML schema is packaged into the ruleset archive and deployed with the RuleApp.