Skip to main content



irServer - Rule Execution Service

note

Although this article is specific to the legacy irServer - Rule Execution Service, it has been retired as of the release of InRule 5.9.0. This article still applies to its upgraded replacement Decision Services - Rule Execution API and can still be used for reference. The primary difference to be aware of is that only the JSON content type examples are relevant to the new Rule Execution API as XML is no longer supported.

.NET applications or third-party software products (e.g. BPM products) can call the Rules Engine via the Rule Execution Service without needing to reference irSDK.

The Rule Execution Service currently supports the REST and SOAP protocols.

See also InRule Runtime Service Config File Settings section for information on storing irCatalog credentials for use by irServer's REST endpoint, and configuring Endpoint Overrides in the config file.

The following topics are provided for assistance with the setup, configuration, and use of the Rule Execution Service:

Accessing the Rule Execution Service via REST

HTTP Request Member Definitions

Overriding RuleApp Endpoints at Runtime

Accessing the Rule Execution Service via SOAP