Ruleset path format

The paths parameter should be specified in the ruleset path format. It can be a canonical ruleset path in the form of /ruleApp/ruleSet.

When a canonical ruleset path is used, all the latest RuleApp and ruleset versions are run. However, if a request is made that uses a specific RuleApp or ruleset version, it does not use the dedicated runtime pods, but instead uses the default runtime pod.

Consider the following configurations:

Example 1:

decisionServerRuntime:
  dedicated:
    - name: miniloan
      paths:
        - /miniloan/production
In this setup:
  • A request to /miniloan/production is handled by the dedicated miniloan pod.
  • A request to /miniloan/2.0/production is directed to the default Decision Server Runtime because it specifies a version (2.0).

Example 2:

decisionServerRuntime:
  dedicated:
    - name: miniloan-specific
      paths:
        - /miniloan/4.0/loan
In this configuration:
  • Only requests that contain /miniloan/4.0/loan in their URL are executed in the dedicated miniloan-specific runtime.
  • Any other requests, including those with different versions or paths (for example, /miniloan/3.0/loan or /miniloan/loan), are handled by the default Decision Server Runtime service.
For more information about the format of a ruleset path, see REST resources.