A look into the crystal ball at JBoss BRMS and BPM Suite
•Transferir como ODP, PDF•
3 gostaram•2,464 visualizações
There is nothing like previewing the future of Business Rules and Business Process tooling. Be among the first one to leave footprints in the fresh snow as we take you on a tour of the JBoss Business Rules Management System (BRMS) and JBoss Business Process Management Suite (BPM Suite). Attendees will be provided with the background architectures, a live demo of their capabilities, and a look at how they are Cloud enabled by the OpenShift cloud service. Join us for an hour of rules, processes, cloud, and crystal ball gazing!
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a A look into the crystal ball at JBoss BRMS and BPM Suite
Semelhante a A look into the crystal ball at JBoss BRMS and BPM Suite (20)
Mais de Eric D. Schabell
Mais de Eric D. Schabell (20)
Último
Último (20)
A look into the crystal ball at JBoss BRMS and BPM Suite
- 1. A look into the crystal ball at JBoss BRMS & BPM Suite 1 Eric D. Schabell JBoss Technology Evangelist JBoss Developer Day London
- 2. Why BRMS & BPM Suite? Under the covers Demo(s) 2
- 4. Business Rules - Example INSURANCE COMPANY Insurance Claim 4
- 5. Example INSURANCE COMPANY Problems: 1. Business rules are hidden in applications – the visibility problem Insurance Claim 5
- 6. Example INSURANCE COMPANY Problems: 1. Business rules are hidden in applications – the visibility problem Insurance Claim 6 2. It takes too long to change business rules – the agility problem
- 7. Business Rules - Example INSURANCE COMPANY Problems: 1. Business rules are hidden in applications – the visibility problem Insurance Claim 2. It takes too long to change business rules – the agility problem 3. People interpret rules differently – the consistency problem 7
- 8. Business Rules - Solution Rule Repository 8 1. Separate the business rules from the applications
- 9. Business Rules - Solution AHA! Rule Repository 1. Separate the business rules from the applications 2. Express rules in terms that the business can readily understand – visibility 9
- 10. Business Rules - Solution AHA! Rule Repository 1. Separate the business rules from the applications 2. Express rules in terms that the business can readily understand – visibility 3. Empower business and IT experts to collaborate – agility 10
- 11. Business Rules - Solution AHA! Rule Repository 1. Separate the business rules from the applications 2. Express rules in terms that the business can readily understand – visibility 3. Empower business and IT experts to collaborate – agility 4. Automate the rules consistency 11
- 13. A Business Process An activity or set of activities that will accomplish a specific organizational goal... Problems: • Inefficient manual processes • Lack of consistency Shipping Catalog Financials • Lack of visibility • Lack of agility • Error prone Inventory Orders 13 Packaged Apps (e.g. SAP)
- 14. BPM - Solution Catalog Shipping 1. Automate interactions with LoB Systems... 2. Drive the business process from a model... 14 Packaged Apps
- 15. BPM - Solution Catalog Shipping Packaged Apps 1. Automate interactions with LoB Systems... 2. Drive the business process from a model... 3. Manage user participation... 15 4. Provide visibility into process execution data
- 16. JBoss BRMS & BPM Suite
- 17. New Products for 2014 Combining the strengths of Polymita and JBoss BRMS JBoss BPM Suite 6.0 Polymita BPMS JBoss BRMS 6.0 JBoss BRMS 5.3 17 JBoss BRMS 6.0
- 18. New Products for 2014 Combining the strengths of Polymita and JBoss BRMS Rules Process Events JBoss BPM Suite 6.0 Polymita BPMS JBoss BRMS 6.0 JBoss BRMS 5.3 Rules 18 Process Events JBoss BRMS 6.0 Rules Events
- 19. 19
- 20. Components Real-time data & event feeds Authoring tools for business users Repository Business analysts Event processor Business rule definitions Rules engine Authoring tools for developers Developers 20 Business data Client applications
- 21. New in 6.0 Real-time data & event feeds Authoring tools for business users Repository Business analysts Event processor UberFire Business rule definitions Client applications Rules engine Authoring tools for developers Drools 6.0 Developers 21 Technology Preview Business data
- 22. 22
- 23. Components Business events Authoring tools for business analysts Enterprise Applications Repository Business analysts Event Processor Business Process Manager Business Rule Definitions Web Services Rule Engine Java Business data Business users Authoring tools for developers Developers BAM Business users 23
- 24. New in 6.0 Business Events Authoring Tools for Business Users Enterprise Applications Repository Business Analysts Event Processor Business Process Manager Business Logic Definitions Data Modeler Forms Designer Web Services jBPM 6.0 Rule Engine Java Business Data Business Users Authoring Tools for Developers Developers Business Central Business Operations/ Analysts 24 BAM Dashboards & Reporting
- 25. Demo BPM Suite Mortgage Demo BPM Generic Loan Demo
- 26. Why BRMS & BPM Suite? Under the covers Demo(s) 26
- 27. ` JBoss BRMS & BPM Suite Articles: http://schabell.org/search/label/BRMS http://schabell.org/search/label/BPMS JBoss BPM Suite Demos: http://www.schabell.org/2013/11/jboss-bpm-suite-automated-lending-generic-loan-demo.html https://github.com/eschabell/business-resource-optimizer-demo http://www.schabell.org/2013/10/jboss-bpm-suite-rocking-the-mortgage-demo.html https://github.com/eschabell/bpms-customer-evaluation-demo (migration from BRMS 5.3) JBoss xPaaS Demos: 27 https://github.com/eschabell/bpms-bam-dashboard https://github.com/eschabell/openshift-bpm-bam-dashboard
Notas do Editor
- <number>
- We will start with a discussion of how the BRMS comes to be. We will breeze over the background of BPM, discuss how the project jBPM releases are incorporated into the BRMS product. From there we will examine the interesting points as they apply to a business user, followed by the more technical elements of BRMS that will be of interest to developers. Finally we will summarize in an overview the new BPM components that come from the jBPM project. We will also mention the components that will NOT be included into the BRMS 5.3 product that are in the jBPM project. These are up and coming features that have yet to mature enough for inclusion at this time, but you can expect to appear in future versions of BRMS.
- <number> How does it get approved or deny?
- <number> business problems brms is designed to resolve RULES IN APPS DIFFICULT TO UNDERSTAND TO THE BUSINESS USER – NOT PROPERLY DOCUMENTED
- <number> CHANGES (REGULATIONS, NEW PRODUCTS) = WEEKS TO CHANGE SPEED PARAMOUNT IMPORTANCE IF RULES WERE EXPLICIT AND ACESSIBLE… LESS RELIANCE ON I.T. FASTER TO CHANGE
- <number> MANUAL INTERPRETATION OF RULES = SAME CLAIM x <> PERSON = <> RESULT (OK or NOK) = PROBLEM !!
- <number> SOLVES THE VISIBILITY PROBLEM
- <number> SOLVES THE VISIBILITY PROBLEM
- <number> SOLVES THE AGILITY PROBLEM BETTER COMMUNICATION BRIDGES THE GAP of BIZ vs IT FASTER AND EASIER CHANGE
- <number> SOLVES THE CONSISTENCY PROBLEM BRMS ELIMINATES CODING; YOU CAN ALWAYS CODE IF YOU LIKE DECISION SERVICE FOR CLIENT APPLICATIONS
- <number> KNOWLEDGE BELONGS TO PEOPLE, NOT TO THE ORGANIZATION ASSIST THEM TO FOCUS ON WHAT HUMANS DO WELL: DECIDE AND ACT
- <number> MODEL PROCESS BUSINESS USERS WORK WITH IT BPM AUTOMATES IT INTEGRATES WITH SYSTEMS (DIRECTLY OR FUSE)
- <number> LEFT: AUTOMATIC ASSIGNATION TO PEOPLE RIGHT: BAM
- <number>
- <number> BRMS 5.3 to 6.0 -> NO if processes BRMS 5.3 -> BPMS 6.0 OK -> PROMOTION !!!
- <number> BRMS SUITE 6 NO jBPM better ui better control versioning + branching drools new version 6.0 – new rule algorithm, faster and more efficient, better use of memory, scalability optaplanner
- <number> BRMS SUITE 6 NO jBPM better ui better control versioning + branching drools new version 6.0 – new rule algorithm, faster and more efficient, better use of memory, scalability optaplanner
- <number> CLIENT -> USERS -> CLIENTE DECISION SERVICE FOR CLIENT APPLICATIONS
- <number> more tooling! process, forms, bam, SIM
- We will start with a discussion of how the BRMS comes to be. We will breeze over the background of BPM, discuss how the project jBPM releases are incorporated into the BRMS product. From there we will examine the interesting points as they apply to a business user, followed by the more technical elements of BRMS that will be of interest to developers. Finally we will summarize in an overview the new BPM components that come from the jBPM project. We will also mention the components that will NOT be included into the BRMS 5.3 product that are in the jBPM project. These are up and coming features that have yet to mature enough for inclusion at this time, but you can expect to appear in future versions of BRMS.