If you already have a working application that uses Classic OpenRules, this page will help you to migrate it to the latest OpenRules Decision Manager.
General Notes. Major changes:
- Contrary to the Classic version, OpenRules Decision Manager has been “mavenized” that essentially simplifies its installation and maintenance. You don’t need Apache Ant anymore but you need to install Apache Maven – see pre-requisites.
- After installing OpenRules Decision Manager by running “openrules.config/install.bat“, you don’t need “openrules.config” anymore as all necessary jar files will be installed by Maven on your machine. So, you may build, deploy, and test your decision project does not mater where it is physically located.
- OpenRules Decision Manager automatically transforms your rules repository into executable Java code, so you don not need access to your Excel-based rules repository in runtime.
- You will be able to easily deploy your decision project on cloud or on premise – see https://openrulesdecisionmanager.com/deploying-decision-services/
- OpenRules Decision Manager includes many new features like Graphical IDE with Rule Debugger, superfast BigTables, and keeping the rules in CSV files, and more.
Migration Example. Let migrate a sample project “Hello” from the Classic version (openrules.models/Hello) to OpenRules Decision Manager (openrules.install/Hello):
|Classic BRMS||Decision Manager|
|DecisionModel.xls includes one Environment table:||DecisionModel.xls includes one Environment table:|
No templates anymore, but additional attributes like model.name, model.goal, model.package
Data types are defined in Glossary
|Batch files: |
– build.bat: Ant-based
– run.bat: Ant-based
– dependencies in openrules.config
– no GUI
|Batch files: |
– build.bat: Maven-based
– test.bat: Maven-based
– pom.xml: with all dependencies
– explore.bat: starts Graphical Explorer