Drools vs. OpenLM for Engineering Licensing

As an open source rule engine and product suite, Drools is well suited for the small and middle scale business to manage and integrate the rules to build the rule-driven system which can process the business-critical data and events to produce the automated decision. It is better to use Drools in the well-secured environment (back-end behind the DMZ), not putting it on the customer-facing front or exposing it directly the to public where may bring direct security risk in the enterprise environment. Drools still needs a lot hardening on the security side.

Incentivized

OpenLM can simplify the reporting of complex licenses with multiple toolboxes or products on one server. It covers most of our license server types, but not all. The academic version is reasonably priced (e.g. for educational institutions) giving 90% of the features, however setting it up on-premise was more complex than our original pilot would suggest. We couldn't do without it now.

• Writing rules with business focus
• Rules evolution and maintenance
• separate business logic from program code

Incentivized

• Peak concurrent license use for any period of time, often less than expected, saves unnecessary over purchase.
• Denials of license, can quickly see where a license is not working, say, after an upgrade.
• Comparison of license utilisation (% when near the limit).
• Quick check of expiring licenses.

• Fusion doesn't support persistence of working memory, which brings some extra high availability risk to our business.
• Guvnor still has a lot room to be implemented, it is not so user-friendly for non-technical people, so a lot of business users complain it is hard to master.
• Rule execution server doesn't even have JMX implemented, hard to be monitored.
• Drools is still lacking support for key Web services standards.

Incentivized

• You can share a link to a dynamic report (e.g. the last 365 days). The URL is very long but it can be used with a 3rd party short URL utility and shared with users.
• Upgrading to the latest version took a long time to troubleshoot, which left a short gap in the saved data.

I did not participate in drools choice. I can only compare drools with the previous situation which was using nothing.

Incentivized

X-Formation, OpenIT, JTB, Sassafras either more expensive for the particular task of managing and monitoring concurrent licenses, or they had a different set of features (such as Sassafras K2/Keyserver also for remote access)

• The IT department quickly adopted Drools as it is a very good java-based rule engine, which saves a lot of time to meet the project timeline and balanced our business requirements.
• Recently we start considering the OpenRules, which may be more business user-friendly.

Incentivized

• The academic version has paid for itself handsomely, including our setup costs. The ongoing strategic information saves costs.