irServer - Rule Execution Service

.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 SOAP

• Adding a Service Reference in Visual Studio
• Calling irServer SOAP endpoint using a Service Reference
• Executing a Decision on irServer SOAP endpoint using a Service Reference
• Configuring irServer SOAP Endpoint to support WsHttpBinding
• Handling irServer SOAP Endpoint Error Conditions
• Caching Behavior 

Accessing the Rule Execution Service via REST

• • Methods
  • Apply Rules Sample Request and Response Formats
  • Execute Decision Sample Request and Response Formats
  • Execute Independent RuleSet Sample Request and Response Formats
  • Execute RuleSet Sample Request and Response Formats

HTTP Request Member Definitions

• RuleApp
  • RepositoryRuleAppRevisionSpec
• RuleEngineServiceOptions
• RuleEngineServiceOutputTypes

Overriding RuleApp Endpoints at Runtime

• Database Connection String
• Mail Server Connection
• Web Service Address
• Web Service WSDL Uri
• XML Document Path
• XML Schema
• XML Schema Validation
• Inline Table
• Inline XML Document
• Inline Value List
• SQL Query
• REST Service X.509 Certificate Path
• REST Service Authentication Type
• REST Service Root Url