ILOG jrules rule Set application and client integration

This paper first introduces the main parts and characteristics of the ILOG JRules V7.0 architecture to be applied in the example. Secondly, the design and implementation of a business rule set application development and integration scenario for example, detailed the application of business rules development, deployment and client calls to its process. This paper focuses on the Java design of the Execution object Model (XOM) in the rule application and the benefits that this approach brings to the writing and execution of the rules, and at the end gives a deployment based on the Web service invocation method to the rule Execution Server The integration scheme and implementation process of rule set and client in environment.

Brief introduction

Typically, if the business strategy of the enterprise is implemented in the application, as the business grows and the policy changes, the implementation becomes increasingly complex and lacks flexibility to react quickly. The advent of the Business Rules Management System (Business Rule Management System, BRMS) provides a more effective solution to the management of business policies for both the developers and business users of the application. Applying business rule management systems, developers and architects can manage business logic independently of application logic, allowing business users to manage business policies independently of the enterprise's IT department. At the same time, the advent of an IT architecture such as SOA enables business logic to be encapsulated in the business rule management system as a rule service for provisioning programs and business process calls. IBM ILOG JRules is a good business rule management system that allows business people and it developers to improve business and automate business policies.

In the process of invoking a rule set, you can invoke POJO, EJB, JMS, Web services, and so on, according to XOM and design requirements. In this paper, a method of invocation implementation based on WEB service is proposed, and in the guide document of ILOG JRules V7.0, a calling method of deploying rule set to decision service with Jax-ws 2.1.1 is introduced, for example, see Guide Integrating into a enterprise application part. The scheme presented in this article selects Axis to create a WEB service that invokes the rule set, which is efficient, responsive, easy to program, flexible, and meets the architectural requirements of SOA.

The main parts and characteristics of ILOG JRules architecture are applied in this paper

ILOG JRules V7.0 creates, manages, and deploys business rules through a set of innovative modules to achieve improved performance.

ILOG JRules Rule Studio: Integrated development Environment (IDE) for rules applications. Rule Studio directly targets the IDE's eclipse family, including the Eclipse IDE. Rule Studio supports ruleset debugging and deployment of the ILOG JRules rules Execution Server, as well as collaboration between the authors of business rules through rule team Server.

ILOG JRules Execution Server: A stable, j2se, and Java-EE-compliant, manageable rule execution environment that runs on a WEB server or application server. It packs the rule engine as a Java Connector architecture (J2C) resource adapter. The rule Execution Server includes a WEB management console that enables effective versioning and management of the set of rules that are deployed above. The rule Execution Server is fully integrated with rules Studio and governing Team server, and can support both developer and policy managers in the business discipline deployment.

Has the following characteristics:

Good ease of use:

Work in an environment integrated with Eclipse, using automatic corrections and "smart rules" to quickly and easily write rules in a language consistent with natural language rules;

Use static rule analysis to detect conflicts and redundancy;

The creation of regular flow can be visualized assembly and split, and meet the design of granularity requirements;

The application of business rules can be quickly deployed and debugged independently of the applied logic.

Easy to manage:

Maintain application integrity while providing control to business people through role-based rule access;

Through testing, common debugging and reconstruction for repeated development;

Use a single interface and rule library to manage code and rules;

At the same time, several release cycles should be prepared, while the next product release will be maintained while maintaining the ongoing release of the product;

Controllability:

Reporting and monitoring the rules through controlled execution processes;

View a complete history of all rule changes and deployments;

Business Rules Application Scenario Description

In industry solutions such as insurance or finance, the employee's salary calculation or employee's promotion demotion will be handled according to the employee's

Various indicators and enterprise management regulations to carry out the corresponding calculation and processing, this process involves a large number of business policies or rules. This article will be based on the staff pay calculation function of the business rules of application development and integration scenarios for example, different rules determine

Different salary calculation methods, but because of the actual demand, these rules are flexible, so, the rules of salary calculation extracted and applied ILOG JRules so that without affecting the performance of application code on the premise of independent rapid development, debugging, deployment and management, and a Web The way a service is invoked is an excellent solution for integrating it with any client.