The document provides an overview of the key features and benefits of a Business Rules Management System (BRMS). It discusses what a BRMS is, its main components like Guvnor, assets, rules, processes, and how it can be used with Eclipse. A BRMS provides a centralized repository for business logic, enables separation of logic and data, and allows non-technical users to define rules through a graphical interface.

1. All the cool stuff of JBoss BRMS Giovanni Marigi JBoss Consultant Red Hat, Inc. January 2012 String.class.getName()

3. BRMS - Guvnor

4. BRMS Assets package facts working sets rules decision tables test scenarios other assets

5. JBPM5 processes

6. BRMS authoring

7. Eclipse integration

8. Rule agents

12. The assets define a knowledge base

13. Business logic is made by several assets: facts (domain model) rules (of course) business processes (workflows) decision tables functions more...

14. Not only business rules!

16. Version control of business assets

17. IDE/User tools to define and to “governance” the decision logic

18. Build, deploy, testing of decision logic

19. Packages of business assets

20. Categorization of business assets

21. Roundtrip, integration with dev Tools (Eclipse)

22. JCR repository (jackrabbit or modeshape) for assets

23. BRMS can be configured for high availabilty

25. Cross domain logic

26. Reuse, logic opened to changes

27. Easy to maintain the business logic

28. Changes in live systems

29. Several stakeholders can contribute in defining the business logic (Business Analyst, Rule expert, Developer, Administrators)

31. Drools Guvnor 5.3.0 last stable

32. Drools Guvnor 5.3.0 includes: Expert 5.3 (rule engine) Fusion 5.3 (CEP) Flow/JBPM5

34. BRMS 5.2 includes: - Drools Guvnor 5.2 - Drools Expert 5.2 - Drools Fusion 5.2

35. BRMS 5.3 (next release) will be based on Guvnor 5.3

36. JBoss Developer Studio

37. Bug fixing,patching SLA Enterprise certification | QA

40. fact model != domain model a fact model typically overlaps a domain model but better to make it decouple from the domain model

41. Rules and assets reason upon a fact model

42. Two ways to do define your fact model: - upload a JAR file containing Java Classes - declare a model within Guvnor

44. Use them to put constraints on a group of facts and restrict the “reasoning domain” of your business rules

45. Disabled by default

47. Don't use a BRMS if you don't have business rules

48. Don't use a BRMS if you don't want or you can't separate logic from data

49. Rules are processed and evaluated by a Rule Engine (Drools Expert)

50. Forward chaining rule engine which implements the RETE algorithm (ReteOO)

51. Rich native language to define rules

52. A rule is contained in a DRL file

53. More info on Drools Expert: Jbug Italy slideshare site: http://www.slideshare.net/jbugrome

60. A spreadsheet can be imported or created via the guided web editor

61. A wizard generator for spreadsheet is available in BRMS!

62. A decision table at runtime is transformed in a series of DRL rules

64. A scenario is made by a given section (list of facts and its initial state) and an expect section

65. What we can “assert” in a expect section? - Rule Validate that a certain rule fired. - Fact value Validate fact values for a fact created in the Given section. -Any fact that matches Validate that there is at least one fact in the knowledge base with the specified field values.

68. JBPM5 is based on Drools Flow

69. Workflow guided by rules

70. Rule workflow is the new “generation” of business workflow

71. Rules + workflow: dynamic processes

73. No legacy xml to define the workflow but a standard!

74. Human task (human interaction with a flow) The task service implementation is based on the WS-HumanTask (WS-HT) specification

75. Rule Task: use drools rules inside the flow

76. Pluggable Service Task (work items): nodes with custom logic (e.g. DBControl, EJBControl, EmailControl)

77. Gateway (split,converge) the decision in agateway can be taken by a drools rule!

78. Events (start,end,intermediate)

79. Timers

81. BPMN2 editor in BRMS (web editor)

82. BRMS can upload BPMN2 processes designed with other BPMN2 modeling tool

83. Online repository to download ready to use service tasks JBPM Service repository

84. JBPM 3 to 5 migration tool https://github.com/droolsjbpm/jbpmmigration

88. DSL functions Define rules in a domain specific language

89. Enumeration Enum data to be used in rules

90. Functions

91. Rule templates

93. Assets anyway can't be branched or tagged!

94. An asset contains meta data information

95. Assets can be categorized

96. An asset can be linked to many categories

97. Categories don't have any meaning at runtime; useful to order the assets

98. An asset can have a status (e.g “Draft”, “Completed”); it's a sort of label

100. Creating a snapshot means that the BRMS package is ready to be used from external application

101. Before taking a snapshot a build package is required

102. With a build every assets inside the package is validated

103. Status and Categories can be used to select only specific assets to include inside a snapshot (Use selector) (e.g. create a snaposhot only with assets belonging to category “Fraud” and with Status “Completed”)

104. A snapshot will be published inside the repository and accessible via a URL

107. Assets can be edited in Eclipse and committed to BRMS (complete roundtrip)

108. Eclipse gives the capability to compare different version of the same asset

109. Requires JBoss Developer Studio 4.x or Eclipse 3.6.x + JBoss Tools

110. File --> Import --> Guvnor --> Resources from Guvnor

113. Create a Drools RuleAgent able to get (download) its KnowledgeBase from BRMS

114. Define a change-set.xml (simple xml file) file where the BRMS packages are listed

115. The KnowledgeBase is the entry point to fire rules, execute bpmn processes,...

120. http://www.jboss.org/jbpm/lists

121. IRC server: irc.codehaus.org

122. Channels: #drools #guvnor #jbpm THAT'S ALL FOLKS!

123. All the cool stuff of JBoss BRMS THANKS! [email_address]