First look at JRules 7

Well it’s been a while since I posted but I can blame being busy in the non-blogging side of life, time off, and preparing for the conferences in the fall. I’m not done with that last point, but I think it was time for me to have a look at JRules 7 which came out a couple of weeks ago.

This will be the first post in a series that covers my experience with trying out JRules 7. The topics will include simple differences, Migration process, Decision Validation Service and Rule Solutions for Office.

My first impressions: I like it.

The transition to the IBM world is almost seemless. Some of the new components have interesting capabilities, overall a good upgrade.

Differences when compared to previous version

The install of different components is separate as opposed to the single install previous versions had.

  • Rule Studio and Execution Server
  • Decision Validation Service (DVS) (replaces Rule Scenario manager or RSM)
  • Rule Team Server (RTS)
  • Rule Solutions for Office

The default web server that comes with the install is now Apache-Tomcat (so long JBoss!). I had my reservations initially, but everything is working just fine so far. Actually, I don’t exactly know what IBM/ILOG changed, but the starup time of the web server is a LOT faster in Tomcat than it was in JBoss. In my case the load time of the web server went from 1m48s to 21s, that’s basically 5 times faster.

The JVM that comes with the install is probably the “IBM Development Package for Eclipse”. I say probably because the IBM J2SE envrionment is not available for Windows. (J2RE 1.6.0) So it looks liek they did away with the usual Sun JVM. I suppose that is normal since it is now an IBM product.

Rule Studio leverages Eclipse 3.3.1, and now comes with an xml editor that allows easy edition of xml, xsd files. In previous versions, you had to rely on a third party plugin for Eclipse.

Installation

The install process is pretty straight forward. I personnaly had some issues when launching the ruleflow editor, but it turned out that the cause wasn’t Rule Studio at all, I needed to upgrade my graphics card drivers. No it wasn’t straight forward to figure that one out. Yes I am glad it is over… 🙂

So far, so good. In my next post, I will discuss my experience migrating a project from JRules 6.7.2 to JRules 7.0.

Series NavigationFirst look at JRules 7.0 – Migration of a project >>

Leave a Reply

Your email address will not be published. Required fields are marked *