Slide 1

Slide 1 text

Runtime governance to achieve greater business visibility Kenneth Peeples, JBoss Technology Evangelist Ivan McKinley, Senior JBoss Consultant July 24, 2013

Slide 2

Slide 2 text

RED HAT | Runtime governance to achieve greater business visibility 2 Abstract Breached SLAs, customers identifying your problems before you do, excessive problem identification time, and the time-consuming and costly task of combining data from various systems. Sound familiar? Runtime governance can help. Runtime governance consists of the collection, correlation, analysis, and presentation of realtime results based on activity events collected from heterogeneous distributed environments. It gives operations and business owners visibility into the health and behavior of a system to react to a combination of events from different systems. Join this webinar to learn how runtime governance provided by Red Hat® JBoss® Fuse Service Works can give you more visibility into your organization’s operations

Slide 3

Slide 3 text

Fuse Service Works Overview Kenneth Peeples

Slide 4

Slide 4 text

RED HAT | Runtime governance to achieve greater business visibility 4 JBoss Integration Product Line

Slide 5

Slide 5 text

RED HAT | Runtime governance to achieve greater business visibility 5 Switchyard

Slide 6

Slide 6 text

RED HAT | Runtime governance to achieve greater business visibility 6 JBoss Overlord – S-RAMP

Slide 7

Slide 7 text

JBoss Overlord – Service Lifecycle Management Design-Time Governance addresses: • Policy management • Quality management • Lifecycle management The Design-Time Governance functionality is layered on top of an S-RAMP repository to provide the following capabilities: • Store and Govern artifacts • Custom Governance Workflows • Integrated Governance Human Task Management

Slide 8

Slide 8 text

RED HAT | Runtime governance to achieve greater business visibility 8 JBoss Overlord – Business Transaction Monitoring

Slide 9

Slide 9 text

RED HAT | Runtime governance to achieve greater business visibility 9 Top Down Fuse Service Works Use Case

Slide 10

Slide 10 text

Run Time Governance Ivan McKinley

Slide 11

Slide 11 text

Provisioning systems Purchasing department External Partner systems Nightly batches

Slide 12

Slide 12 text

complexity of large system landscapes How many systems are affected to make a single business transaction happen • Shop System • CRM • Billing System • External Payment Providers • Order management or Provisioning Typcialy a business transaction spans multiple services and possibly IT systems

Slide 13

Slide 13 text

Consider complexity of large system landscapes How to detect bottlenecks and latency in the business service? How to define and track measurable service level agreements? A business process typically spreads across multiple services

Slide 14

Slide 14 text

Number provisioning systems Purchasing department External Partner systems Nightly batches

Slide 15

Slide 15 text

Business Transaction creates Value broken Business Transaction ?

Slide 16

Slide 16 text

Avoid To have unmonitored Business processes and transactions, that span multiple services and systems BECAUSE If Lines of Business inform you of a problem you are already in a defensive and reactive position If Feedback from Users is the First Point in Time you hear about an Issue - you already lost to much • Time • Reputation • Money

Slide 17

Slide 17 text

RTGov Server Event pre-emptive action Informed decision Identify trends EPN Infinispan, DB, Elasticsearch Drools Fusion REST RTGov UI Lets try that again!

Slide 18

Slide 18 text

RTGOV : • Part of overlord governance project • https://www.jboss.org/overlord • Often referred to as Business activity monitoring or BAM • The monitoring of business processes across multiple systems • Determining the impact of events in the context of the business • Realtime analytics and reacting on these events

Slide 19

Slide 19 text

Realtime event collection Two ways to report events Integrated Preprocessing Validation Business policy enforcement REST API Submission of events Querying events

Slide 20

Slide 20 text

Integrated collector

Slide 21

Slide 21 text

RTGov Server Event Perform pre-emptive action: Identify trends EPN Infinispan, DB, Elasticsearch Drools Fusion REST RTGov UI Lets try that again!

Slide 22

Slide 22 text

EPN A network of nodes Event processors • Performs realtime analysis • Performs transformation Event distribution Notifications

Slide 23

Slide 23 text

EPN: Processors • DroolsEventProcesor • MvelEventProcessor • KeyValueEventProcessor (Elasticsearch)

Slide 24

Slide 24 text

EPN Event types

Slide 25

Slide 25 text

RTGov Server Event Perform pre-emptive action: Identify trends EPN Infinispan, DB, Elasticsearch Drools Fusion REST RTGov UI Lets try that again!

Slide 26

Slide 26 text

EPN CEP CEP. complex event processing • Detect, Correlate, React • Primarily an event processing concept Event is a • Significant • change of state • at a particular point in time Complex event • Abstraction, composition or aggregation of other events

Slide 27

Slide 27 text

EPN CEP: Scenario An airport has a baggage routing, monitoring and control system. – When a bag is checked in (scanned) at the check-in desk and is not scanned at the load staging area within 10 minutes, raise a warning for bag missing Reasoning over absence of events 1 rule “Baggage lost” 2 when 3 $b1 : BagScanned( location == CHECK_IN ) 4 not BagScanned(bagTag == $b1.bagTag, 5 location == STAGING, 6 this after[0s,10m] $b1 ) 7 then // Raise a event 8 end 1 { 2 "name": "LostBaggageCEPProcessor", 3 "sourceNodes" :["BagScanned"], 4 "predicate": { 5 "@class": "org.overlord.rtgov.ep.mvel.MVELPredicate", 6 "expression": "event instanceof org.overlord.rtgov.example.BaggageEvent" 7 }, 8 "eventProcessor": { 9 "@class": "org.overlord.rtgov.ep.drools.DroolsEventProcessor", 10 "ruleName": "lostBaggage" 11 }, 12 "notifications": [ 13 { 14 "type": "Results", 15 "subject": "LostBag" 16 } 17 ] 18 }

Slide 28

Slide 28 text

RTGov UI: Services • High level view of the services deployed • References and dependency data • Details service information

Slide 29

Slide 29 text

RTGov UI:Situations • Outline situations detected by RTGov • Data drill down and call trace data. • Identification of issues • Ability to perform corrective action by replaying message

Slide 30

Slide 30 text

RTGov UI: Analytics • Based on Kibana • Data drill down and deep drive analytics . • Data correlation • Extendable : Business specific data can added with little effort

Slide 31

Slide 31 text

RTGov UI : Services Services View • High level view of the services deployed • References and dependency data • Details service information Situation View • Outline situations detected by RTGov • Data drill down and call trace data. • Identification of issues • Ability to perform corrective action by replaying message

Slide 32

Slide 32 text

Demo

Slide 33

Slide 33 text

Demo : SLA • Identity and react on SLA breach

Slide 34

Slide 34 text

Demo : SLA • INSERT SCREEN share here

Slide 35

Slide 35 text

Demo : SLA • Apply runtime policy based on business data

Slide 36

Slide 36 text

Demo : SLA • INSERT SCREEN share here

Slide 37

Slide 37 text

Demo : SLA • Apply runtime policy based on business data

Slide 38

Slide 38 text

Demo : SLA • INSERT SCREEN share here