A description of the ODM Rules SDK, a set of APIs and components to embedd business rules authoring and execution functionality inside custom applications.
This document discusses business rule management and when a Business Rule Management System (BRMS) is needed. It defines business rules as statements that define how a business runs, such as compliance rules, validation rules, and calculations. A BRMS is described as a set of tools and processes that facilitate communicating, deploying, and executing business policies within an IT system. It allows business rules to be managed as enterprise assets and enables a rich development lifecycle for business policies. Key components of a BRMS include a rule engine, rule editors, and processes for managing the development and deployment of rules.
IBM zUniversity 2004 : ILOG JRules on IBM eServer zSeriesDan Selman
This document discusses ILOG JRules certification on IBM eServer zSeries mainframe systems. It provides an overview of ILOG and its business rule management software. Key points include that ILOG JRules was certified to run on IBM zSeries systems running z/OS and z/Linux, as well as with WebSphere Application Server. The certification testing validated the rule engine's functionality when deployed to a WebSphere cluster and invoked via Java and XML.
WebSphere Technical Conference 2009 : Enhancing your BPM Solution with ILOG J...Dan Selman
This document discusses integrating business rules with BPM solutions using IBM's ILOG BRMS. It provides an overview of ILOG's product lines including the BRMS and its components. Reasons for combining BPM and BRMS include externalizing business decisions and separating process and rule lifecycles. Guidelines are given for when to use BPM rules versus BRMS based on factors like rule importance and change frequency. The document compares BPM rules and BRMS and provides best practices for integrating the two including developing rules and processes separately and organizing rules into decision services.
Paris Java User Group : Enabling Agile Business and IT CollaborationDan Selman
The document discusses the need for systems to be designed to enable change. It notes that many aspects of a system can change, including code, configuration, data, models and more. The presenter advocates designing systems with change in mind using a change-oriented architecture. Specifically, the document recommends externalizing data and policies from code, creating reusable services, and using a business rules management system to help govern and implement changes in a controlled manner. It acknowledges that no single technology can address all change-related challenges but that a BRMS can assist with many aspects of managing changes.
A Model-Based Approach for Extracting Business Rules out of Legacy Informatio...Valerio Cosentino
The document summarizes Valerio Cosentino's PhD thesis defense on extracting business rules from legacy information systems. It outlines his business rule extraction framework, which identifies business terms and rules in source code like COBOL and Java, as well as relational databases. The framework represents extracted rules using text, graphs, and a vocabulary to link rules to their implementations in a traceable way for both technical and business users. It was evaluated on an IBM COBOL application where extracted rules were verified by IBM experts.