irServer - High Performance Business Rule Engine

irServer is the central nervous system of InRule. It provides services for the following functions:  

Catalog Management State Management Performance Monitoring Database Access

Run-time execution Message Queue Interaction Email & Alert Messaging

Variable Rule Execution Fire Modes Depending on your needs, you may want to specify the order for the firing of rules and rule sets. InRule supports three execution modes where you can tell the engine to fire rules in the manner it deems the most appropriate or to fire rules in the order you specify.

Rule Execution Modes

Available as a Web Service

InRule provides the option of implementing a service-based component of the rule engine, called the rule service. The rule service utilizes the rules catalog and externalizes critical business functions to consuming applications. It can be invoked via a Web Service call or via a message queue where rule sets and application data can be cached for high-performance scenarios.

The SDK's rule engine connection object allows applications to seamlessly choose the connection option they prefer (e.g. asynchronous/synchronous message queue or Web Service). The service can be implemented in a fault-tolerant, scalable architecture utilizing network load-balancing techniques. In a given environment, multiple rule engine services can be run in parallel to increase throughput and performance of the calling applications.

Highly-optimized XML Document Object Model (DOM)

One of the most expensive processes for service-based processing is the time it takes to serialize and deserialize an XML document during inter-process communication. For this reason, InRule utilizes a highly efficient XML DOM to load a transaction into the rule engine for processing. Depending on the XML document, InRule's proprietary XML DOM is in some cases 10 times faster than traditional DOMs such as MS XML for updating and retrieving values.

irServer - Flexible Catalog Management

The catalog service provides the ability where users can manage accounts, security access, versions, and the check-in/check-out of rule applications. As rule applications are checked-out, modified, and checked-in, new versions are created and managed.

Subsequently, at run-time using the SDK's rule engine connection, applications can choose to pull rule applications from the catalog by latest "published" version, by label, or by specific version number for execution. If a rollback is required, the administrator can specify the correct "published" version to use. Catalog access can be set up to authenticate against multiple authentication stores including Active Directory, LDAP-compliant server, or a database table. The catalog is accessible as a web service.

Compatible with SQL Server and Oracle

The rules catalog may reside on either Microsoft SQL Server or Oracle database platforms. Each platform has the full set of repository security and source management functionality available to it.

Programmatic Access via irSDK

Full programmatic access to repository Items provides the users with the ability to manage accounts, security access, versions, and the check-in/check-out of rule applications. As rule applications are checked-out, modified, and checked-in, new versions are created and managed.

Supports Enterprise Authentication Models

The InRule Catalog Service can be setup to authenticate against 3rd party authentication providers including LDAP-compliant directory services such as Active Directory, built-in database providers, or a custom provider.