Visual Rules can be integrated into a broad range of architectures and ensures greater transparency across the entire span of your business processes. It supports different execution scenarios: from integration directly into a Java application through mass data processing to deploying rules as web services in a service-oriented infrastructure.
Any rule models deployed to Visual Rules Execution Platform automatically become available as standard web services.
These services can be consumed by a wide variety of clients, not limited to Java architectures but also available to heterogeneous IT landscapes or legacy systems. It supports SOA integration standards and different version control options, which facilitate reliable rule management even in very complex scenarios.
The necessary WSDL and XML schema files are automatically generated and contain a detailed rule interface description that enables easy integration with any web service client. Visual Rules Execution Platform also provides generic service interfaces for scenarios where loosely coupled binding is desired. These rule services provide excellent integration into .NET applications and tools.
Compliance regulations often require enterprises to be able to fully explain any decision they made. When was something decided? Based on which data? Using which rules? Execution Platform automatically produces rule execution traces and keeps a history in its database.
Rule execution with Execution Platform is extremely fast. Any number of simultaneous threads can execute the same rule logic without affecting each other. The sequential and stateless execution mode of the rule engine provides optimal linear scalability. Execution Platform can be deployed into standard Java EE application server clusters and automatically makes full use of all cluster members.
Dynamic loading of rule code and automatic unloading of unused rule versions ensure a small memory footprint, even with thousands of individual rule models (and versions thereof) deployed simultaneously.
The Java code generated by Visual Rules from the rule models can be directly integrated into your own Java applications, e.g. to be executed on mobile devices as well as in time-critical client/server applications.
To package the Java code, Visual Rules supports so called rule artifacts (JAR files) containing the rule code as byte code, the rule model as an EMF model and information on rule dependencies (including rule versions). These artifacts and runtime libraries can be imported via the class path into Java applications like any other Java library.
Calling rules from within applications is done directly within the source code of the application. Visual Rules provides an API to integrate and call generated rule code, as well as defining the input parameters for the rules, resetting statistics, and retrieving result sets and action calls.
Other APIs for hot deployment and monitoring allow particular rule versions to be loaded and changed, as well as analyzing runtime statistics.
With Visual Rules Batch Platform, the business logic created for interactive software applications is also used for the non-interactive processing of mass data. In both scenarios, the required program code is generated from the same rule model. This reuse of business rules saves time and effort when creating batch jobs and ensures the consistency of the processing logic and the quality of the processing results. The batch applications satisfy the highest requirements in relation to performance and processing large volumes of data.
Visual Rules allows you to record execution statistics during runtime and to monitor and trace how rules are executed.
In the graphical model, runtime statistics display the rules processed per request along with the processing time. This allows you to monitor all execution details while the system is running. The evaluation of log files and incremental rule execution supply further information,