Accessing via REST

irServer Rule Execution Service supports use of standard HTTP verbs to execute rules in addition to the existing SOAP Endpoint support.

The irServer Rule Execution Service uses content negotiation to determine the request and response types. Note: If not specified, both the request and response types will default to XML.

• Request Examples
  • Content-Type: application/xml
  • Content-Type: application/json
• Response Examples
  • Accept: application/xml
  • Accept: application/json

The following topics and samples are provided for assistance with the use of the REST Endpoint:

• 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

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