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:
- HTTP Request Member Definitions
- Overriding RuleApp Endpoints at Runtime
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.
Please sign in to leave a comment.