What is needed when executing a decision service by posting a REST request?

Question

Options

• Aruleset library
• Bruleset name
• CXOM JAR file
• DRuleApp JAR file

• A
  89% (49)
• B
  4% (2)
• C
  2% (1)
• D
  5% (3)

Explanation

Executing a decision service via REST requires a ruleset library because it provides the complete path identifier the Rule Execution Server needs to locate and invoke the correct ruleset - it's the unique address of the deployed decision logic, not just a partial name. Option B (ruleset name) is insufficient on its own because a name alone doesn't uniquely identify the full path within the server's deployed artifacts. Option C (XOM JAR) is the eXecution Object Model used during development and deployment to define the object model, but it's already been compiled and deployed server-side before any REST call is made. Option D (RuleApp JAR) is similarly pre-deployed to the Rule Execution Server ahead of time - you reference it via the ruleset path, you don't attach it to the HTTP request. Memory tip: Think of the ruleset library like a library's call number - just as a librarian needs the full call number (not just a title) to pull the exact book, the REST endpoint needs the full ruleset library path to pull the exact decision logic.

No community discussion yet for this question.