XOM deployment with decision services

A RuleApp that you deploy must reference the correct XOM.

When you deploy a decision service, Rule Designer goes through the following process:

  1. Builds the XOM binary from the source files that are referenced by the decision service.
  2. Deploys the XOM if it is not already present in Rule Execution Server, and retrieves the XOM URI.
  3. Copies this URI to each ruleset that is contained in the RuleApp. Specifically, Rule Designer copies the URI to a property of the ruleset called ruleset.managedxom.uris.

With this mechanism, each ruleset in Rule Execution Server references the correct XOM.

Note: If the XOM is based on an XML schema (.xsd file), the XML schema is packaged into the ruleset archive and deployed with the RuleApp.

XOM deployment in Decision Center

When Rule Designer builds the XOM from the source files, it places the XOM binary under resources/xom-libraries. The XOM binary is then published to Decision Center with the rest of the decision service.

With the XOM binary file synchronized between Rule Designer and Decision Center, RuleApps deployed from either environment reference the correct XOM.

XOM modifications

You modify the XOM source files in Rule Designer. Rule Designer always builds the XOM binary from the source files. You can then publish the XOM to Decision Center.

If you import a decision service from Decision Center into an empty workspace:
  • You do not obtain the XOM source files. You must obtain these source files in the usual way, for example through source code control.
  • The XOM binary obtained from Decision Center is copied to the resources/xom-libraries folder. The files in this folder should not be used in the XOM path.