Professional Documents
Culture Documents
WebSphere Business
Monitor v7
Agenda
1
Business Activity Monitoring (BAM) provides process visibility
Business leaders gain real-time visibility and actionable insight into processes
2
3
Analyze a range of process data with BAM
Take action faster with up-to-minute information on personalized dashboards
For example:
CICS
WebSphere
Business Services
Fabric
IMS
WebSphere MQ
Workflow
WebSphere
Sensor Events
Events
WebSphere
Message Broker WebSphere WebSphere
Business Events Partner Gateway Third Party IBM FileNet P8
Applications 7
How to Publish Events to Monitor
Options to emit XML for BAM via a variety of approaches
WebSphere MQ
WS-Notification
REST
3 4 Services
Event Monitor Model Monitor
Distribution Application Event Database
processing
Action 7
Services
Business Take action (email, pager, alert,
situation events process/service invocation)
Monitor Server
(installed on WebSphere Application Server 7.0 or WebSphere Process Server 7.0)
10
Agenda
11
Model Authoring Tips and Pitfalls
• ***Business*** Monitoring
• Model granularity
• Model constructs to use with care
– Child MCs
– Recurring wait-time triggers
– Deliver to All
12
Business-relevant Events
• Only turn on event emission
where truly necessary for
business activity monitoring
– WebSphere Business Monitor should not
be used for IT monitoring
– Enabling emission for all possible event
types might cause 100 events to be
emitted per process instance, but your
monitor model may only have KPIs, etc.
that care about 10 of those
– Best practice is to just turn on events
used in selected templates and variables
– Turning off unneeded events improves
performance of both the emitting app
and the monitor model 13
Model Granularity
It is generally best to split up monitor models
based upon the event source
Each model is autonomous: a separate application
with its own input event stream
Consider a single high-level
model, fed by outbound
events emitted from
multiple low-level models
– Business analysts only care
about the high-level model
– The low-level models could
change without affecting the
high-level model (if the event
definitions remain constant) 14
Generate high and low level monitor models
IBM developerWorks Download for Modeler
15
Child Monitoring Contexts
When generating an MM from BPEL, consider using
Event Groups rather than Child MCs for activities
- Reduces number of cubes, simplifies dashboard usage
16
Recurring wait time triggers
• Triggers that should be
evaluated periodically
• Consider dashboard
defined KPI alerts over
modeled KPI alerts 17
Deliver to All
• Event delivery option for multiple correlation matches
• Be careful when you have many active instances and
the event could correlate to a high percentage of them
– With 1 million active instances, an event that correlates to
1/3 of them, arriving once every 5 minutes, would result in
over 1000 event deliveries/second
18
Multi-threaded event processing
• Events are processed more efficiently in multi-threaded mode
• Requirements to support multi-threading:
– All inbound events must contain the key to the root MC
– All correlation expressions (including for events for child/grandchild
MCs) must reference that key to the root MC
20
Monitor Runtime Components
• CEI Event Service
• Queue Bypass
• Service Integration Bus
• Dimensional Analysis & Reporting
• Business Space
• Business Monitor API REST Service
• Business Monitor Action Services
• Business Monitor Data Movement Services
• Business Monitor Data Services Scheduler
21
CEI Event Service
• Business Monitor uses the CEI Event Service to emit outbound events.
• Which CEI Event Service is used is specified by defining an Emitter
Factory for use by Business Monitor.
• Business Monitor emits outbound events synchronously by default to
ensure that event order is preserved.
22
CEI Event Service
• Tuning parameters
– Release-to-release performance results
• Error Handling
• Error Queue
34
Tuning Parameters
• Use multi-threaded mode
36
Release-to-Release Performance
Events per Second
2000
1750
1500
1250
1000
750
500
250
0
Monitor 6.0.2 Monitor 6.1 Monitor 6.2 Monitor 7.0*
• Correlation exceptions
• Parent exceptions
• Value out of range behavior
• Retry settings
38
Error Queue
• Use the admin console (or wsadmin/Jython)
to view and administer the error queue
39
Just Announced
41
High Availability
• Use clustering to avoid a Single Point of Failure,
and for workload management*
v7 Improvement
• WPS has made Deployment Environment
framework a common component
available to all BPM stack products.
• Monitor exploits Deployment Environment
framework and offers two out of the box
topology patterns:
Sample 4-cluster topology with 2 nodes for failover and scalability
► Create a 1-cluster topology for POCs and
small production environments that need
simple failover
► Create a 4-cluster topology for increased
production isolation and scalability
44
Business Monitor as part of BPM Deployment
Environments
46
Summary
• Choose queue-bypass
48
Get started on the path to agility, performance, and
growth TODAY !
• Learn about Getting Started with IBM
BPM for Rapid ROI
http://publib.boulder.ibm.com/bpcsamp/
50
Go to the Business Process Management Zone!
http://www.ibm.com/developerworks/bpm
51
Learning More about WebSphere BPM
IBM Education Assistant
http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/topic
/com.ibm.iea.wbmonitor_v7/plugin_coverpage.html
52
Copyright and Trademarks
53