Application Integration with InRule

The InRule Rules Engine can be integrated into end applications in many different ways.  Typical implementations range from calling the rules engine as a simple calculation engine to driving dynamic surveys incorporating rules and metadata to influence UI display, validation, and navigation.

Application Integration Topics

• InRule Product Architecture
• Rule Execution Process Flow
• irSDK Assembly Information
• Using InRule NuGet Packages
• Configuration Files
• Performance Logging and Monitoring
• irServer^®- Rule Execution Service
• irAdapter for BizTalk Server
• InRule Activity for Windows Workflow
• .NET Assembly State Refresh Options
• InRule Culture Settings
• Interacting with Non .NET Platforms
• Embedded Authoring Control
• Customizing irAuthor with Extensions
• License Activation Utility
• InRule Temp Files
• irSDK for .NET core

Core Runtime Objects used to call the Rules Engine

Refer to the source code example: Basic Example of Calling the Rule Engine to see how to use these objects in code.

RuleSession

• Session object that manages all of the rules engine request directives and execution results

RuleApplicationReference

• Instance of a runtime rule application
• Derived Classes: FileSystemRuleApplicationReference, CatalogRuleApplicationReference, InMemoryRuleApplicationReference

Entity

• Holds data for the rules engine
• State may be saved and loaded as needed