Skip to Content

  

The Product roadmap for SAP NetWeaver Business Rules Management (BRM) is now published. You can download it from here,

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/702315d9-7901-2b10-eaa1-d9e4f5470cac

In this post, I will introduce the new planned product from SAP and also highlight some key messages from the roadmap

 

What is SAP NetWeaver Business Rules Management?

 

SAP NetWeaver Business Rules Management (SAP NetWeaver BRM) is a set of pure java components that will provide rules modeling, management and execution capabilities. It will be packaged as an add-on with SAP NetWeaver Composition Environment. The first release of SAP NW BRM will be available with CE 7.1.1.

 

The major planned components of SAP NetWeaver BRM are in the graphic below

 

SAP NetWeaver BRM - Components

 

Excerpt from the Roadmap that defines these technical sub-components of the BRM technology in CE

 

Rules Composer: The rules composer is the modeling and implementation environment for business rules. This will ship with NetWeaver CE 7.1.1. This functionality will be available in two flavors: from within the SAP NetWeaver Business Process Management (SAP NetWeaver BPM) process composer to model rules in a business process context and as a separate perspective in SAP NetWeaver CE to model rules to be used by non-BPM applications.

 

Rules Engine: The rules engine represents the runtime for rules execution. This will ship with NetWeaver CE 7.1.1 . This release will feature the availability of an inference engine based on the popular RETE algorithm

 

The other components are planned for later releases.


 

Rules Modeling with the Rules Composer

 

You can model rules using the Rules Composer in a separate perspective within the NetWeaver Developer Studio when you expect your rules to have a wider consumption. You can use this method for building reusable rule services or when you want to build rules enabled composites .

The first release will support modeling business rules in the form of Decision Tables, If Then Rules. You will be able to model rules using data models available in the form of XML Schemas, Java Object Models. You can also define your own business model inside the Rules Composer, and map these business terms to your data model later in the life cycle.

 

 

Intgrated Process & Rules Modeling

 

When you are modeling a business process with the process composer, you can model business rules within the context of this business process from the Process Composer perspective in the NetWeaver Developer Studio

 


  

Building Rules-enabled Applications

 

The graphic below captures how business rules deliver value across the application stack.

 


  

Roadmap Highlights

  1. SAP NetWeaver BRM will be available as an add-on in the Composition Environment
  2. SAP’s newest BPM building block, Galaxy , will sport a tight integration of Rules and process modeling resulting in a unified modeling experience
  3. It is planned that BRM will enable the rapid modeling & deployment of rules enabled Composites & business processes
  4. It is planned that BRM will enable even ABAP business applications to take advantage of the flexibility offered by business rules out of the box
To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Vandana Tanawade
    Hello,

    Its good that SAP is coming with BRM functionality as well. Its correct that the externalization of business rules increases the flexibility of the organization. But you have made reference in the roadmap paper to the scattered knowledge and due to multiple implementations of same rule across organization may lead to failure in meeting regulation requirements etc.
    This actually is a governance issue than technology issue. In a typically large organization IT generally is decentralized with each unit catering to their own IT needs. There could even be multiple repositories resulting in duplicate services/rules. Its a trade-off for any organization to control such duplication. There could be central governance or central repository where each decentralized unit can store their services. But to make other units reuse the same service requires a proper governance model. Even if the other units want to reuse a service, but with a minor modification/specialization. This will require them to go through the whole process which can delay their entire schedule.
    Also in such cases there is question of who owns the original service/rule and who will bear the cost of changing the rule.
    Every organization has to come up with their own governance model that suits their specific requirements – business, technical, administrative etc.
    A tool will just ease the execution of this governance model.

    Regards,
    Vandana.

    (0) 

Leave a Reply