Most promising rule engine BRFplus

[Former Member]

I attended BRFplus session in SAP DKOM 2012 Bangalore. Joydeep Paul from BRFplus Team talked about ongoing development and it was amazing.

He started with the concept of managing Business rules using BRFplus and then the upcoming stuffs which I want to share with you.

+ Decision Service Manager- This will be very useful to those customer's who are running on NW 6.4 or higher and want to make use of latest version BRFplus say NW 7.31 SP4 or higher without investing time and man force on upgrades.

How? - You need to connect the Target System where you want to deploy the rules while creating an application in the Source System. Once you are finished with the rule design, deploy it into the Target System; so that you can use it at run time without any performance issue. In future, if business users modify the rules then he/she need to deploy them again into the Target System.

Source System- NW 7.31 SP4 or Higher & Target System- NW 6.4 or Higher

+ BRFplus Powered by HANA- This demo explained how BRFplus will be using the power of HANA; and the best part is you don't need to be a HANA expert to execute rules. BRFplus internally takes care of everything to generate Call Procedure SQL scripts; which is required to process rules on HANA and this is where BRFplus and SAP NetWeaver BRM (Java based Rule Engine) have differences in their solution.

From my knowledge, you need to be a HANA studio expert to design rules in SAP NetWeaver BRM.

+ Microsoft Silverlight UI- If you are tired of using Web Dynpro UI elements and looking out for more flexibility to design rules, here is your catch.

BRFplus is going to leverage Microsoft Silverlight technology that provides a rich user experience for a business user to design and model business rules by just drag and drop; with most appealing graphical and highly responsive controls with nice visual effect like animation, zooming etc.

+ Cloud- Quite more interesting is that BRFplus is stepping into the Cloud space too, but it wasn't in detail.