Redp 4433

Front cover
IBM Business
Process Management
Reviewers Guide
Work smarter through business-IT
collaboration
Enable business-driven design

and realize business agility
Achieve continuous process

improvement
Luc Chamberland
Lee Gavin
Alex Koutsoumbos
Ramani Mathrubutham
Jim McGarrahan
Joe Pappas
ibm.com/redbooks Redpaper
International Technical Support Organization
IBM Business Process Management Reviewers Guide
April 2010
REDP-4433-02
Note: Before using this information and the product it supports, read the information in Notices on
page vii.
Third Edition (April 2010)
This edition applies to IBM WebSphere Dynamic Process Edition Version 7.0, its offerings, and related
offerings and technologies, including Business Space powered by WebSphere, IBM WebSphere Business
Modeler, IBM WebSphere Business Compass, IBM WebSphere Integration Developer, IBM WebSphere
Process Server, IBM WebSphere Business Monitor, IBM WebSphere Business Services Fabric, and IBM
WebSphere Industry Content Packs.
Copyright International Business Machines Corporation 2010. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
The team who wrote this paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Now you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Stay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

April 2010, Third Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1. Charting the BPM vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 Building a smarter planet with BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 The characteristics of BPM success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1 Flexibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.2 Agility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.3 Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.4 Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.5 Business and IT alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.6 Continuous process improvement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 The IBM BPM Suite. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.1 WebSphere Business Compass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.2 WebSphere Business Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.3 WebSphere Integration Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.4 WebSphere Process Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.5 WebSphere Business Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.6 WebSphere Business Services Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.7 WebSphere Industry Content Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.8 Business Space powered by WebSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3.9 Additional offering capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Unifying focus areas across WebSphere Dynamic Process Edition . . . . . . . . . . . . . . . . 7
1.4.1 Linking strategic intent to processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4.2 Workflow support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.3 Business rules and policy support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.4 BAM enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.5 Accelerated time to value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.6 Improving business and IT collaboration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5 Building on open standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6 Supporting global solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.7 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2. BPM interaction with Business Space powered by WebSphere . . . . . . . . 11

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2 Common user interface infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.1 Business Space powered by WebSphere concepts . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.2 Creating your own business space and pages . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.3 Managing business spaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2.4 Saving time with pre-built business space templates . . . . . . . . . . . . . . . . . . . . . . 19
Copyright IBM Corp. 2010. All rights reserved. iii

2.2.5 Integrating with other user interface frameworks . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3 Accelerate time to value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3.1 BPM life-cycle stages and associated widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 3. Enabling BPM with WebSphere Business Compass and WebSphere

Business Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2 Collaborate on strategic intent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.1 Strategy, capability, vocabulary, organization, and process maps . . . . . . . . . . . . 32
3.2.2 Collaboration diagrams, service documents, and form documents . . . . . . . . . . . 33
3.3 Facilitating modeling for documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.1 Customizable process diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.2 Facilitate printing and reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.4 Growing the role of business. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.4.1 Human-centric processes and forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.4.2 Interactive process design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.5 Accelerating time to value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.5.1 SOA Business Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.5.2 APQC process classification framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.5.3 Growing a repository of assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.5.4 Leverage assets defined in WebSphere Business Services Fabric . . . . . . . . . . . 51
3.6 Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.6.1 Reviewing processes with WebSphere Business Compass . . . . . . . . . . . . . . . . . 52
3.6.2 Leveraging Excel spreadsheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.7 Closing the gap between business and IT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.7.1 Data maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.7.2 Implementation-ready business measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.8 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 4. Enabling BPM with WebSphere Integration Developer and WebSphere

Process Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.2 A foundation for reusable assets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.2.1 Service Data Objects (SDOs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2.2 Service Component Architecture (SCA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.2.3 BPEL choreography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.3 Enabling agility in business solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.3.1 Business rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.3.2 Service selection and mediation policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.4 Accelerating time to value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.1 Leveraging the process model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.4.2 Interactive process design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.4.3 Consuming iterative definitions from WebSphere Business Modeler . . . . . . . . . . 73
4.4.4 Migrating running business processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.4.5 Developing service gateways and proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.4.6 Sharing evolving projects for monitor model development . . . . . . . . . . . . . . . . . . 76
4.4.7 Team development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.4.8 Integration Solutions view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.4.9 Tools for testing and problem determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.4.10 Server Logs view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.5 Enhancing human-centric BPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.5.1 Dynamicity for knowledge workers (case handling) . . . . . . . . . . . . . . . . . . . . . . . 81
4.5.2 Parallel routing of a task with result aggregation . . . . . . . . . . . . . . . . . . . . . . . . . 84
iv IBM Business Process Management Reviewers Guide

4.5.3 Business calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.5.4 Integrated forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.5.5 Audit trails of processes and tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.5.6 Federating staff repositories and participant substitutions . . . . . . . . . . . . . . . . . . 88
4.6 Lowering the total cost of ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.6.1 Administering business processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.6.2 Managing failed processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6.3 Storing and forwarding messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.6.4 Administering solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.6.5 Availability and scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.7 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Chapter 5. Enabling BPM and BAM with the WebSphere Business Monitor. . . . . . . . 97
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.2 Empowering the line of business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.2.1 Critical insight throughout the business day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.2.2 Creating and subscribing to business alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.2.3 Personalizing and creating KPIs on the fly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.2.4 Accessing KPI history and projecting future KPI values . . . . . . . . . . . . . . . . . . . 102
5.2.5 Monitoring and managing human tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.2.6 Business problem root-cause analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.2.7 Using monitor data for reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.2.8 Quickly test and monitor business processes . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.3 End-to-end process visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.3.1 Monitoring WebSphere Process Server and WebSphere Enterprise Service Bus
applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.3.2 Improving insight with WebSphere Business Events . . . . . . . . . . . . . . . . . . . . . 109
5.3.3 Monitoring applications with WebSphere Message Broker. . . . . . . . . . . . . . . . . 110
5.3.4 Monitoring CICS applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.3.5 Monitoring events from IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.3.6 Monitoring FileNet processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.3.7 Monitoring WebSphere MQ Workflow processes and applications . . . . . . . . . . 115
5.3.8 Monitoring business applications with WebSphere Adapters . . . . . . . . . . . . . . . 116
5.3.9 Emitting custom events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.3.10 Robust event handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.3.11 Automating corrective and mitigating action . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.4 Accelerating time to value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.4.1 Simplified iterative development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.4.2 Achieve quickstart monitoring with WebSphere Process Server . . . . . . . . . . . . 122
5.4.3 Predefined templates and assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.4.4 SOA Business Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5.4.5 Industry accelerators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5.4.6 KPI and Key Agility Indicator (KAI) libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.4.7 Synchronization with WebSphere Integration Developer . . . . . . . . . . . . . . . . . . 127
5.4.8 Synchronization with WebSphere Business Modeler . . . . . . . . . . . . . . . . . . . . . 129
5.4.9 Developing using Rational Application Developer . . . . . . . . . . . . . . . . . . . . . . . 129
5.4.10 Full-function unit test environment with interactive debug . . . . . . . . . . . . . . . . 130
5.4.11 Event recording and playback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.5 Lowering the total cost of ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
5.5.1 Flexible configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
5.5.2 Simplifying administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.6 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Contents v
Chapter 6. Enabling dynamic BPM with WebSphere Business Services Fabric. . . . 135
6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
6.2 A foundation for dynamic BPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
6.2.1 Business services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
6.2.2 Composite business applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
6.2.3 Dynamic assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
6.2.4 Business service repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.3 Enable agility with business service policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
6.3.1 Business service policy simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
6.3.2 Programming business service policy modeling using context specifications . . 144
6.3.3 Expressive business service policy power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
6.3.4 Authoring business applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
6.3.5 Authoring business service policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
6.4 Web-based authoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
6.4.1 Authoring vocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
6.5 Integrated and aligned with the WebSphere BPM portfolio . . . . . . . . . . . . . . . . . . . . 149
6.5.1 Programming model alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.5.2 Integration with WebSphere Business Modeler . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.5.3 Integration with WebSphere Business Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.6 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Chapter 7. Accelerating time-to-value with WebSphere Industry Content Packs . . . 153

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
7.2 WebSphere Industry Content Pack core tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
7.3 Using WebSphere ICP assets in business-driven BPM solution development . . . . . . 162
7.4 WebSphere Telecom ICP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
7.5 WebSphere Banking ICP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
7.6 WebSphere Healthcare ICP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
7.7 WebSphere Product Lifecycle Management ICP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
7.8 WebSphere Insurance ICP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
7.9 WebSphere ICP asset navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
7.10 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
How to get IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
vi IBM Business Process Management Reviewers Guide

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product, program, or service that does not
infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not give you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring
any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs.
Copyright IBM Corp. 2010. All rights reserved. vii

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. These and other IBM trademarked terms are
marked on their first occurrence in this information with the appropriate symbol ( or ), indicating US
registered or common law trademarks owned by IBM at the time this information was published. Such
trademarks may also be registered or common law trademarks in other countries. A current list of IBM
trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
CICS InfoSphere Redbooks (logo)
ClearCase Lotus Notes RequisitePro
Cognos Lotus Sametime
DataPower Notes Smarter Planet
DB2 Rational Team Concert WebSphere
FileNet Rational z/OS
IBM Redbooks
IMS Redpaper
The following terms are trademarks of other companies:
Java, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.
Microsoft, and the Windows logo are trademarks of Microsoft Corporation in the United States, other
countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
viii IBM Business Process Management Reviewers Guide

Preface
Market demand for business process management (BPM) has grown significantly in recent
years and shows no sign of abating. Based on consultations with our clients, a set of
capabilities that IBM makes available enables you to build robust and holistic BPM solutions,
whether they are integration-centric, human-centric, or content-centric.
In this IBM Redpaper publication, we provide an overview of the IBM BPM portfolio to BPM
market watchers who have a keen interest in understanding the most current BPM technology
releases and how they can be used together. Specifically, we review WebSphere Dynamic
Process Edition, including the following key benefits and capabilities:
Role-based business spaces
IBM WebSphere Business Modeler
IBM WebSphere Integration Developer
IBM WebSphere Process Server
IBM WebSphere Business Monitor
IBM WebSphere Business Services Fabric
IBM WebSphere Business Compass
IBM WebSphere Industry Content Packs
For more information about the IBM strategy to provide innovative technology in the BPM
marketplace, go to the IBM Web page:
http://www.ibm.com/software/info/bpm/
The team who wrote this paper

This paper was produced by a team of specialists from around the world working with the
International Technical Support Organization.
Luc Chamberland is a Manager with WebSphere Business Process Management for IBM in
Toronto, Ontario, Canada. He provides guidance to IBM clients and field-facing teams on
WebSphere Dynamic Process Edition and the business value of BPM, and identifies BPM
trends and requirements for consideration in future product plans. Luc has worked with IBM
for 16 years in numerous areas, including Java and XML development, cross-product
strategy, and compilers. He holds a Master of Arts degree from the University of Toronto.
Lee Gavin is a Consulting IT Specialist in the WebSphere BPM Black Belt Team. The Black
Belt Team is a worldwide team with a focus on client pre-sales engagement and enablement
for the IBM WebSphere BPM portfolio of products. Prior to joining the Black Belt Team, Lee
was the SW IOT TechWorks lead for WebSphere Business Monitor, WebSphere Message
Broker, and WebSphere Adapters. From 20012006, Lee was an ITSO Project Leader (in
Hursley and Raleigh) in the WebSphere team, specializing in business integration and
application integration.
Copyright IBM Corp. 2010. All rights reserved. ix

Alex Koutsoumbos is a Consulting IT Specialist in the worldwide WebSphere BPM
BlackBelt team. Based in Melbourne, Australia, he has been in the IBM SWG for over 12
years. His expertise spans applications development, distributed object technologies, and
service-oriented architecture (SOA), with a primary focus on BPM. He holds a Bachelors of
Information Technology in Software Development from Monash University. He has contributed
to numerous publications, including papers and IBM Redbooks publications.
Ramani Mathrubutham is with the WebSphere BPM Enablement Team in USA. He has
seven years of experience in BPM and SOA and holds MS and MBA degrees. He has 15
years of software development experience in creating enterprise software applications in Java
and in other languages.
Jim McGarrahan is a Senior Software Developer in the United States. He has more than five
years of experience in the WebSphere Business Process Management software development
organization. He has worked at IBM for 24 years. His areas of expertise include Business
Process Management, including Business Activity Monitoring and Systems Management. He
has recently written about combining Process Lifecycle Management with Business Process
Management to optimize Automotive end-of-life processes and how Business Event
Processing and Business Intelligence can be leveraged with Business Activity Monitoring for
increased insight into business processes and improved ability to take mitigating and
corrective action to address business situations.
Joe Pappas is a Consulting IT Specialist in the Business Performance and Service

Optimization organization with 10 years of Business Process Management experience. He
holds an MBA in Finance from Fordham University and a BS in Aerospace Engineering from
Boston University. He has expertise in WebSphere Business Monitor and human-centric
business process management. He has contributed to a number of IBM Redbooks and
Redpaper publications in regard to Business Process Management.
The authors want to give special thanks to Laura Gardash (IBM Canada), our editor, for her
guidance and assistance.
Thanks to the authors of the previous edition of this paper:

Luc Chamberland
Ramani Mathrubutham
Jim McGarrahan
Jennifer King
Now you can become a published author, too!

Heres an opportunity to spotlight your skills, grow your career, and become a published
author - all at the same time! Join an ITSO residency project and help write a book in your
area of expertise, while honing your experience using leading-edge technologies. Your efforts
will help to increase product acceptance and customer satisfaction, as you expand your
network of technical contacts and relationships. Residencies run from two to six weeks in
length, and you can participate either in person or as a remote resident working from your
home base.
Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html
x IBM Business Process Management Reviewers Guide

Comments welcome
Your comments are important to us!
We want our papers to be as helpful as possible. Send us your comments about this paper or
other IBM Redbooks publications in one of the following ways:
Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
Send your comments in an e-mail to:
redbooks@us.ibm.com
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400
Stay connected to IBM Redbooks

Find us on Facebook:
http://www.facebook.com/pages/IBM-Redbooks/178023492563?ref=ts
Follow us on twitter:
http://twitter.com/ibmredbooks
Look for us on LinkedIn:
http://www.linkedin.com/groups?home=&gid=2130806
Explore new Redbooks publications, residencies, and workshops with the IBM Redbooks
weekly newsletter:
https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm
Stay current on recent Redbooks publications with RSS Feeds:
http://www.redbooks.ibm.com/rss.html
Preface xi
xii IBM Business Process Management Reviewers Guide
Summary of changes
This section describes the technical changes made in this edition of the paper and in previous
editions. This edition may also include minor corrections and editorial changes that are not
identified.
Summary of Changes
for IBM Business Process Management Reviewers Guide
as created or updated on April 16, 2010.
April 2010, Third Edition

This revision reflects the addition, deletion, or modification of new and changed information
described below.
New information
IBM WebSphere Business Compass
IBM WebSphere Industry Content Packs
Business Space powered by WebSphere
Changed information
IBM WebSphere Business Modeler
IBM WebSphere Integration Developer
IBM WebSphere Process Server
IBM WebSphere Business Monitor
IBM WebSphere Business Services Fabric
Copyright IBM Corp. 2010. All rights reserved. xiii

xiv IBM Business Process Management Reviewers Guide
1
Chapter 1. Charting the BPM vision

IBM understands todays business climate and challenges, and provides a holistic business
process management (BPM) vision and portfolio of capabilities so that businesses can
embrace the reality of the Smarter Planet.
This chapter discusses the BPM vision and provides an overview of the IBM BPM portfolio.
Copyright IBM Corp. 2010. All rights reserved. 1

1.1 Building a smarter planet with BPM
Dramatic increases in computing power are leading to new approaches and smarter solutions
in which flexible, intelligent, and dynamic infrastructures can be applied to address current
and future opportunities. Businesses can instrument activities so that they can be measured
and improved, interconnect across silos, partners, and the broader value chain, and
intelligently derive insight from an interconnected world of devices, systems, and businesses.
Businesses like these have embraced the smarter planet vision.
BPM provides a path to participating in the smarter planet. BPM manifests itself in numerous
ways in business environments. Typical BPM solutions are all around us: supply chain
processes for inventory management, self-service portals for managing employee benefits,
financial processes for compliance, and call center management reports for service
organizations. Whether your business needs to document existing processes, define flexible
policy options to handle a broad scope of business situations, facilitate human task flows,
inject intelligence into systems to reflect business-level decision-making, or gather
operational details about how well the business is running, BPM is there.
As the pace of change and competition accelerates in todays challenging economic climate,
enterprises are under tremendous pressure to improve the way they do business. Business
leaders from around the world are focused more than ever on the economic, social, and
environmental changes driven by global integration, where free trade agreements, the
Internet, and globalization are simultaneously making the world smaller, flatter, and smarter.
These leaders have articulated the need to deliver products and services faster, raise the
quality of what they deliver, rein in costs, grow revenues, raise the bar on accountability and
transparency, have the agility to take advantage of market opportunities, have information on
hand to react to unforeseen events, and be able to see long term trends. Global economic
pressures drive business needs to be more agile, flexible, and responsive to market
demands. Regardless of how well the enterprise runs, it needs to adapt and improve, or it will
be outdone by competitors.
Whats the downside of inflexible business models and siloed solutions? Production and
service outages, backlogs and process bottlenecks, supply chain disruptions, stock outs,
missed service level agreements, ineffective use of staff, poor customer satisfaction,
operational reports that provide too little too late, and the list goes on. No one wants to be the
next case study on enterprise failure.
By working smart, businesses achieve the agility to succeed. Overcome the restrictions of the
past by moving to an agile business model, use Web 2.0 to build interactive ecosystems to
meet the situational needs of knowledge workers, build dynamic processes that leverage
reusable, service-based components, and embrace the Smart SOA approach that turns
applications into reusable services.
1.2 The characteristics of BPM success

The demands on information systems to help the business step up to current challenges are
enormous. The enterprise looks to information systems to fulfill requirements that, at times,
seem incompatible, and IT leaders have the daunting task of enabling the right IT
infrastructure to enable the CEOs vision. Let us consider the key characteristics of a holistic
BPM infrastructure.
2 IBM Business Process Management Reviewers Guide

1.2.1 Flexibility
Business dynamics change, regardless of how well plans are thought out. But how easy is it
to modify an IT solution without a massive IT effort? The choices made today should not limit
the choices that need to be made in the future.
Imagine that a bank has implemented a consumer loan approval process wherein the credit
verification portion of the process has been outsourced to a third party. During the first six
months that the solution has been in production, the bank has been continually unimpressed
with the third partys track record of returning consumer credit data. The service level
agreement is not being met, which itself was difficult to determine. The banks confidence in
the third party is waning, but the bank does not want its reputation of providing fast customer
service to suffer. If the bank chooses a different third party to provide the credit check service,
can it switch out vendors with minimal IT costs and no service interruption?
1.2.2 Agility
There are many decisions to make as processes run. The right decision is often influenced by
various factors and cannot simply be expressed as a set of conditional if-then-else
statements. The business needs to express a dynamic business policy in terms that IT
infrastructure can effectively harness, and that the business can manage on the fly as that
policy changes.
Imagine that an airline is facing tough competition to keep fares low, manage rising costs, and
still make a profit. It establishes a complex pricing policy that determines fares dynamically
through various factors and calls to services that are not known until a fare request is issued.
Being able to effectively define and simulate this policy before deployment and modify the
policy to keep pace with market changes will determine whether the fleet will still be flying in a
year.
1.2.3 Collaboration
Invariably, disparate departments in an enterprise often develop and grow their missions and
capabilities isolated from other departments. As these departmental silos grow, so do their IT
systems, but at some point you realize that there is valuable information that should be
shared across departments. Enabling departments to share information reveals business
efficiencies (for example, by eliminating the need to enter duplicate data) and provides
broader business insight across the organization. But can these disparate systems be
enabled to work together without costly and risky rip-and-replace initiatives?
1.2.4 Speed
Business no longer has the luxury of taking years to develop solutions. Business and IT
departments require the tools to assemble solutions based on reusable assets, minimal
coding, robust integrated test facilities, and a straightforward deploy capability.
Heterogeneous environments introduce the additional challenge of integrating various
hardware and software platforms, which dare not slow down solution development.
Imagine that the CIO has asked for more detailed cost analysis reports to see how
depreciation of the retail inventory affects overall costs. You have four weeks to pull together a
prototype. IT architects and developers will need to extend the existing solution to pull in data
from inventory ERP systems, modify cost calculations and the report format, and collaborate
with subject matter experts from the accounting department to validate that the right
Chapter 1. Charting the BPM vision 3

approach is being taken. Can you show a prototype in four weeks? Sometimes, you do not
get a second chance.
1.2.5 Business and IT alignment

To effectively improve business processes, an organization cannot and should not rely solely
on IT resources to design, collaborate, improve, build, deploy, and monitor those processes.
The line of business (LOB) brings subject matter expertise and domain knowledge into the
definition of what the business needs (requirements), why certain needs are prioritized higher
than others (strategic goals), and how those needs are reflected in process definitions
(models). Striking the right balance across your organization to optimally leverage strengths
and experiences across both the IT and LOB departments facilitates the speed and agility
that you need to succeed.
The LOB needs to take a much more active role in both defining and testing business
processes and seeing the business results in real time so it can react swiftly with business
insight. The LOB needs tools that can be easily tailored and used, tools that provide the
necessary handoffs and integration points with the IT organization.
Consider the case where a Store Operations Executive for a retail chain, using a business
dashboard, is notified that sales in a particular outlet are lagging. Drilling down through the
data to identify the root cause, she also notices that there have consistently been low staffing
levels at the store. Armed with timely, relevant information, this business leader can take
action to ensure that there are better recruiting and retention practices at the store. She also
asks human resources to ensure that the sales training process has correct compliance
measures in place, and that those measures also be tracked in the business dashboard.
1.2.6 Continuous process improvement

Implementing effective BPM in your organization is an ongoing journey. Processes are initially
designed, simulated, and tested based on a set of assumptions about many factors: costs,
activity durations, resource availability, and probabilities around various process paths. As
BPM solutions are deployed and used in production environments, visibility into real-world
analytics might, quite likely, challenge some of those key assumptions. Continuous process
improvement is about taking those production-time insights and refactoring them into your
original process models to evolve them for optimal performance.
For example, consider an automated insurance claim processing solution in which the
percentage of claims that would require manual exception handling was originally estimated
at 5%. In production, however, the monitoring results over the past six months show that 12%
of the claims require human intervention. This discrepancy could impact the staffing levels
you require to meet customer satisfaction targets. Being able to leverage root-cause analysis
to improve your process design should be a best practice approach to improving your
business.
1.3 The IBM BPM Suite

The IBM BPM Suite contains a comprehensive set of role-based, componentized capabilities
that provide end-to-end process automation and coordinate human activities to enhance
performance, lower costs, reduce cycle times, address regulatory compliance requirements,
and make the business easier to manage. Leaders can transform insight into action to take
advantage of opportunities and mitigate risks with real-time process visibility.

Using the IBM BPM Suite, you can strategize, model, simulate, run, rapidly change, monitor,
and optimize core business processes. The IBM BPM Suite brings together capabilities from
across IBM and includes a choice of three foundational offerings, each with specific strengths
to help you get started quickly with BPM regardless of the type of BPM solution you need:
IBM WebSphere Dynamic Process Edition, which supports a broad range of scenarios
that can include service-oriented architecture (SOA) infrastructures and back-end
integration, combinations of automated services, human activities, diverse operating
system platforms, IT and LOB project drivers, transactional integrity, scalability, and
performance
IBM FileNet Business Process Manager supports content-centric scenarios where
enterprise content management and analytics surrounding enterprise documents and
data are as critical as the processes themselves.
Lombardi, an IBM company, supports quick time-to-value scenarios where LOB drives
human-centric projects that have minimal integration requirements.
You can use these offerings in combination or stand-alone, driven by your business needs.
They provide strong interoperability so that you can start with the offering that addresses your
most immediate needs and evolve your enterprise capability over time by including additional
offerings to address a broader spectrum of BPM scenarios. WebSphere Dynamic Process
Edition provides the following integrated set of capabilities that enable your business to
quickly build, deploy, and manage robust BPM solutions.
1.3.1 WebSphere Business Compass

WebSphere Business Compass is an on-premise, server-based platform that enables
business leaders to analyze the strengths, weaknesses, opportunities, and threats across the
business, map out their organizational capability, and identify the priority areas for BPM
attention. A Business Process Management Notation (BPMN) process editor can be used to
define high-level process maps. With BPM BlueWorks, you can collaborate to define strategic
intent in a cloud-based environment hosted by IBM. BlueWorks includes a wealth of
industry-specific assets, blogs, and podcasts that encourage BPM community.
With WebSphere Business Compass, you can also host process model reviews so that
authorized staff can review and comment on process model definitions before IT
implementation. When model definitions have been approved, you can host system-of-record
process definitions that can be referred to across your organization, all accessible using a
Web browser.
1.3.2 WebSphere Business Modeler

With WebSphere Business Modeler, a business analyst can fully visualize, understand,
document, test, and share business processes. You can simulate process runs to identify
bottlenecks and inefficiencies, and define key performance indicators and business metrics
for use in WebSphere Business Monitor. Then, you can leverage the real business results in
WebSphere Business Modeler simulations for continuous process improvement. In addition,
WebSphere Business Modeler can generate IT implementation artifacts for WebSphere
Process Server and facilitate testing of human-centric processes in a process server
environment.

1.3.3 WebSphere Integration Developer
With WebSphere Integration Developer, you can build services and SOA-based integration
solutions across WebSphere Process Server, WebSphere Enterprise Service Bus (ESB), and
WebSphere Adapters. Plus, WebSphere Integration Developer accelerates the adoption of
SOA by rendering existing IT assets as service components, encouraging reuse and
efficiency. Using drag-and-drop technology and wiring reusable service components together,
the integration developer can construct process and integration solutions. Furthermore, the
test and debug capabilities of WebSphere Process Server and WebSphere Business Monitor
enable you to rapidly prototype BPM and business activity monitoring (BAM) solutions.
1.3.4 WebSphere Process Server

WebSphere Process Server is a high-performance engine that ensures your BPM solutions
are enabled through SOA for maximum flexibility, interoperability, scalability, and robustness.
First-class support is provided for straight-through processing, human tasks, business rules,
and business state machines. The integrated service bus mediates disparate resources for
reuse, irrespective of vendor, platform or whether they are home-grown or packaged
applications. The sophisticated management tools of WebSphere Process Server enable you
to easily see the overall health of your solutions, administer security, start and stop
processes, and modify business rules that have already been deployed.
1.3.5 WebSphere Business Monitor

WebSphere Business Monitor is an integrated business activity monitoring (BAM)
environment that provides end-to-end visibility of business activity on WebSphere Process
Server, WebSphere MQ Workflow, FileNet Business Process Manager, and other enterprise
applications. Web-based and portal-based dashboards provide near real-time information so
that business leaders can make timely operational and strategic decisions. Fully configurable
dashboards show you only what you need to see, and deliver alerts to e-mail, pagers, or
PDAs. Monitoring results can be used in WebSphere Business Modeler simulations to
complete the BPM feedback cycle, and the WebSphere Business Monitor development toolkit
provides templates and a test environment to further accelerate time to value.
1.3.6 WebSphere Business Services Fabric

WebSphere Business Services Fabric simplifies business process assembly and
management of composite business applications. By exposing the capability of IT systems as
reusable application building blocks, business users can enact rapid business process
change using business policies instead of code. Process execution is customized based on
preferences and entitlements of recipients. Clients can confidently innovate and respond to
market demands with greater agility and flexibility. Furthermore, dynamic services give you
the ability to leverage existing assets (third party, custom, or from WebSphere Industry
Content Packs).
1.3.7 WebSphere Industry Content Packs

To accelerate solution development, WebSphere Industry Content Packs provide
standards-based, industry-specific assets. Each pack offers a set of assets that span the
BPM life cycle, from capability models and process models for use at design time, to service
models and sample dashboards for use during solution implementation. You can customize
templates, assets, and samples for reuse and integrate them seamlessly with the WebSphere

BPM tools. The following industries are supported: telecommunications, banking, insurance,
healthcare, and industrial product life-cycle management.
1.3.8 Business Space powered by WebSphere

To give users Web-based mashup capability to assess, collaborate, and take action on
running the business, a role-based business space is bundled with the WebSphere Dynamic
Process Edition runtime technologies. Using a growing set of predefined drag-and-drop visual
elements and templates, administrators or process owners can rapidly create user interfaces
and set granular user-access levels. Business users can customize the look and feel of their
own business space, configure the visual elements and alerting mechanisms, and even
modify the parameters of deployed processes and business applications, all without involving
IT. The ability to visually mash up capabilities from various products provides an unrivalled
holistic view into your business.
1.3.9 Additional offering capabilities

To support BPM scenarios that are implemented with the foundational offerings, IBM provides
a broad range of additional capabilities:
WebSphere Service Registry and Repository Advanced Lifecycle Edition provides
design-time and runtime repositories to manage governance and asset reuse across the
BPM life cycle.
Lotus Forms provides secure, auditable, XFDL-based forms that help automate
paper-based processes and facilitate human interactions.
Built on a business mashup framework that can be integrated with a business space,
WebSphere Portal provides a single user access to Web content and applications.
WebSphere MQ is the leading ESB messaging backbone, improving the flow of
information across an organization, supporting the information-transfer needs of BPM
solutions.
Reinforced by high quality-of-service characteristics, leading enterprise service buses
(WebSphere Message Broker, WebSphere Enterprise Service Bus, and WebSphere
DataPower) provide loosely coupled interconnectivity between service requesters and
providers, and augment the processing of messages.
WebSphere Adapters enable you to quickly service enable existing applications, ERP, HR,
CRM, and supply chain systems.
1.4 Unifying focus areas across WebSphere Dynamic Process

Edition
The integrated capabilities of WebSphere Dynamic Process Edition enable key BPM value
propositions.
1.4.1 Linking strategic intent to processes

Improving business processes is most successful when guided by a clear understanding of
the goals, requirements, priorities, and organizational capability of the business. WebSphere
Business Compass (and IBM BPM BlueWorks) enable SWOT (strengths, weaknesses,
opportunities, threats) analysis and links to associated actions and business measures. By

linking strategic priorities to processes that are owned by or affect specific parts of your
organization, you establish traceability from the boardroom to process execution to ensure
business success.
1.4.2 Workflow support

People play a fundamental role in many processes. WebSphere Dynamic Process Edition
provides support across the BPM life cycle to enable human activities. Businesses define
human tasks (and any accompanying forms and escalation policies) in their business
processes with WebSphere Business Modeler. Developers implement and deploy human
tasks with WebSphere Integration Developer, and manage active human tasks with
WebSphere Process Server. In WebSphere Business Monitor, business leaders use custom
dashboards to assess workload across a team, assign tasks to team members, and take
action to optimize business performance.
1.4.3 Business rules and policy support

Many factors often determine the course of action that is chosen in a process. WebSphere
Dynamic Process Edition provides richer support for defining dynamic behavior with business
rules and policies. With WebSphere Business Modeler, business analysts define business
rules tasks and logic, and then generate IT artifacts that seamlessly integrate with
WebSphere Integration Developer for implementation. To keep pace with rule changes in the
business environment, WebSphere Process Server provides business space management
capabilities to dynamically modify rules and schedules. ILOG extends this rules capability
with enterprise-wide business rules management. For rapid policy definition, simulation and
management, WebSphere Business Services Fabric enriches the ability to express and
bundle policies and enables maintaining the policy life cycle to be distinct from the related
processes.
1.4.4 BAM enablement

Business leaders need operational and strategic insight into how the business is running so
that they can make well-informed and timely decisions. Business activity occurs on a broad
range of systems. A true BAM environment factors in events from broad heterogeneous
environments to reflect the big picture. In response, the reach of WebSphere Business
Monitor extends to receive events from WebSphere Process Server, WebSphere Message
Broker, FileNet Business Process Manager, WebSphere MQ Workflow, and a wide selection
of enterprise information systems (EISs) using WebSphere Adapters.
1.4.5 Accelerated time to value

Getting solutions up and running quickly is necessary to respond to business demand and
change. The development environments for the IBM BPM portfolio continue to be enhanced
to provide more enriched predefined assets, templates, service repository support, code
generation capabilities, and overall improved usability. In addition, the tools are synchronized
so that the roles can quickly and effectively work together. To achieve quick success and then
build incrementally, IBM provides a methodology that outlines how to build and deploy
LOB-driven, human-centric solutions within 60 days in the IBM Redbooks publication BPM
Solution Implementation Guide, REDP-4543.

1.4.6 Improving business and IT collaboration
BPM is a discipline that brings together business expertise and IT capability. Providing a set
of technologies that enables these two areas to collaborate on defining, building, and
managing business process solutions unleashes the power of the enterprise to win in the
marketplace. Roles in both business and IT are empowered to self-sufficiently make their
contributions.
1.5 Building on open standards

Given the heterogeneous nature of many client IT infrastructures, enterprises look for
technology that provides maximum flexibility. Industry and technology standards offer open
flexibility and safeguard IT investments.
IBM actively participates in several standards bodies (shown in Figure 1-1) pertinent to BPM,
and IBM products support numerous standards.
Object Busi ness Process Modeling Notation (BPMN)

Management Busi ness Process Definition Meta-model (BP DM)
Group (OMG) Busi ness Process Maturity Model (BPMM)
Busi ness Motivation Model (BMM)
Oasis Servi ce Component Architecture (SCA)
Web Services Business Process Execution Language (WS-BPE L)
Common Base Event (CBE)
Web Services Event Format (WEF)
Web Services Notification (WSN)
Web Services Distributed Management (WSDM)
Web Services Resource Framework (WSRF)
Eclipse An open development platform comprised of extensible
frameworks, tools and runtimes for building, deploying and
managing software
W3C Various Web and XML standards, including XML, XML Schema,
XSLT, WSDL, XForms, and WS -Policy
WS I Web service interoperability profiles and testing tools
Open Ajax Open Ajax Hub
Alliance
Figure 1-1 Key standards bodies
IBM also participates in or co-leads standards initiatives for BPEL4People, WS-HumanTask,

J2EE, and event processing.
1.6 Supporting global solutions

As companies internationalize their operations and grow through mergers and acquisitions,
the ability to act as one team while operating in multiple languages is critical. IBM BPM
products provide national language support and are translated into multiple languages,
making the IBM BPM set of technologies truly global in scope.
Imagine having a team in Sydney develop your BPM solution for order tracking, server
clusters correlate order events from across the world, regional offices track operational
business activity in their native languages, and your headquarters in Madrid examine the

impact of order processing on the companys overall strategy. Global companies require
global solutions.
As an international company, IBM understands and operates in a global environment. The

map in Figure 1-2 highlights the IBM product development laboratories where the BPM
products are designed, implemented, and tested. Moreover, IBM BPM service specialists are
located in all geographies. From Beijing to Burlingame, IBM is investing in BPM.
Figure 1-2 IBM Development Lab locations for BPM
1.7 Summary
WebSphere Dynamic Process Edition demonstrates its full value when harnessed to solve
complex integration challenges, bringing the LOB and IT departments together. The complete
set of capabilities follows a consistent set of standards and underlying architectures to ensure
that business users can effectively represent the business, that developers can properly
reflect the business intentions when implementing solutions, and that administrators can
easily manage, scale, and administer end-to-end business processes. WebSphere BPM
enables you to work smarter.

2
Chapter 2. BPM interaction with Business

Space powered by WebSphere
Business process management (BPM) interacts with role-based business space so that
business users can perform these tasks:
Assess, collaborate, and take action on running the business
Rapidly create and customize user interfaces
Accelerate development with predefined templates and components
Set granular user-access levels
Modify parameters of deployed processes and business applications, without involving IT

2.1 Introduction
An integral aspect of a BPM solution is the ability of various business users to collaborate to
capture and drive business process improvements, as well as interact with deployed
processes to ensure optimal business performance. Business solution developers, users, and
administrators each play a role in defining, executing, or maintaining the business. Business
solution developers require a robust set of tools to rapidly build business process solutions.
Users need to be empowered to customize and improve their experience and respond to
shifting business needs.
Business Space powered by WebSphere provides a holistic

user interface framework and a set of configurable assets,
A browser-based
providing first-class integration with the IBM BPM runtime Web 2.0 user
technologies. Business Space powered by WebSphere is interface for
bundled with WebSphere Process Server, WebSphere
Business Monitor, WebSphere Business Compass (formerly business process
known as WebSphere Business Modeler Publishing Server), solutions
WebSphere Business Services Fabric, FileNet Agile ECM,
WebSphere ESB, WebSphere Business Events, and WebSphere Service Registry and
Repository. Business Space powered by WebSphere is also used as the front end to BPM
Blueworks, which is the free online on-ramp to IBM business process management. For more
information about BPM Blueworks, go to this Web page:
https://apps.lotuslive.com/bpmblueworks/
2.2 Common user interface infrastructure

Business Space powered by WebSphere is a browser-based, Web 2.0 user interface for
business process and IT solutions, enabling users to interact with business processes and IT
solutions wherever they are. Using a business mashup paradigm, you can combine visual
capability and diverse information sources into an integrated user experience. Business
Space powered by WebSphere delivers pre-integrated visual components, enabling a
seamless user experience across the IBM BPM portfolio.
2.2.1 Business Space powered by WebSphere concepts

Business Space powered by WebSphere is built on the following foundational concepts:
Widget
A single, configurable graphical user interface pane or view. A widget is an embeddable
component that can produce and consume events and interact with other widgets. Multiple
instances of the same widget can be on the same page, each with a different
configuration.
Page
A collection of widgets that are organized by a layout of sections, each containing one or
more widgets. A business space can generate a URL link to a specific page, which can be
provided to other users so that they can more quickly access that page.
Palette
A collection of available widgets that can be used to populate the page layout sections,
typically through drag-and-drop actions. Widget lists are organized into categories and
can be filtered for quick selection. The set of widgets shown reflects the contributing

products that have been installed. As more products are installed, more widgets become
available.
Business space
A collection of pages that are organized under tabs. The scope of a business space
typically represents a view into a BPM solution. Unrelated solutions can be placed in
different business spaces. A business space can be created in the following ways:
From an empty business space shell
Using a pre-configured template
Copying or importing an existing business space
You can easily switch between different business spaces that you have access to. Figure 2-1
shows a typical business space.
Banner
Page tabs
Widget palette
Widgets
Figure 2-1 A typical business space
2.2.2 Creating your own business space and pages

Users have different solution needs, so they often need the ability to customize the user
interface to suit those needs.
The layout or organization of widgets on a page can take one of several patterns (shown in
Figure 2-2 on page 14). You can select the page layout when you create the page, or you can
change the layout of an existing page to suit your needs. Widgets can be resized and
re-arranged to suit viewing preferences.
Chapter 2. BPM interaction with Business Space powered by WebSphere 13

Figure 2-2 Business space page layouts
After you have selected a layout, adding widgets is easy. When you edit a page, a widget
palette is presented to you (shown in Figure 2-3). You can select a widget and place it on a
page. You can also filter widgets by category to help you find the widget that you are looking
for much more easily.
Widget
category filter
Widget palette
Widgets
Figure 2-3 The Business Space powered by WebSphere widget palette filtered by category
You can configure fixed widget details, such as display

details and page and widget titles, so that they have more
Dynamically
meaning in the context of your solution (shown in Figure 2-4 configure variables
on page 15). For example, you can rename the title of the that affect running
Team List widget to Claims Department and point to specific
Web sites, spreadsheets, and presentations. processes

Figure 2-4 Configuration window for the Task Definitions List widget
To back up a business space or page configuration, you can export the business space and
page definition. This capability is also handy when someone else wants to use a specific
business space or page definition, but you do not want to share access to your business
space or page.
When information in one widget is related to information in another widget on the same page,
widgets can be configured to send and receive information between them, creating a
cooperative connection, which is also called wiring widgets. For example, selecting an alert
(retail order taking too long to fulfill) in the Alerts widget (the source) can highlight a specific
process instance (order #24680) in the Instances widget (the target). That same Instances
widget can serve as the source for a Diagrams widget, which displays instance-specific
diagrammatic details (order stuck in supply chain). You can also define custom cooperative
connections.
Another example of widget wiring is discussed in 2.3.1, BPM life-cycle stages and associated
widgets on page 20: one widget displays a form that depends on the task that you select in
another widget. Data is sent from one widget to another through an event, and the receiving
widget is automatically updated based on the information sent.
There are many ways to provide a custom user interface appearance, such as by choosing a
different business space style. Business Space powered by WebSphere comes with many
themes to choose from, which are shown in Figure 2-5 on page 16.

Figure 2-5 Styles available with Business Space powered by WebSphere
You can also replace the default login page with organizational logos and other graphics
(shown in Figure 2-6 on page 17).

Default login
window
Custom login
window
Figure 2-6 Default and custom login windows
More information about customizing the login page for Business Space powered by
WebSphere is available at this Web page:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.bspace.help
.admin.doc/customizing/customizingtheloginpage.html
2.2.3 Managing business spaces

Use the Business Space Manager (shown in Figure 2-7 on page 18) to manage your
business spaces, including creating and deleting them, adding pages to them, and setting
access controls at the page or business space level. Access to a business space does not
necessarily allow access to the constituent pages. For example, a business space owner can
set up common pages that all employees can view, other pages that only specific
departments can view, and still others with sensitive financial information reserved for
executives.

Create or import List of spaces
spaces and associated pages
Business space actions

such as theme choice,
sharing, and so on
Figure 2-7 Business Space Manager
Users can see the business spaces that they own, as well as business spaces for which they
are assigned as a viewer or editor. In this context, role-based access pertains to what can be
seen in the business space; access to underlying solution data is managed through
role-based access to the runtime components.
There are four levels of access that can be set for a user or group of users, shown in Table 2-1
on page 19.

Table 2-1 Role-based access to business space
Access Permitted actions
level
Viewer Navigates the pages in a business space and sees the widgets on a page
Editor Adds, lays out, and modifies pages in a space, including adding, removing, or
configuring widgets
Owns all pages the editor creates, even if the editor is not the owner of the space
containing the page
Performs all Viewer actions
Owner Deletes spaces

Transfers ownership
Determines who has access to a space and individual pages
Determines whether users have Viewer or Editor access
Has Owner access to every page in the space
Performs all Editor actions
Superuser Has administrative rights and Owner access to all spaces and pages
Shares access to a space or page with selected users or all users
Modifies pages and templates
Access levels can be set on groups, as well as individuals, ensuring that managing access is
scalable.
If there are specific capabilities that are not supported using

the predefined widgets, IT can create custom widgets using
Widgets are
Web authoring tools and can write the implementation in implementations of
various Web technologies, from HTML and JavaScript to the iWidget
Flex. Widgets are implementations of the iWidget public
specification, which is based on open Web formats (such as standard
HTML, XML, and JavaScript). IBM Rational and
WebSphere Integration Developer tools provide an authoring environment (editors) for
working with HTML and JavaScript files directly and for packaging that Web content into a
Web archive for straightforward deployment.
2.2.4 Saving time with pre-built business space templates

To create a business space faster, use the pre-built templates. Each template includes pages
and widgets that are used in typical BPM scenarios. Because BPM scenarios are both
product specific and cross product in nature, the templates include widgets from the various
contributing products. For example, the Managing Business Performance template
seamlessly integrates widgets from both WebSphere Process Server and WebSphere
Business Monitor to provide business measure insights that guide required actions. The list of
available templates is extensive. For more information about available templates, see
Business Space powered by WebSphere at this Web page:
.framework.scen.cross.doc/overview/learningtousetheavailabletemplates.html
As the business environment grows its use of business spaces, a superuser might choose to
create additional custom space templates by converting proven business spaces into
templates.

2.2.5 Integrating with other user interface frameworks
Business Space powered by WebSphere can also be used in other user interface frameworks
from IBM, such as IBM Mashup Center and WebSphere Portal. Business Space powered by
WebSphere uses IBM Mashup Center for its foundation, and, as a result, individual spaces
can be published to IBM Lotus Mashup Center and you can add widgets from IBM Lotus
Mashup Center into Business Space powered by WebSphere.
There are many advantages to integrating IBM Lotus Mashup Center and Business Space
powered by WebSphere. Perhaps the most significant is the ability to create dashboards from
various data feeds, not just IBM BPM products. You can also create custom widgets in the
IBM Lotus Mashup Center framework without coding, to complement the built-in widgets from
Business Space powered by WebSphere.
WebSphere Portal and Business Space powered by WebSphere can also be integrated.
WebSphere Portal is a premier enterprise-level user interface, providing mature, stable, and
scalable technology. For years, WebSphere Portal has provided clients with a solid foundation
on which large Web portals are created and managed. WebSphere Portal also boasts many
portlets (which are analogous to widgets in the Web 2.0 world). Portlets can serve as the
front-end to many J2EE applications. WebSphere Portal also enables a richer, more finely
grained administration. One potential path to take is to use Business Space powered by
WebSphere to get up and running with a BPM front-end. Then, as your UI needs become
more rigorous, integrate with WebSphere Portal to manage that complexity.
2.3 Accelerate time to value

Although you can define everything about a business space, you will most likely start with
some of the predefined assets, which provide direct access to key configurable business
solution behavior. In addition, assets are included at the widget, page, and business space
level. Those template assets contain widgets from each of our products in the BPM life cycle.
For more information, see the following Web page:
.csh.widg.common.doc/reference/listofwidgets.html
Next, we discuss the pertinent widgets in each stage of the BPM life cycle and how they can
help you achieve accelerated time to value and increased agility with your business.
2.3.1 BPM life-cycle stages and associated widgets

This section discusses the BPM life-cycle stages and associated widgets.
Business process modeling and design

To start the life cycle, it is a good idea to document many aspects of your business. From that
information, processes can be further designed, measured, and optimized. WebSphere
Business Compass (formerly known as WebSphere Business Modeler Publishing Server)
provides capabilities to capture that information and the front-end is realized in widgets that
we describe here.
At the heart of WebSphere Business Compass is the Design widget, which is part of the
Business Design Widgets category (Figure 2-8 on page 21). In the Design widget, you can
create different artifacts to document your business. We will describe the main types of
documents in more detail next. For more information about WebSphere Business Compass,

see Chapter 3, Enabling BPM with WebSphere Business Compass and WebSphere
Business Modeler on page 31.
Design widget
Document
types to create
Figure 2-8 Business Space powered by WebSphere page in edit mode showing the widget palette
Let us take a closer look at some of the types of documents that you can create (Figure 2-9).
Figure 2-9 Business Space powered by WebSphere page in edit mode showing the widget palette
Strategy maps
To help you visualize strategies for your organization, you can create strategy maps to
document the strengths, weaknesses, opportunities, threats, actions, goals, and measures of
your organization and how they are linked. As you begin your process optimization journey,
you often think in these terms rather than in terms of a process although the development of a

strategy map can certainly lead to and help in the development of process maps. As you
move further along your journey, you can link other artifacts back to artifacts in the strategy
map. Figure 2-10 on page 22 shows an example of a strategy map.
Action
Strength
Goal
Strategy
Weakness
Measure
Uncategorized
Opportunity
Threat
Figure 2-10 Example of a strategy map
Capability maps
To begin implementing your strategy, document what your business does in capability maps.
You can think of capabilities as the goods or services that your business provides to your
customers, which is in contrast to processes because processes document how your
business provides these goods or services. Figure 2-11 shows an example of a capability
map.
Figure 2-11 Example of a capability map

Each box in a capability map represents a good or service that your organization provides
and can be custom color-coded to suit your needs. These capabilities can also be linked to
artifacts in your strategy maps to show how they are interrelated. You can also create
sub-capabilities within a capability. Wherever a sub-capability has been created, you see an
icon (Figure 2-12) in the capability.
Figure 2-12 Icon indicating sub-capabilities
Vocabulary
As you increase the scope and number of artifacts, you will realize that you need to
standardize words or phrases that your business uses. The vocabulary document helps you
standardize the meanings of terms, business item definitions, messages, errors, and roles
that are used in your business documents. Figure 2-13 shows an example of a vocabulary
and the different types of entries, such as term, role, business item (can be thought of as data
or information), or message, that you can have (an example of an error is not shown).
Figure 2-13 Example of a vocabulary
After you develop a vocabulary, you can use it anywhere in other documents to standardize
meanings within descriptions of artifacts (Figure 2-14 on page 24).

Figure 2-14 Searching a vocabulary
Organizational maps
You can also create your organizational hierarchy and use the organizational units as owners
of your various design artifacts, such as capabilities and strategy map components. You can
also add roles to organizational units. Figure 2-15 shows the hierarchy in an organizational
map.
Figure 2-15 Example of an organization map
Figure 2-16 on page 25 is an example of assigning organizational units ownership to strategy

and capability artifacts.

Figure 2-16 Adding owners
Process maps
Finally, after you create the foundational elements, you can create a process map. It is not
necessary to create organization, strategy, or capability maps before creating a process map,
but doing so helps prioritize process map design, especially if you are new to business
process management. An easy-to-use palette that contains standardized Business Process
Modeling Notation (BPMN) elements helps you create detailed processes (Figure 2-17).
Figure 2-17 Example of a process map
You can choose to use a simple palette to begin process development (Figure 2-18).
Figure 2-18 Simple palette

Or you can use a more complex palette (Figure 2-19).
Figure 2-19 Complex palette
In either case, you can drag elements onto the canvas, link them together, and add details.
Depending on the process artifact, you can also add roles or organization units, measures,
and links to foundational elements, attachments, service definitions, inputs, and outputs.
Now, because all that is required is a Web browser, adopting BPM is much easier and quicker
for analysts.
Human interaction and collaboration

After an initial iterative round of process development with business analysts, the process
models can be made available to a wider audience for review and feedback. The process
models are published (details in Chapter 3, Enabling BPM with WebSphere Business
Compass and WebSphere Business Modeler on page 31), and users are granted permission
to view and comment on process models in Business Space powered by WebSphere using
the Draft Artifacts widget, which is part of the Reviewing category. That feedback is
consolidated and used to further refine the process model (Figure 2-20).
Published process
Displaying multiple
comment subject lines
Indicates comment
Figure 2-20 Example of a Process Draft Review page
Running processes
When all the feedback has been gathered and the process agreed to, the next step is to
deploy and start running the process. Again, Business Space powered by WebSphere
widgets are involved. There are quite a number of widgets that are associated with running
processes, but we will focus in on the main widgets to start and run a process that involves
human interaction.
There are many ways to start a process. One way is to start the process from the Task
Definitions List widget, which is part of the Human Task Management widget category. When
starting a process that involves human interaction, a form (which is generated and refined as
part of process development) is displayed in which a user can enter information. That form is
displayed in the Task Information widget, which is part of the Human Task Management

category. The widgets are wired together so that the task that is selected in the Task
Definitions List sends data to the Task Information widget and the Task Information widget
displays the appropriate form for the selected task.
Another widget that can help is the Diagrams widget, which is under the Business Monitoring
category. The Diagrams widget displays a graphical representation of a process. Within the
context of monitoring a process instance, you can show the path in the process that the
instance took as well as where the process currently is in the process. Figure 2-21 shows an
example of a human interaction space.
Process and Tasks widgets Task Information widget
Diagrams widget
Figure 2-21 Example of a human interaction space
Business activity monitoring and analysis

Now that you have a process running, you likely want to measure your process to ensure that
you are tracking towards the strategic goals that were outlined earlier. In the following section,
we present an overview of monitoring capabilities in Business Space powered by
WebSphere. For more information about business activity monitoring, see Chapter 5,
Enabling BPM and BAM with the WebSphere Business Monitor on page 97.
A key aspect of WebSphere Business Monitor is its ability to show real-time information in a
visually compelling manner. Information is collected for each process instance and is
aggregated for Key Performance Indicators (KPIs), dimensions, and reports. Many widgets
are involved, namely the Instances, KPIs, and Reports widgets, which are found under the
Business Monitoring category (Figure 2-22 on page 28).

Figure 2-22 Example of the Business Monitoring widget palette
Each process flow is an instance, and those instances can be shown in the Instances widget.
Individual process measures can be displayed and the display can be customized, filtered,
and sorted to your specifications so that you see only what is relevant to your monitoring
needs (Figure 2-23).
Figure 2-23 Example of the Instance widget with process measures
As information is collected from individual instances, that information can be aggregated and
reported upon in numerous ways. One way is by using the KPI widget. A KPI is a quantifiable
measure designed to track one of the critical success factors of a business process.
Examples of KPIs are average, minimum, maximum, sum, or a calculation (as shown in
Figure 2-24 on page 29). KPIs also include a target (the white bar in the gauge) and an
infinite number of ranges, all of which you can define in Business Space powered by
WebSphere.

Figure 2-24 Example of the KPI widget
Other types of aggregation include information over time and by dimensions. You can think of
dimensions of aggregates by type, such as sales for each location. The Reports widget
displays this data. For example, Figure 2-25 shows a business weeks worth of data broken
out daily by a dimension. The dimension can be anything that you need it to be, such as
location (country, city), division, or product type. With the flexibility of dimensions, you can
perform powerful analysis in your Web browser.
Figure 2-25 Example of the Reports widget
2.4 Summary
With a glimpse into some Business Space powered by WebSphere features, we have come
full circle in our BPM life cycle. We have demonstrated how Business Space powered by
WebSphere is the face of that life cycle using various widgets in the IBM BPM suite. Business
Space powered by WebSphere facilitates your journey through business process
management by providing a consolidated user interface for WebSphere Business Process
Management and enabling key business process management scenarios for various
business users to effectively collaborate and run the business.

3
Chapter 3. Enabling BPM with WebSphere

Business Compass and
WebSphere Business Modeler
You can enable business process management (BPM) with WebSphere Business Compass
and WebSphere Business Modeler, which together help you perform the following tasks:
Document strategies, capabilities, vocabularies, organizations, collaborations, services,
and high-level processes
Define human-centric business processes, integrated with forms and data
Start modeling faster using pre-built assets, shared assets, and services
Simulate, optimize, and test processes before implementing them
Collaborate as a team to define, review, and share processes
Generate the baseline for process implementations and a clean handoff to IT

3.1 Introduction
Traditionally, departmental and functional area managers have requested that procedural
manuals be defined and disseminated across the enterprise. Defining processes was itself a
long, painstaking process. IT assistance was typically required to automate specific
numeric-intensive tasks, but the business managed the overall process.
As IT systems evolved, IT departments took on more responsibility for managing various

aspects of process definition. In some cases, processes still dominated by manual tasks and
paper were orchestrated as workflows. Many IT departments hired business-savvy IT staff
who took existing procedural documents and interviewed subject-matter experts to define
these workflows.
Today, many IT departments continue to manage the definition Improve the

of business processes, but they realize that they need to
improve the collaboration between business and IT. Business collaboration
processes are best understood by the business, which needs between business
the tools, methodologies, and assets, coupled with its own
domain expertise, to define what the current business and IT
processes are, and what is required to improve them. The
business needs to leverage reusable service assets in process definitions, and review
process definitions with a broad team.
With WebSphere Business Compass, many people can collaborate to document their
business and design high-level processes in a Web-based environment. WebSphere
Business Compass can serve as starting point for process optimization in WebSphere
Business Modeler and process deployment in WebSphere Process Server. In addition,
WebSphere Business Modeler can publish processes to WebSphere Business Compass for
feedback from a wide range of stakeholders.
In addition to enabling business analysts to define business processes, WebSphere Business

Modeler puts powerful process simulation capabilities in the hands of business analysts to
assess optimal task flows and resource use. The results of various what-if scenarios can be
compared to identify how they fare on task durations, costs, human involvement, resource
usage, and other factors. Your business can achieve significant cost savings by determining
the best processes to implement before these process specifications are handed over to IT.
Thus, the line of business (LOB) plays its rightful critical role in enabling BPM.
3.2 Collaborate on strategic intent

Process optimization does not always start with documenting a process. In fact, many people
do not think of their business in terms of processes, but rather as a set of strategies and
capabilities shown with organizational charts. WebSphere Business Compass allows you to
capture these and more. Then, you can use these resources to document your processes.
3.2.1 Strategy, capability, vocabulary, organization, and process maps

Chapter 2, BPM interaction with Business Space powered by WebSphere on page 11
provides details about strategy, capability, vocabulary, organization, and process maps. See
2.3.1, BPM life-cycle stages and associated widgets on page 20 for detailed descriptions.
To summarize, you can document your business strategies by creating a strategy map (as
shown as an option in Figure 3-1 on page 33), cataloging goals, actions, measures,

strengths, weaknesses, and so on in a free-association form. Next, you can record the
capabilities of your business, such as what goods, services, or functions your business
provides. By creating a vocabulary in a vocabulary map, you can standardize the meaning of
roles, data, words, phrases, and acronyms. You can search for and use vocabulary entries in
names or descriptions within WebSphere Business Compass. You can also enter in your
organizational hierarchy in an organization map and use it to assign the responsibility of each
task when you document your processes. Finally, you can document your business processes
in process maps. This usage pattern offers insights into the range of ways to document your
business with WebSphere Business Compass.
Figure 3-1 Strategy, capability, vocabulary, organization, and process maps in WebSphere Business
Compass
Next, let us discuss other types of documents that you can create in WebSphere Business
Compass.
3.2.2 Collaboration diagrams, service documents, and form documents

As you map processes, you might require those processes to interact with the outside world.
You can show this interaction by creating collaboration diagrams. Each of the processes is
placed in a pool where you can choose which elements within the process are public touch
points, as shown in Figure 3-2. These touch points are displayed in the pool and represent
points in the processes that exchange information. This exchange is represented as a
message between processes.
Figure 3-2 Example of a collaboration map
Chapter 3. Enabling BPM with WebSphere Business Compass and WebSphere Business Modeler 33
Service documents present a business-friendly view of the IT services that are available to
enable processes, and include information about the types of actions a service provides, as
well as the required inputs and outputs for each action, as shown in Figure 3-3. These inputs
and outputs are reusable Web services in keeping with service-oriented architecture (SOA)
principles. Many times, you might want to document these services first before developing
your process maps (a bottom-up approach) versus creating a process map while generating
the service documents (a top-down approach). Either approach is valid. You might prefer a
bottom-up approach if you already have a number of Web services in WebSphere Integration
Developer. You can import those services into the WebSphere Business Compass repository
for reuse in process maps.
Figure 3-3 Example of a service document
Lastly, there are form documents where you can create forms using a palette and canvas, as
shown in Figure 3-4 on page 35. Later, you can associate forms with tasks in a process
(bottom-up approach) to enable users to walk through a process and see what forms are
involved at each step, enabling a deeper understanding of how the process is performed.
Similarly you can create forms as you create a process (top-down approach). Either approach
is valid. Another way to create a form is to use an image file of a form that will be used (a .gif,
.jpg, jpeg, or .png file) rather than creating one using the palette and canvas.

Figure 3-4 Example of a form document
When you have captured your business intent in WebSphere Business Compass, you can
apply more sophisticated analysis and capabilities in WebSphere Business Modeler, such as
process simulation and process automation. The work completed in WebSphere Business
Compass can be imported directly from the WebSphere Business Compass repository into
WebSphere Business Modeler.
3.3 Facilitating modeling for documentation

Business analysts often model their business processes to optimize or implement them. At
other times, they model them simply for documentation purposes. In either case, you need to
understand where you are before thinking about where you need to go. WebSphere Business
Modeler includes a growing set of capabilities that lets you visually highlight the various
features of your processes and makes printing and reporting process diagrams and
information easier.
3.3.1 Customizable process diagrams

WebSphere Business Modeler provides the flexibility to depict a range of process information
visually: from incredibly simple process flows to semantically rich diagrams (Figure 3-5 on
page 36). The modeling modes provide added flexibility to hide or show process complexity
and perform constraint checking.
Figure 3-5 WebSphere Business Modeler palette and Process editor
For standards-compliant process visuals, leverage the IBM continues to

Business Process Modeling Notation (BPMN) style process
elements. IBM continues to play a leading role in the OMG play a leading role in
standards committee in defining BPMN, working with other the OMG standards
BPM vendors to achieve consistency in business process
notation and semantics. committee in
defining BPMN
The workflow in Figure 3-5 can be enriched in many
different ways. Consolidated diagram display settings can be toggled on or off to display
various levels of detail (shown in Figure 3-6 on page 37), depending on what stage you are at
in defining your process and who your audience is. For example, you can more effectively use
color by not only coloring process elements by a particular characteristic (for example, by
role), but also provide a color legend.

Figure 3-6 Display and print settings
You can change the image shown in a visual element to more accurately reflect your process
semantics (shown in Figure 3-7).
Figure 3-7 Adding an image to display with an element
When viewing process diagrams that include local subprocesses, you can understand the
relationship of the parent process to a local subprocess by displaying the subprocess in
context (Figure 3-8), simply by opening up the subprocess in place. You can also easily move
a process element into a local subprocess or loop, or view a subprocess in a new page.
Figure 3-8 Expand subprocess in place
3.3.2 Facilitate printing and reporting

To share model information among the team, business analysts often generate listings of
model information, print posters of their models, or generate print-ready versions of their
models. WebSphere Business Modeler simplifies the sharing of model information by
providing robust printing and reporting features.
When printing with limited space, choose the Compact Diagram option (shown in Figure 3-9)
to bring diagram elements closer together (without overcrowding). Youll notice a difference
when compared to a diagram that has auto-layout applied to it, which straightens out the
diagram but leaves ample room to continue inserting new model elements.
Figure 3-9 Compacting a diagram

Not only can users easily show page breaks and specify that visual elements be automatically
moved off of page breaks, but they can automatically have page annotations added to printed
report pages to easily locate where a portion of the process diagram picks up in the printed
report. The print format (poster, report), paper size, and scaling options that are shown in
Figure 3-10 provide the consolidated flexibility to get exactly the required output format.
Figure 3-10 Print options
To consolidate the specification of report details, a report template wizard (Figure 3-11)
guides users through the process of choosing a report output format, source, and report
template so that they can generate and print reports in seconds.
Figure 3-11 Report template wizard
3.4 Growing the role of business
With WebSphere Business Modeler, business analysts have an easy-to-use desktop tool that
helps them formalize rigor into the definition of business processes as tasks (including human
tasks and business rules tasks), forms, decisions, business items (business-oriented data
objects), subprocesses, resources, and repetitive task loops. These elements constitute the
foundation for many business processes, and many of them mirror the capabilities provided to
IT developers in WebSphere Integration Developer but expose the element characteristics
that are relevant to business analysts.
To enable business analysts with additional capability in defining business processes,

WebSphere Business Modeler provides enhanced capability to define and simulate
human-centric processes.
3.4.1 Human-centric processes and forms

Complex process flows are often a combination of automated The relationship
tasks and human tasks. In fact, many organizations begin the
journey of understanding their manual business processes by between user
defining human workflows. Defining a business process interfaces, data,
precisely determines how these activities are choreographed
and identifies activities for future automation. WebSphere and process flows
Business Modeler provides first-class support for defining is natural
human tasks and the interaction of these tasks with business
items and forms.
The relationship between user interfaces, data, and process flows is natural (Figure 3-12 on
page 41), and any of these elements can be used as the starting point for modeling:
Process approach - First, define the task elements of the process flow, including the
human tasks and the connections between them. Then, iteratively begin adding and
associating forms, data, and other elements.
Data approach - First, define the business items. Lay out the process-control flow, and add
a data flow by way of business items as task inputs and outputs. Then, generate a
structured form from a business item. For example, generate an Invoice form from the
attributes of the Invoice business item.
User interface approach - First, define the form, perhaps by scanning a long-standing
paper form that should be rendered electronically, and then converting the PDF document
to a Lotus form. Based on the form, create several human tasks and business service
objects that interact with the form. For example, from the Invoice form, generate human
tasks for Complete invoice, Review invoice, and Approve invoice.

Figure 3-12 A WebSphere Business Modeler model integrates the process flow, data, and user interface
WebSphere Business Modeler provides integrated support for Lotus Forms. You can import
an existing form (for example, from WebSphere Business Compass) or create one with the
integrated Lotus Forms Designer. You can start with the Standard Designer perspective,
which gives you all the capability that you need to build simple forms, and then move on to the
Advanced Designer perspective to take advantage of complex functions, such as forms data
modeling and XPath editing.
Regardless of your starting point, it is important to keep your Keep your process
process data and your form user interface in sync. If you have
an associated business item and form, and the business item data and your form
is subsequently updated, it is now out of sync with the user interface in
corresponding form. WebSphere Business Modeler
automatically detects this situation and helps you take action sync
to synchronize the process data and form (Figure 3-13).
Figure 3-13 The Synchronize Form window
Forms serve not only as the interface to human tasks within a process, but as the interface to
the process itself. Associating a form with a process provides a consistent user-initiated
mechanism to start a process.
Just as the LOB can save significant time, costs, and effort by leveraging the simulation
capabilities of WebSphere Business Modeler to determine the efficiency of process flows, you
can also simulate a process storyboard, as seen through a sequence of form preview screens
(Figure 3-14). By stepping through the forms that are associated with human tasks, the
business analyst gets an early perspective on what the user experience will be.
Figure 3-14 Simulating a process storyboard
As you simulate the processing of each human task, the integrated Lotus Forms viewer
shows the associated form, and you can interact with that form to ensure that it behaves as
expected, without assistance from IT.
3.4.2 Interactive process design

Business analysts can also quickly and easily test Test user-centric
human-centric processes in the context of a real test server,
using interactive process design. After IT (essentially acting as processes in the
a service provider to the LOB) sets up WebSphere Process context of a real
Server (and WebSphere Business Monitor, if applicable),
business analysts can deploy a process and monitoring
test server
solution, without involving IT. When the business analyst
indicates that a process (developed in WebSphere Process Server mode) can be tested on
the server (Figure 3-15 on page 43), the requisite implementation artifacts are generated and
deployed to a preconfigured business space.

Figure 3-15 Process context menu
The business analyst can then test and evaluate the process and business measures in a test
sandbox (shown in Figure 3-16 on page 44). By empowering the LOB to readily assess the
effectiveness of its processes, this powerful capability reduces back-and-forth interactions
between the LOB and IT departments and accelerates process deployments.
Figure 3-16 Business spaces used for process testing
Interactive process design is best suited for Assess how deployed

human-centric processes, enabling business analysts
to log on as one or many roles to test task flow, form business measures
interactions, escalations, subprocesses, and business change as process
rules. By leveraging the pre-built business measure
metric templates in WebSphere Business Modeler, instances run
business analysts can also assess how deployed
business measures change as process instances run and use business services that reside
in a service repository (for example, WebSphere Service Registry and Repository), if that
repository is registered with the test server. For services that still need to be implemented as
back-end service calls (for example, using adapters to access third-party services), business
analysts can temporarily use a human task to ensure that the process task flow is correct.
Services that reside in a service repository can be accessed if that repository is registered
with the test server.
After logging in to the deployment environment for the test server, an external Web browser
opens with the pre-configured business space, which includes many widgets that help
business analysts to assess the BPM solution (shown in Figure 3-17 on page 45) by
performing the following tasks:
Using the Start Process Instances widget, which launches process instances of deployed
processes, start the process instance.
Using the Lotus Forms view, fill in and submit forms that are associated with human tasks.
Using the Claim Available Tasks widget, see which tasks the current user can claim.

Using View Process Instance History widget, view the input and business rules values that
were passed to process instances that have already run.
Using the Change Parameter Value for Business rules widget, view and change the
dynamic behavior of specific evaluation activities to assess the impact on process
behavior.
Using the Trace Process Execution widget, see the process diagram and the process
execution path as process instances run.
Using the Process execution trace and data values widget, see a step-by-step trace of
each process instance activity, including activity output data values.
Using the Business Measures page (which is also generated for you), see Key
Performance Indicators (KPIs), dimensional analysis, and instance metrics for the
processes you run.
These business space widgets provide a holistic view of what the business analyst needs to
test the process. A production-level deployment environment likely does not contain this
broad scope of widgets. Of course, business analysts can remove or add widgets to their test
environments.
Figure 3-17 Typical activity flow when testing a process with Interactive Process Design
As they iteratively test processes with the interactive process design capability, business
analysts might see technical issues arise that are beyond their ability to handle. For example,
there might be problems with the test server setup, client configuration, or generated process
artifacts. In such cases, business analysts need a quick way of bringing in IT and providing
them with the necessary information to perform effective problem determination. Either from
within the business space or in a deployment window for WebSphere Business Modeler, the
business analyst can select Request Help from IT (shown in Figure 3-18 on page 46), which
generates a ZIP file that IT can import into WebSphere Integration Developer. The ZIP file
contains traces, server logs, and the generated implementation artifacts for the process.
Figure 3-18 Requesting help from IT to resolve deployment issues
3.5 Accelerating time to value

Although WebSphere Business Modeler provides a wealth of capabilities that help you design
your new process models, having access to existing assets accelerates time to value.
Industry accelerators provide direct industry-specific value for various industries, often
aligned with specific industry standards and leveraged by IBM Global Services.
Using predefined assets that are available either directly within the product or that are
available from the IBM SOA Business Catalog provides the following benefits:
Improved time to value by helping solution developers do The SOA Business
their jobs more effectively
Catalog is a
Improved time to market by quickly providing relevant
solutions comprehensive
Reduced development costs by reducing churn on online resource
resources
Contained operating costs by reducing deployment time
3.5.1 SOA Business Catalog

The service-oriented architecture (SOA) Business Catalog is a comprehensive, online
resource for ready-made business models (or predefined assets) supplied by IBM and IBM
Business Partners that have been validated for enablement on IBM SOA products. The
catalog (shown in Figure 3-19 on page 47) holds thousands of assets, including adapters,
Web services, process models, and plug-ins that are regularly updated to keep pace with
business, technical, and regulatory changes and continually help you build your SOA
solutions. Third parties (for example, IBM Business Partners) can register licensed assets in
the catalog. The catalog provides an asset overview and details on where to get the asset
and accompanying documentation.

To access the SOA Business Catalog, go to this Web page:
http://www-304.ibm.com/jct09002c/gsdod/weblistfilter.do?prog=RFSOA&tab=0
You can search the catalog in many ways, including by using the following criteria:
Asset type (code, data, model, or tools)
Business need (for example, CRM, ER planning, business integration, or supply chain)
Industry focus (over 20 industries to choose from)
IBM SOA foundation product
Figure 3-19 IBM SOA Business Catalog
IBM provides assets that are based on a long history of developing domain expertise. For
example, assets that are associated with the Information Framework for Financial Markets
draw on over 100 person years of modeling and analysis work with the financial services
industry. Assets help you with such processes as post-trade processing and reporting,
account opening, know-your-customer initiatives, and regulatory compliance, typically
reducing analysis time by 40% and significantly accelerating the time that it takes to secure
stakeholder approvals.
3.5.2 APQC process classification framework

To jump-start solution development, WebSphere Business Modeler supports a KPI library
based on the process classification framework from the APQC, a member-based nonprofit
organization that provides benchmarking and best practices to over 500 organizations
worldwide. APQC Process Classification Framework (PCF) organizes operating and
management processes into 12 enterprise-level categories and more than 1500 processes
and associated activities (Figure 3-20 on page 48).
Figure 3-20 KPI library based on APQC classification framework
3.5.3 Growing a repository of assets

As the LOB teams develop various global tasks, business items, roles, and other project
resources, the opportunities for reuse grow. And more than simply leveraging existing assets,
organizations can mature a business process modeling center of excellence that encourages
consistency and best practices, under effective governance policies.
To help foster asset reuse, WebSphere Business Modeler Mature a business

has first-class integration with Rational Asset Manager
(shown in Figure 3-21 on page 49), a repository that process modeling
enables teams to store approved and completed assets. center of excellence
(In contrast, a team development system, such as
Concurrent Versions System (CVS) or Rational
ClearCase, provides a development-time repository for teams that collaborate on projects.)
This server-based content management system can be accessed across a broad
organization, with appropriate levels of access so that teams can view various sets of assets.
You can search through the repository using multiple filters to quickly locate the required
assets.

Figure 3-21 Visually browsing Rational Asset Manager
The power of Rational Asset Manager becomes evident through the rich set of metadata
details that can be associated with each asset. In addition to the asset name, you can see the
version number, contributor details, custom labels, tags, and related assets. As an asset
evolves, you can choose to upgrade to a more current version, understand how it is used, and
even see how others have rated it.
For a given asset, it is important to understand the A rich set of

relationship that this asset has to both assets that it requires
and assets that depend on it (shown in Figure 3-22 on metadata details
page 50). Understanding these relationships will influence can be associated
what related assets you might need to download, as well as
help you understand the impact on other assets if you update with each asset
this asset.
Figure 3-22 Visualizing asset dependencies
The built-in notification mechanism of Rational Asset Manager enables you to subscribe to
receive e-mail regarding assets about which you want to be updated. When passing
completed process model elements between WebSphere Business Modeler and WebSphere
Integration Developer, the integration developer can use this notification mechanism to be
alerted to assets that are now ready for implementation. When the business analyst adds new
or updated assets to the asset repository, the business analyst can indicate that project
interchange files must be generated for WebSphere Integration Developer or WebSphere
Business Monitor. In fact, if the integration developer publishes the WebSphere Integration
Developer module and the monitor model at the same time, the monitor model will be
customized to monitor the Business Process Execution Language (BPEL) process
implementation.

3.5.4 Leverage assets defined in WebSphere Business Services Fabric
WebSphere Business Services Fabric enables business analysts to define composite
business applications, business services, and business vocabularies to support extensible
solutions that can accommodate changing business conditions. If the target runtime
environment is WebSphere Business Services Fabric, being able to leverage existing assets
(that had been defined in the business space) in WebSphere Modeler enables business
analysts to perform the following tasks:
Define assets details.
Leverage WebSphere Business Modeler capabilities, such as simulation, reporting, and
publishing.
Generate a baseline of implementation artifacts.
With WebSphere Business Modeler, you can import WebSphere Business Services Fabric
Repository elements (shown in Figure 3-23), which are represented as existing WebSphere
Business Modeler element types:
A composite business application is imported as one or more global processes.
A business vocabulary is imported as one or more business items or roles.
A business service is imported as a service, as well as one global process for each
service implementation variation. These global processes are empty but are associated
with the service, allowing the business analyst to specify the details of the service
capability and enabling the business analyst to define alternate process flows for the
different business service variations.
Figure 3-23 Importing WebSphere Business Services Fabric Repository assets
Consider the case when a process model includes a global task or service that always
performs the same action, regardless of business context. You can replace this process
model element with imported business service extensibility, and modify existing variations
and model new ones.
When working with a process model that is targeted for implementation and deployment with
WebSphere Business Services Fabric, ensure that you are working in WebSphere Business
Services Fabric mode because this mode constrains the type of elements that can be used
and ensures that the IT tools can leverage the generated IT artifacts. In addition, a model
element can be assigned the Dynamic Assembler implementation type (shown in
Figure 3-24) so that the element is interpreted as a Dynamic Assembler Component in the IT
tools.
Figure 3-24 Specifying an implementation type as Dynamic Assembler
3.6 Collaboration
For modeling projects to be successful and to ensure that they effectively factor in the broad
organizational expertise for a particular domain, it is critical that teams be able to share
process elements and have robust mechanisms for reviewing each others work. In
WebSphere Business Modeler, business analysts can share model project data through
import and export facilities, team support (CVS, Rational ClearCase), or by sharing PDF
reports. Teams can also collaborate by sharing data across projects, making project data
available for viewing and commenting through WebSphere Business Compass, and taking
advantage of Rational ClearCase performance over wide area networks and Web-based
views. They can also generate reports in Microsoft Word format.
3.6.1 Reviewing processes with WebSphere Business Compass

With WebSphere Business Compass, process definitions and other model artifacts can be
shared across a broad organization (illustrated in Figure 3-25 on page 53). Business analysts
use WebSphere Business Modeler to publish processes (including relevant diagrams,
artifacts, and attachments) to the server, enabling subject-matter experts, process
implementers, and business analysts to collaborate on the definition of process models. After
processes have been reviewed and approved, system-of-record process models can be
published for referral across the enterprise intranet and even through a secure extranet with
business partners.
Using custom business space widgets for WebSphere

Business Compass, project administrators can grant
Enable subject-matter
users and groups access to projects and release experts, process
artifacts. For draft projects, users add comments about implementers, and
the overall process or about specific process diagram
elements (shown in Figure 3-25 on page 53). Comments business analysts to
have various attributes that enable users and project collaborate
administrators to categorize, filter, and manage
comments: comment type (problem, question, or suggestion), comment priority (high,
medium, or low), and comment status (open or closed). This consolidated commenting
system enables quicker and more streamlined project reviews. All comments can be exported
for use in quality-control records.

User
Workstation
WebSphere
Business Modeler
Publisher client
WebSphere
Business Compass
Intranet
Managers and
Consultants Employees
Executives
Figure 3-25 User context for WebSphere Business Compass
Figure 3-26 on page 54 shows a typical WebSphere Business Compass interface.
Figure 3-26 Typical WebSphere Business Modeler Publishing Server interface
3.6.2 Leveraging Excel spreadsheets

Business users are typically the process subject-matter experts in their organizations, and
they often convey their knowledge using office productivity tools with which they are familiar.
WebSphere Business Modeler provides import facilities to leverage their insights into
formalized process artifacts.
The definition of data structures often begins in spreadsheets. Predefined worksheets

(available in multiple languages) provide a prescriptive starting point for entering process data
(shown in Figure 3-27 on page 55). Business analysts can then choose to import as much or
as little from the worksheets, or work in stages. The WebSphere Business Modeler import
capability defines business items, roles and individuals, organizational units and locations,
and tasks.

Figure 3-27 Importing structured data from Microsoft Excel
3.7 Closing the gap between business and IT

Although WebSphere Business Modeler can be effectively leveraged on its own to document
and share business processes, its value in a broader BPM context becomes more apparent
when it is used with other tools to define and implement business process elements. Various
roles across business and IT are typically involved in enabling enterprise-scale projects.
Therefore, the ability to share data between tools becomes critical for smooth transitions
between roles.
WebSphere Business Modeler provides a broad range of integration capabilities, supporting

the following formats or products: Microsoft Excel, Microsoft Visio, WebSphere MQ Workflow,
Web services, XML Schema Definition (XSD), XML, Rational Software Architect (represented
in Unified Modeling Language (UML)), Rational Data Architect, Rational RequisitePro,
WebSphere Business Monitor, WebSphere Integration Developer (represented in Business
Process Execution Language (BPEL)), WebSphere Service Registry and Repository, and
FileNet Business Process Manager.
WebSphere Business Modeler and WebSphere Integration Developer share the capability to
define data maps, backwards connections, and exception outputs.
3.7.1 Data maps

As you iteratively develop your process model, you might need to integrate a new service into
the model. If the new service has a different interface than what has been passed through the
data flow, you need to map the data definitions. A data map element transforms data between
source and target to facilitate data flow. WebSphere Integration Developer supports data
maps. Therefore, if you are modeling for implementation on WebSphere Process Server,
maps defined in WebSphere Business Modeler are preserved. To avoid unnecessary
complexity when defining a business model, define complex data maps in WebSphere
Integration Developer.
Consider the case in which the first version of an order process includes a local task to check
credit. The business analyst later discovers that there is an existing service (which can be
imported from WebSphere Service Registry and Repository) that should be leveraged.
However, this imported checkCredit service requires different data input and output than is
used by the previous and succeeding tasks. Data maps bridge the gap by enabling an
existing data structure to be mapped to the interface requirements of the service (shown in
Figure 3-28).
Figure 3-28 Using data maps to interface with a service
The map editor (shown in Figure 3-29 on page 57) provides a straightforward visual approach
to define the mapping: simply connect the attributes between the source and target data
objects. This capability not only gives the business analyst added precision to specify data
object mappings, but it enables early testing of this process pattern with the Interactive
Process Design capability.

Figure 3-29 The Map editor
When working with repeating tasks, it can be more straightforward to draw a connection to an
earlier point in the process than using a loop. The WebSphere Integration Developer concept
of a cyclic flow is now available in WebSphere Business Modeler for backwards connections
(shown in Figure 3-30). Simply draw a connection back to an earlier part of the process. Take
care, however, that there is a way to get out of this loop, or it will run indefinitely.
Figure 3-30 Using a backwards connection and exceptional output
To address the handling of problems that might arise when a process runs, IT typically
defined fault handlers using tools, such as WebSphere Integration Developer. This makes
sense for IT-related exceptions, but the LOB must have a way to indicate how
business-related exceptions are dealt with and to be able to test them before implementation.
With WebSphere Business Modeler, you can import Web services that have defined fault
handlers. Alternatively, you can create fault outputs in a given task, triggered by
exception-handling criteria to generate exceptional output.
3.7.2 Implementation-ready business measures

Just as the ability to test processes is greatly accelerated with the Interactive Process Design
capability, which generates BPEL code and deploys it directly to a test server, a similar
capability is provided for business measures. You can define business measures and test
them before passing them to IT for implementation. As with business processes, you must be
in WebSphere Process Server mode to use Interactive Process Design. When Verify Process
Design is invoked, a monitor model is generated and deployed to a target-managed
deployment environment that is configured with WebSphere Business Monitor.
Your business measures (and any dependent business

measures) must be valid and error free, and either based
Define business
on a predefined template or on a fully specified calculation measures and test
expression. It might be helpful to develop and test your them before passing
business measures in stages. For example, when the
process model is relatively stable, begin by defining an them to IT for
instance metric (elapsed duration of an end-to-end implementation
process). After verifying that the correct business measure
is being rendered in the business space, define a KPI (average process duration) that
performs a function (average) on the set of aggregated instance metrics (shown in
Figure 3-31). When deployed, the KPI value changes while you iteratively complete process
instance runs.
Figure 3-31 Specifying the calculation details of a business measure
3.8 Summary
WebSphere Business Compass and WebSphere Business Modeler enable business analysts
to easily and rigorously describe business processes, accelerate process definition by using
various assets, collaborate across the organization to ensure that the processes reflect
business and IT requirements, simulate and refine them for optimal business results, deploy
and test them in a test sandbox, and effectively interact with IT for process implementation.

4
Chapter 4. Enabling BPM with WebSphere

Integration Developer and
WebSphere Process Server
You can enable business process management (BPM) with WebSphere Integration
Developer and WebSphere Process Server. WebSphere Integration Developer and
WebSphere Process Server can help you perform the following tasks:
Create agile business solutions with business rules and dynamic service selection
Leverage business process models designed by business analysts
Integrate human tasks and forms with business processes
Test and deploy BPM solutions on proven, robust runtime environments
Keep pace with industry standards

4.1 Introduction
Many clients start the business process management (BPM) journey focusing on end-to-end
process automation. The primary purpose behind process automation is to improve business
performance by automating business processes, which requires us to better understand and
formalize processes, making them more efficient.
Process automation works by streamlining processes across disjointed IT systems,

information, and human tasks, orchestrating them into an optimized process flow. Process
automation includes human workflow management capabilities to orchestrate manual tasks,
run them faster, and make them repeatable and consistent (shown in Figure 4-1). It also
includes broad process integration capabilities to connect to diverse IT systems and
information, including the use of service-oriented architecture (SOA), adapters, and other
integration techniques.
Figure 4-1 Process automation
The IBM BPM strategy relies on two complementary products to enable BPM solutions that
deliver key process automation capabilities: WebSphere Process Server to run and manage
deployed BPM solutions and WebSphere Integration Developer to design and test BPM
solution implementations.
WebSphere Process Server is a high-performance

processing engine that supports processes that meet
A high-performance
business goals. It ensures that processes designed in processing engine
WebSphere Business Modeler or WebSphere Integration built on open
Developer run consistently, reliably, securely, and with
transactional integrity. It is built on open standards and standards
deploys and runs processes that orchestrate services
(people, information, systems, and trading partners) within an SOA or non-SOA

infrastructure. Furthermore, WebSphere Process Server supports various BPM capabilities,
including processes, business rules, state machines, human tasks, and forms integration with
processes. These capabilities are built on top of a robust application server, an enterprise
service bus, and SOA underpinnings (shown in Figure 4-2).
Business
Business Human Business BPM service
State
Proces s Tasks Rules components
Machines
Mediation Dynamic
Data Relation- Busi ness Supporting
Flows Service
Maps ships Calendars services
(ESB) Selection
Service Component Business Common Event SOA core

Architecture Objects Infrastructure capabilities
WebSphere Applicati on Server ND (J2EE Runtime)
Figure 4-2 WebSphere Process Server
WebSphere Process Server orchestrates the assets of a business to form highly optimized
and effective processes, enabling a broad range of BPM scenarios involving people,
processes, and information. It is built on and contains WebSphere Enterprise Service Bus,
which includes service bus capabilities to mediate disparate services, helping to maximize
the reuse of assets wherever they are, regardless of the vendor, platform, or whether they are
built by companies themselves or provided as part of packaged applications.
WebSphere Process Server enables dynamic workflows for greater flexibility and control and,
when combined with the power of WebSphere Business Monitor, processes can be optimized
to meet changing business requirements, providing a competitive advantage.
WebSphere Integration Developer (shown in Figure 4-3

on page 62) provides a user-friendly, Eclipse-based
Accelerate the
authoring environment for end-to-end integration in SOA, adoption of SOA by
enabling integration developers to build SOA-based BPM rendering existing IT
and integration solutions across WebSphere Process
Server, WebSphere Enterprise Service Bus, and assets as service
WebSphere Adapters. Its rich features simplify integration components
and accelerate the adoption of SOA by rendering existing
IT assets as service components, encouraging reuse and efficiency. It enables rapid
assembly of business solutions by wiring reusable service components that can be
discovered from multiple locations, such as IBM WebSphere Service Registry and Repository
and IBM Rational Asset Manager.
Chapter 4. Enabling BPM with WebSphere Integration Developer and WebSphere Process Server 61
Figure 4-3 WebSphere Integration Developer
WebSphere Integration Developer enables integration developers to assemble complex

business solutions, whether processes, mediations, adapters, or code components, using
drag-and-drop technology to visually define the sequence and flow of business processes. It
is closely integrated with WebSphere Business Modeler to import models for rapid
implementation.
The integration developer has access to a wide range of functionality when authoring process
integration solutions. Models imported from WebSphere Business Modeler are automatically
translated into a set of standards-based Business Process Execution Language (BPEL)
processes and XML Schema Definition (XSD)-typed data. Alternatively, the integration
developer can code services in languages that are well suited to the business integration
domain, wire services together in the Assembly editor, and lay out the orchestration between
processes, exposing this orchestration as a service for further reuse.
4.2 A foundation for reusable assets

With BPM enabled by service-oriented architecture (SOA), you can leverage your
organizations assets to the fullest extent. Business integration developers work either

top-down (creating solutions by aggregating existing services) or bottom-up (authoring new
services and exposing them for reuse) to produce enterprise-quality software. Support for
software standards enables either development approach to be successful; lack of such
support presents several hurdles, either by requiring developers to master unfamiliar
concepts or by creating problems when integration with other vendors is necessary. IBM
addresses these challenges by supporting the Service Data Objects (SDOs), Service
Component Architecture (SCA), and Web Services Business Process Execution Language
(WS-BPEL) open standards.
4.2.1 Service Data Objects (SDOs)

Business integration developers must master different data implementations, such as
Enterprise JavaBeans (EJBs), Java Database Connectivity (JDBC) RowSets, and Java
Message Service (JMS) message objects. Because SDOs provide a consistent view of the
data with an abstraction layer for disconnected data, developers can minimize the learning
curve that is usually required to handle multiple standards. IBM supports the SDO standard
with the business object framework, which implements and extends the SDO standard with
concepts that are important to integration solutions.
The business object framework allows integration developers to easily define a generic data
model. Because the underlying technology is based on well-defined XML, it is relatively easy
to map application specific data into common formats using the IBM XML mapping tools or
manipulate that data as it flows through the main process, as shown in Figure 4-4. The XML
technology is implemented using an XML processing engine that conforms to XML standards
and uses advanced processing techniques to provide high performance with reduced
resource consumption.
Figure 4-4 The Business Object editor in WebSphere Integration Developer
Alternatively, developers can generate business object definitions from existing enterprise
assets using the External Service wizard (for example, with an existing SAP or Oracle
system) or by importing existing XML Schema Definition (XSD) files into the workspace.
4.2.2 Service Component Architecture (SCA)
The key concept behind delivering SOA solutions is that each service should have
well-defined interfaces, shielding users from implementation details so that they can focus on
the functionality that the services deliver and how that functionality relates to business needs.
IBM has joined with several other industry participants to define a standard for
component-based architecture: SCA.
SCA provides loose coupling to the endpoint implementation for services that are defined in
the business process. Integration developers can abstract endpoints further by performing
lookups through the WebSphere Service Registry and Repository. Plus, business analysts
can reuse services that were defined in WebSphere Integration Developer as black-box
implementations in WebSphere Business Modeler, providing a clear delineation between the
service producer and consumer (shown in Figure 4-5).
Figure 4-5 The Assembly editor in WebSphere Integration Developer
Each of the main programming models offered in WebSphere Integration Developer is

represented as a SCA component at development time (human task, Java, process, rule
group, or state machine). The key advantage to using an SCA component is that the interface
is separate from the implementation; therefore, an implementation strategy can change
without requiring the interface that is defined in the SCA component to change.

IBM provides a highly optimized and high-performing SCA processing environment that runs
SCA applications with transactional integrity. The SCA processing environment is built on top
of the WebSphere Application Server infrastructure (using the J2EE programming model) to
provide other important characteristics, such as high availability and scalability, that are
suitable for enterprise BPM and SOA solutions. WebSphere Process Server SCA modules
can also interoperate with Open SCA services that are developed on Rational Application
Developer and hosted by the WebSphere Application Server feature pack for Service
Component Architecture.
When development is complete, the integration developer can extend the system by importing
services or making new services available for reuse. The WebSphere Integration Developer
toolset seamlessly represents all data as SDOs, reducing programming complexity.
4.2.3 BPEL choreography

The BPEL programming language provides a rich model for orchestrating multiple service
invocations with more complex business logic. The base language defines support for
multiple invocation paths, variables, and complex compensation or fault handling when errors
are encountered. The integration developer uses drag-and-drop techniques (shown in
Figure 4-6) to create business process definitions rapidly and efficiently and meet the
changing needs of the business.
BPEL a ctivities
Services that inter act with
BPEL process the BPEL proces s
Figure 4-6 The Process editor in WebSphere Integration Developer
IBM largely supports Version 2.0 of the WS-BPEL standard, as well as concepts introduced
by two extensions to the WS-BPEL standard: BPEL for Java and BPEL4People. BPEL for
Java allows integration developers to define complex business logic inside their processes
using the Java programming language. BPEL4People defines a mechanism for integration
developers to include human tasks in the process.
4.3 Enabling agility in business solutions
BPM implementations respond faster to changing needs when supported by process agility
enablers. Agility enablers represent various tools that affect a change in a business process.
Each of the six agility enablers (policies, rules, service selection, active content, events, and
analytics) complements each other. All are available to make processes more flexible and
responsive.
WebSphere Process Server supports business agility by supporting business rules.

WebSphere Enterprise Bus (embedded in WebSphere Process Server) supports mediation
policies and dynamic service selection to enable the dynamic invocation of services. In
addition, capabilities, such as ad-hoc task creation and skip and redo tasks in a process flow,
provide flexibility to a business user, enabling the user to adapt processes to a more dynamic
business environment.
4.3.1 Business rules

The business rule logic that is extracted from a business process must be modifiable as the
needs of the business change. For each business rule, an administrator can change a
number of items. For example, for each operation defined on a business rule group, the
administrator can modify the schedule of active rules for that operation. The administrator can
modify the current business rule that is active for the operation or can schedule business
rules to be active in the future. The administrator can even update a business rule (rule set or
decision table) after it has been deployed to WebSphere Process Server.
In addition, by using templates (shown in Figure 4-7 on page 67), business analysts can
modify parts of the rule logic in the rule sets or decision tables. For example, if a business rule
is used to specify the discount on orders above a specific amount, the amount of the discount
and the amount of the order are parameters that, with a template definition, a business
analyst can modify using different management clients.

Figure 4-7 A rule set with rules specified using templates
Business analysts can make changes to business rules that are deployed to WebSphere
Process Server using Web-based tools, such as the Business Rules Manager and the
Business Rules widget in Business Space powered by WebSphere powered by WebSphere
(shown in Figure 4-8 on page 68). In addition to this built-in rules support, business rules that
are created and run in WebSphere ILOG Rule Business Rule Management System can be
exposed as SCA references and invoked from a business process.
Update busine ss
rules dynamic ally
Figure 4-8 Business Rules widget
4.3.2 Service selection and mediation policies

WebSphere Process Server is built on and contains WebSphere Enterprise Service Bus
(ESB). WebSphere ESB delivers a flexible connectivity infrastructure for integrating
applications and services and enabling SOA development. WebSphere ESB also provides
service selection and mediation-policy management through its integration with WebSphere
Service Registry and Repository.
Dynamic service selection

With the service selection capability, integration developers can invoke an external service as
part of processing a message in a mediation flow, perhaps even dynamically by deciding on
the actual service to be invoked at run time rather than at design time.
Mediation flows can be integrated with WebSphere Service Registry and Repository to make
service applications more dynamic and more adaptable to changing business conditions
(shown in Figure 4-9 on page 69). Furthermore, WebSphere Service Registry and Repository
can store information about services that are in use, will be used, or that people want to be
aware of. These services might be in local systems or in remote systems.

Figure 4-9 Dynamic service selection
When developing an SCA module that needs to access service endpoints from WebSphere
Service Registry and Repository, the integration developer includes an Endpoint Lookup
primitive in the mediation flow. At run time, the Endpoint Lookup mediation primitive obtains
the service endpoints from the registry that match its requirements and sets up the
appropriate target service for invocation. Figure 4-10 shows the Endpoint Lookup primitive.
Figure 4-10 Endpoint Lookup primitive in WebSphere ESB
Another solution that is based on the proxy service gateway pattern enables you to add
dynamicity to service invocation without using WebSphere Service Registry and Repository.
Each message is associated with a service endpoint, and the map is maintained in a built-in
configuration store that can be administered using the Business Space powered by
WebSphere Proxy Gateway widget (shown in Figure 4-11).
Figure 4-11 Proxy Gateway widget in Business Space powered by WebSphere
Mediation policies
Many enterprises want to dynamically control their service interactions by using contextual
information. You can develop new service interactions that achieve greater levels of flexibility
and administrative control using mediation policies, which improve the contextual control of
service interactions.
WebSphere ESB leverages WebSphere Service Registry

and Repository for mediation policy governance. When an
Achieve greater
integration developer uses WebSphere Integration levels of flexibility
Developer to create SCA modules that contain mediation and administrative
flows, any module property that is promoted (making a
property modifiable by the runtime administrator) is also a control using
dynamic property. Dynamic properties can be overridden, mediation policies
at run time, using mediation policies in WebSphere
Service Registry and Repository.
With the Policy Resolution Mediation primitive (Figure 4-12 on page 71), WebSphere Service
Registry and Repository can be queried to obtain the appropriate policy for the message
context. This primitive evaluates the mediation policies and propagates them along the
mediation flow. You administer mediation policies using the Mediation Policy Administration
widget in Business Space powered by WebSphere, and attach policies at the scope of SCA
mediation modules, service endpoints, and operations.

Figure 4-12 Policy Resolution primitive in WebSphere ESB
In Figure 4-13, two mediation policies were loaded into WebSphere Service Registry and
Repository. Depending on the value of the quality of service (QOS) conditional attribute in the
incoming message, WebSphere Service Registry and Repository returns the appropriate
policy, allowing WebSphere ESB to choose the appropriate service for an invocation: either
the one with the lower uptime or the one with the higher uptime.
QOS = Gold 99.999% up
ESB Service
QOS = Silver 99.9% up Provider
Condition
QOS = Gold
Mediation Policy A
WSRR
Mediation Policy B
Figure 4-13 Policy resolution in WebSphere Enterprise Service Bus

WebSphere Integration Developer provides a rich set of capabilities that help in the design,
development, implementation, and, ultimately, deployment of your BPM solutions, helping
your IT teams achieve a high level of productivity and efficiency. It provides a rich set of
editors for creating BPM artifacts, wizards in various contexts, and pattern-based approaches
to developing BPM solutions. Furthermore, it contains a copy of the WebSphere Process
Server runtime environment that an integration developer can use to test solutions. The
following sections highlight some key functions in WebSphere Integration Developer.
4.4.1 Leveraging the process model
To accelerate the development of end-to-end BPM solutions, WebSphere Integration
Developer is closely integrated with WebSphere Business Modeler and WebSphere Business
Monitor. Business Analysts who are the domain experts define and create the business
process, which can then be exported to WebSphere Integration Developer for the IT
developer to refine and deploy into WebSphere Process Server. The following sections
highlight the integration between the products.
4.4.2 Interactive process design

Interactive Process Design (IPD) increases time to value by enabling executable process
models to be fully defined and tested from WebSphere Business Modeler by business
analysts for typical use cases. The business analyst creates the process model in
WebSphere Business Modeler, invokes the Verify Process Design capability (which
generates and deploys the underlying solution artifacts), and then evaluates typical use cases
in the generated business space to test that the process runs correctly in the runtime
environment (shown in Figure 4-14).
Verification environment for

testing busines s proces s
Use Skip a nd Redo tasks for

dynamic workflow testing
Get help from IT to validate Track execution and validate

pr ocess execution input and output values
Figure 4-14 Problem determination for Interactive Process Design
The integration developer supports the business analyst by setting up the test environment
that runs WebSphere Process Server, creating services that the business analyst can use in
WebSphere Business Modeler and helping the business analyst with problem determination.
WebSphere Integration Developer provides a fully functional unit test environment to test and
refine the business solution.

4.4.3 Consuming iterative definitions from WebSphere Business Modeler
The process model that the business analyst created in WebSphere Business Modeler will
eventually be deployed into a production environment that runs WebSphere Process Server.
WebSphere Business Modeler includes a WebSphere Process Server mode that constrains
the process model to ensure that it can be exported to WebSphere Integration Developer
successfully and offers guidance to help the business analyst specify technical details to
fine-tune the nature of the IT-level artifacts that are generated when the artifacts are exported.
The integration developer receives these artifacts from the analyst and modifies those
artifacts in WebSphere Integration Developer for eventual deployment into WebSphere
Process Server (shown in Figure 4-15).
On many occasions, the relationship between business process elements that are defined in
WebSphere Business Modeler and the corresponding IT artifacts in WebSphere Integration
Developer is not always one to one. The challenge remains to manage iterations of definitions
on both the business and IT sides, ensuring that each team effectively understands the
changes that have been made in the other domain and keeps them in sync.
List of changes to the

business process
Graphic al view of changes to

the business proc ess
Figure 4-15 The Project Synchronization wizard in WebSphere Business Modeler
The integration developer uses WebSphere Integration Developer to receive updates from the
business analyst (as shown in Figure 4-15), see specifically where changes have been made
in the imported artifacts, comparing changes to existing versions of the artifacts, and merge
the appropriate changes. The integration developer can also generate a change-report file
that lists the model implementation changes that a business analyst can use in WebSphere
Business Modeler to validate the potential impact on process semantics.
4.4.4 Migrating running business processes

A key to successful businesses is enabling processes to be agile and facilitating an
environment where processes can be changed as business conditions evolve. A business
process might need to be changed for various reasons, such as to accommodate updated
regulatory compliance and new business requirements. In the case of long-running business
processes, it might be necessary to migrate processes that are currently running (called
in-flight processes) from an older version of a process to a newer version in a well-defined
manner. WebSphere Process Server provides the capabilities and flexibility necessary to
design, update, and migrate such long-running processes to provide greater flexibility and
meet changing business needs (Figure 4-16).
Figure 4-16 Creating new processes in WebSphere Integration Developer
In WebSphere Integration Developer, you choose the processes for which new versions are
required. Each new version is then created with a new validity date (Figure 4-17 on page 75).
You can make changes to the new version by editing the business logic. Typical changes

include adding human tasks and invoking additional services in response to new
requirements.
Figure 4-17 Process Migration Specification in WebSphere Integration Developer
After the new process version is created, you can use the migration specification wizard
(Figure 4-17) to create a migration specification that administrators deploy and use to migrate
running processes to the new version. Monitoring data that is associated with the previous
version is also associated with the newer version.
4.4.5 Developing service gateways and proxies
In WebSphere Integration Developer, you can develop different types of service gateways and
service proxies using the Patterns Explorer in WebSphere Integration Developer, shown in
Figure 4-18.
For example, a service gateway acts as a proxy to various services by providing one entry
point for incoming requests. Manually creating a service gateway requires creating artifacts,
such as gateway interfaces, bindings, and business objects. You can create these artifacts
with just a few clicks using the Patterns Explorer, ensuring easier and faster solution
development.
Figure 4-18 The Patterns Explorer in WebSphere Integration Developer
4.4.6 Sharing evolving projects for monitor model development

A business analyst can use events that occur while process instances run on WebSphere
Process Server as input into what business users see in WebSphere Business Monitor
dashboards. WebSphere Integration Developer provides first-class integration with the
WebSphere Business Monitor development toolkit to accelerate the development of monitor
models for these processes.
In WebSphere Integration Developer, the integration developer can use the Generate Monitor
Model wizard (Figure 4-19 on page 77) to introspect each module and generate a
stand-alone monitor model that is based on a predefined template for components in that
module (process, human task, business rule, and so on). The developer can further refine the
generated model while maintaining the flexibility to add other monitoring elements iteratively,
which allows both the application and the corresponding monitoring solution to co-evolve. The

integrated tools keep the two code bases (implementation code and monitor model) in sync,
without requiring the developer to manually reconcile existing and updated monitor models.
Figure 4-19 The Model Generation wizard in WebSphere Business Monitor
4.4.7 Team development

A central asset repository can be used to store and reuse BPM artifacts, allowing the BPM
solution development team to share and browse the artifacts. For example, a developer might
want to find and reuse the approved version of a process model, even if someone else
created it.
In WebSphere Integration Developer, you can share assets using IBM Rational Asset
Manager. Notification mechanisms can be set up to notify the developers when one of the
assets they depend on for their solutions is updated in the repository. You can also share
source using source management repositories, such as Concurrent Versioning System
(CVS), Rational Team Concert, and Rational ClearCase. Figure 4-20 on page 78 shows the
integration with the CVS repository, allowing collaboration and sharing of artifacts.
WebSphere Integration Developer allows the developer to browse and synchronize artifacts
with the repository as needed.
Figure 4-20 CVS integration in WebSphere Integration Developer
4.4.8 Integration Solutions view

When working on broad solutions that encompass multiple business modules, libraries, and
other dependent projects in a solution, the Integration Solutions view helps the integration
developer organize groups of related projects and more easily perform common actions on
the projects, such as sharing them in a team environment.
The integration developer can open the integration solution

diagram in the Integration Solution editor, see the
Organize groups of
relationships between the related projects that are referred related projects and
to in the integration solution, and perform functions that more easily perform
apply to all modules in a solution, such as testing the
solution and checking the solution into a repository. common actions on
those projects
Figure 4-21 on page 79 shows a snapshot of an
integration solution in the Solution Diagram editor. It also
shows the projects and libraries used in the solution, as well as dependencies on external
Web services.

I ntegration Sol uti ons pane listing
proj ects used i n thi s solution
A sol ution diagram showing

relationshi ps between projects
Mod ules and l ibrari es

used i n the sol uti on
Figure 4-21 Integration Solutions view
4.4.9 Tools for testing and problem determination

BPM solutions need to be thoroughly tested before being deployed into production
environments with WebSphere Process Server. WebSphere Integration Developer provides
the Integration Test client to test, debug, and troubleshoot modules, components, and
complete solutions. The test client features an intuitive user interface that enables integration
developers to easily manage and precisely control tests. The integration test client is shown in
Figure 4-22 on page 80.
Figure 4-22 The integration test client
Almost all the tasks performed in the integration test client are executed through the Events
and Configurations pages. On the Events page, the integration developer can perform
numerous test activities that enable interaction with the module during testing, such as
selecting an operation to test, specifying values for the operation, and invoking the operation.
In the Configurations page, you can edit the default test configuration or you can create and
edit new test configurations.
In many cases, an integration developer creates a set of components that rely on dependent
components that are either not created or fully developed. To test these components, you can
use the integration test client to emulate the dependent SCA components and ensure that
these components meet requirements. You can also create comprehensive test cases, test
suites, and test buckets for fine-grained and scenario-level testing.
4.4.10 Server Logs view

It is often necessary to troubleshoot a solution during development time using logs and traces
emitted by the server. The Server Logs view in WebSphere Integration Developer displays
server console and log file records as well as invocation records when cross-component
tracing capability is enabled (shown in Figure 4-23 on page 81).

Figure 4-23 Server Logs view
The Server Logs view provides several advantages over the traditional Console view, such as
the ability to filter records, display invocation records in hierarchical format, and load
invocation records directly into the integration test client when data is captured with
cross-component tracing.
4.5 Enhancing human-centric BPM

With the ability to involve people in business processes in WebSphere Process Server, you
can capture simple to complex business processes that include a mixture of automated and
human steps. By treating a human task as another kind of service, you can build flexible
processes that evolve to become more automated over time (for example, replacing a current
human task with an automated service) without significantly reworking the original process.
WebSphere Integration Developer and WebSphere Process Server offer a broad range of
support for human-centric BPM:
Dynamicity for knowledge workers (case handling)
Single-person and multiple-person (parallel) human task routing
Business calendar support
Integrated forms capabilities
Finer-grained control over the selection of people who may perform a human task
These features simplify configuring and managing processes that involve people, therefore,
reducing the total cost of ownership.
4.5.1 Dynamicity for knowledge workers (case handling)

Enhanced dynamic workflows are business processes in which the business logic can be
adapted at run time. For example, the assigned business worker might decide to repeat an
activity, launch a subtask, or skip some steps in the business process. Business processes
should provide the needed flexibility to efficiently run such scenarios.
WebSphere Process Server supports the ability to
combine well-defined procedures with operational
Case handling
flexibility using the case-handling paradigm. Case leverages the expertise
handling allows dynamic changes, including the ability and knowledge of the
to skip or redo one or many human activities, support
for adding human activities on the fly, and the ability to task owner to enable
attach documents to business processes (shown in flexible processes
Figure 4-24).
Collaboration scopes are a type of generalized flow that is used to model dynamic workflows,
providing the model for creating workflows that are conducive to actions, such as redo, skip,
and add additional steps. This scope also sets up a case folder variable that can be used to
share data documents.
View details and act Skipped future

Completed task on tasks task
Running tas k with a

pending sub-ta sk
Figure 4-24 Case handling in WebSphere Process Server
Case handling is ideally suited to situations in which task owners use their knowledge to
adapt business processes, because it enables the business analysts to create workflows that
are well-defined, yet give process participants the flexibility to use their own skills and
judgment to adapt the flow to the business needs. For example, the task owner can perform
the following actions:
Repeat a number of activities if the initial results were not satisfactory - For example, a job
applicant might be called in for a second interview if an additional manager wants the
opportunity to speak to the applicant. In this case, the task owner will redo a task.

Expedite the process - For example, a loan application might be dismissed at a certain
point in the process without going through the final steps. In this case, the task owner will
skip a task.
Trigger subprocesses - For example, a doctor might order a blood test, because a patient
is not responding in an expected fashion. In this case, the task owner will add an additional
dependent task.
Advanced task management capabilities

Business Space powered by WebSphere task-management capabilities also help you during
case management and other human task scenarios:
Managing escalations: The Escalation widget in Business Space powered by WebSphere
(Figure 4-25) shows you the escalation statuses of tasks. You can filter and sort
escalations and view escalated tasks in the process diagram. In addition, you can initiate
escalations that have not yet been triggered.
List of tas ks with esca lations grouped by

task na me
Task Information showing e scalation details
Figure 4-25 Managing escalations in Business Space powered by WebSphere
Working continuously: Often, when someone completes a task and wants to start the next
task, the user wants the next task to be available immediately rather than having to choose
the next task from a list of tasks. This method of working continuously (where the next task
is presented to the user automatically) is supported in Business Space powered by
WebSphere. The next task can be chosen based on different criteria, such as age of the
task, task priority, and business data.
Tasks filtering and grouping: Using Business Space powered by WebSphere task widgets,
you can also group related tasks based on custom criteria, filter tasks, and control the
number of tasks on a page. The criteria for filtering and grouping can use business data,
as well as predefined data, such as task name and task owner.
4.5.2 Parallel routing of a task with result aggregation
In many process flows, multiple people must work on a task, and the results of their work
must be aggregated to complete the task. This action is called parallel routing. WebSphere
Process Server and WebSphere Integration Developer help you easily create and configure
parallel routing using powerful aggregation functions and, optionally, a completion function
that allows preemptive completion of the task. For example, if two of four owners have
completed a parallel task, the human task can be marked complete (Figure 4-26).
Figure 4-26 Configuring a parallel human task in WebSphere Integration Developer
The human task is configured to be a parallel task in

WebSphere Integration Developer (Figure 4-26).
Easier configuration of
When this task is invoked in WebSphere Process parallel routing ensures
Server, each potential owner of the human task has a better time to value for
sub-task to work on and complete. You can specify an
aggregation function that will aggregate the developers
responses from each owner. Some of the aggregation
functions concatenate responses and calculate voting
percentages, as shown in Figure 4-27 on page 85.

Figure 4-27 Aggregrate function for collating results of parallel tasks
As mentioned earlier, the process might require preemptive completion of the human task,
which is achieved by using the optional completion function, shown in Figure 4-28. The
completion function can be based on time or other conditions, such as the percentage
completed.
Figure 4-28 Completion function for parallel tasks
4.5.3 Business calendars

Business calendars are modeled in WebSphere Integration Developer to represent
non-contiguous times and run in WebSphere Process Server wherever elapsed time
(duration) is needed, such as in human task expiration or business process wait activities.
Figure 4-29 on page 86 shows the definition of a business calendar in WebSphere Integration
Developer.
Figure 4-29 The Business Calendar editor in WebSphere Integration Developer
Imagine that a human task must be completed in two days; however, a holiday occurs or a
weekend occurs during this time. Using an appropriate calendar, you can ensure that this
holiday or weekend is excluded when WebSphere Process Server calculates the elapsed
time. In Figure 4-30, a business calendar is used to indicate the duration before a task is
overdue.
Figure 4-30 Selecting a calendar for a human task

Business calendars can also be modified at run time using the Business Calendar Manager
widget. Role-based access control is available to set proper permissions and allow business
users to read or update existing calendars in the Business Calendar Manager.
4.5.4 Integrated forms

Business users often use forms in BPM applications as input to start a business process or
capture the progress of a business process. WebSphere Integration Developer and
WebSphere Process Server integrate Lotus Forms capabilities for a richer BPM experience at
both authoring time and run time.
With WebSphere Integration Developer, the developer

can use the integrated Lotus Forms capability (shown in
Use the integrated
Figure 4-31) to generate forms-based clients for existing Lotus Forms
human tasks. capability to generate
forms-based clients
Figure 4-31 Forms generation for a human task in WebSphere Integration Developer
The generated form is based on the task interface definition and can be customized (shown in
Figure 4-32 on page 88). In addition, the developer can also create human tasks from an
existing form and can create processes that are initiated by a human task using existing
forms.
Figure 4-32 Lotus Forms running in Business Space powered by WebSphere
4.5.5 Audit trails of processes and tasks

Businesses often need to maintain an audit trail or record of processes. Audit events are
raised when the state of a process or activity or a human task changes. Typical events include
starting or stopping processes.
Events that are related to business processes and human tasks can be generated to
Common Event Infrastructure (CEI), to an audit log, or both. The audit log events (shown in
Figure 4-33) are written to the audit trail in the Business Process Choreographer (BPC)
database, and CEI events can be written to the CEI database or to other destinations and
monitored by applications, such as WebSphere Business Monitor, to aggregate information
from events, display it in real time, and analyze historical data.
Figure 4-33 Auditing business processes
4.5.6 Federating staff repositories and participant substitutions

WebSphere Process Server leverages the Virtual Member Manager capabilities in
WebSphere Application Server to provide advanced support for assigning individuals or
groups to specific human tasks. Virtual Member Manager makes it easy to extend the number
of attributes and factors that can be injected into the process of deciding who does specific
human tasks.

Also called delegation support, this key capability allows the
integration developer to inject additional support into the
Automatic
assignment process so that business users can more easily reassigning of
manage absences by having first-class support for tasks ensures that
substitution. Substitution allows a business user to specify
whether someone is absent and, if absent, to identify a list of human tasks are
people as substitutes. not left waiting
The integration developer defines the substitution policy to be applied on a per-task template
basis. At task definition time (Figure 4-34), the integration developer uses WebSphere
Integration Developer to select the substitution policy. Depending on the selected policy,
various criteria are applied at run time to compute the substitutes.
Figure 4-34 Delegation support for human tasks
4.6 Lowering the total cost of ownership

After you have deployed your BPM solution, you want to keep the resources that are required
to maintain that solution to a minimum. WebSphere Process Server helps you manage
processes by giving you more control over the administration of processes and activities,
governance of process failures with unified failure management tools, and tools for monitoring
and managing your production environment.
WebSphere Process Server also leverages underlying WebSphere Application Server
network deployment technologies to provide high scalability, availability, and performance. By
leveraging advanced clustering and failover techniques, WebSphere Process Server ensures
a high level of process integrity and, with proper planning of your topology, helps ease your
administration, maintenance, and deployment costs.
4.6.1 Administering business processes

Business processes can be administered through the BPC Explorer Web tool in WebSphere
Process Server. BPC Explorer helps the administrator manage processes and activities in
human tasks as well. It can be configured to apply role-based security so that only users with
proper authorization can work with processes (shown in Figure 4-35).
Administer business
proc esses and view the
state of the process
Administer business
process te mplates,
instances, and activities
Figure 4-35 Business Process Choreographer (BPC) Explorer
As an administrator, you can see information about process templates, process instances,
tasks, and associated data, and you can act on this information. You can perform advanced
problem determination to diagnose process failures and can select activities to redo, skip, or
invoke a subprocess. You can also migrate process instances from one version of the process
to another version. BPC Explorer has an optional reporting function that provides reports
about the statistics of a process.
The Process State view (shown in Figure 4-36 on page 91) gives a graphical representation
of the process and its current state. An administrator can monitor the activities that the
process executed and view details related to the specific activity. If an activity failed, the
administrator can see details about the error and repair the activity.

Figure 4-36 The Process State view in BPC Explorer
4.6.2 Managing failed processes

Planning a recovery strategy for handling failures is a critical part of deciding on a production
environment and creating the appropriate topology for your applications. WebSphere Process
Server provides tools that help you identify failures in your business processes and repair
those failures effectively.
The Failed Event Manager (shown in Figure 4-37 on page 92) is a graphical Web tool that is
available to administrators who manage failed processes and messages in the system.
Administrators use the Failed Event Manager to find and manage failed events on all of the
servers in a complex production environment. The Failed Event Manager reports events that
failed because of errors in SCA, Java Message Service (JMS), and stopped, terminated, or
failed business processes. The interface enables administrators to see (and in some cases,
edit) the data for a failed event, resubmit a failed event, and delete a failed event.
Resubmit failed e vents to
repair failed flows
Figure 4-37 Failed Event Manager
The Failed Event Manager is integrated with BPC Explorer. The failed process can be opened
from the Failed Event Manager and repaired in BPC Explorer.
4.6.3 Storing and forwarding messages

Critical systems in IT environments are built to have a high degree of availability and
redundancy. However, sometimes an application that provides a critical service in an SOA
environment fails, and services that depend on the failed service must adapt. WebSphere
Process Server enables this adaptation: When WebSphere Process Server detects that a
target Service has failed, it saves (or stores) the messages that are destined for the target
server, instead of failing the invocation and creating failed events (Figure 4-38).
Figure 4-38 Store and forward QoS qualifiers in WebSphere Integration Developer

When the target service is running again, the stored messages can be reprocessed
(forwarded) using the Store and Forward widget in Business Space powered by WebSphere
(see Figure 4-39).
Stor e and forward actions for

messages
Ca rd Pro c e s s
Ca rdPro ces s
Figure 4-39 Store and forward administration widgets
4.6.4 Administering solutions

Monitoring business solutions in the IT environment is a critical activity of any administrative
task. WebSphere Process Server provides widgets in Business Space powered by
WebSphere that show you a snapshot of the overall system health (see Figure 4-40). These
widgets provide status, such as about the application servers, nodes, clusters, and
deployment environments, and other information about solutions, such as state, deployment
targets, and module versions.
The System Hea lth The Module Health widget

widge t monitors the monitor s the health of specific
hea lth of the de ployment modules and associated
environment resource s
Figure 4-40 Solution administration widgets in Business Space powered by WebSphere
4.6.5 Availability and scalability
Clustering is a key technique that you can use to improve the availability and the scalability of
a WebSphere Process Server environment. With clustering, you can increase the availability
of the system, which can ensure some level of continuity of service in case of failures.
Clustering is also a way to accommodate additional workload scalability by making additional
processes and systems available to run transactions.
Selecting an appropriate topology for your production environment depends on several

factors, including the available hardware resources, the types of business processes that you
plan to implement, your scalability requirements, and the administrative effort involved (refer
to Table 4-1). The following table lists the topology patterns that WebSphere Process Server
supports.
Table 4-1 Factors to be considered to build your topology

Factors to be Single cluster Remote Messaging Remote Messaging
considered topology topology and Remote Support
topology a
Number of clusters to One cluster for all One cluster for One cluster for
maintain components applications and applications
for the support One cluster for
infrastructure support
One cluster for infrastructure
messaging One cluster for
messaging
Hardware Can be implemented More hardware Most hardware

requirements on limited hardware required for distributed intensive
environments
Long-running Use should be minimal Use must be balanced Ideal environment for
processes, state against resource interruptible
machines, and human availability processes, state
tasks machines, and human
tasks
Administrative burden Relatively small Requires additional Requires the most

effort administrative effort
Scalability Easiest to scale but all Messaging cluster Easiest to scale

components are scalability is limited All functions are
scaled at the same All other separated
rate components are
Messaging cluster
scaled at the same
rate scalability is still
limited
a. You can extend the Remote Messaging and Remote Support topology pattern to include a Web
applications cluster that you can use when both WebSphere Process Server and WebSphere
Business Monitor are deployed into that cluster.
In general, the Remote Messaging and Remote Support topology pattern is the most suitable
production topology, but the choice ultimately depends on your unique requirements. As you
plan for your production environment, carefully consider the advantages and disadvantages
of each of the common topology patterns as outlined in the table.

WebSphere Process Server provides tools that help create
and administer topology patterns. The patterns are
Deployment
represented as deployment environments, and the wizards enable
Deployment Environment Configuration wizard (shown in rapid creation of
Figure 4-41) on the administrative console helps you create
these patterns rapidly and effectively. You can rapidly advanced topology
configure an environment that not only includes WebSphere patterns
Process Server but other BPM products, such as WebSphere
Business Monitor. In addition, you can easily define database configuration specifications for
the different topology patterns. The Deployment Environment wizard uses these
specifications, enabling a consistent, repeatable experience across the BPM product stack.
Figure 4-41 The Deployment Environment wizard in the WebSphere Process Server administrative console
4.7 Summary
WebSphere Process Server and WebSphere Integration Developer provide robust
standards-based capabilities to implement, test, deploy, and manage BPM solutions. These
products form the integral enabling component of the IBM BPM portfolio and are integrated
with a broad range of connectivity technologies to extensively reach across heterogeneous
systems in your enterprise. By linking business and IT, WebSphere Integration Developer and
WebSphere Process Server contribute to a holistic BPM strategy.
5
Chapter 5. Enabling BPM and BAM with the

WebSphere Business Monitor
You can enable business process management (BPM) and business activity monitoring
(BAM) with WebSphere Business Monitor. WebSphere Business Monitor can help you
perform the following tasks:
Achieve real-time, end-to-end process visibility in business processes and operations
Create new dashboards, Key Performance Indicators (KPIs), and alerts with minimal IT
involvement
Proactively manage your business
Ensure continuous business process improvements
Accelerate time to value using powerful templates and accelerators

5.1 Introduction
The fundamental value of business activity monitoring (BAM) Managers need
is that it gives you real-time insight into how well your
business is running. You receive this information in a timely up-to-the-minute
manner so that you can identify problems and business insight on key
opportunities and facilitate continuous business improvement
and proactive corrective action, ultimately reducing costs and operational metrics
increasing revenues. To take timely action, you need to be
alerted to operational information about unforeseen events that affect your customers or the
bottom line. You also need to be made aware of long-term trends that identify strategic targets
and factor in opportunities and competitive challenges.
5.2 Empowering the line of business

An essential component of business process management (BPM) is to enable the line of
business (LOB) to play an active role in defining how the business processes should be
managed. The scope of this role includes the ability to define the high-level business metrics
(with WebSphere Business Modeler), view operational and strategic business activity using
dashboards, be alerted to key situations, and use real-time data to improve business process
definitions (also working with WebSphere Business Modeler).
Business conditions change quickly for many Customize your dashboards

reasons, such as responding to a competitor
introducing new product lines, evolving to without requiring IT to
customers expectations for improved service, re-implement, test, and
and dealing with product recalls.
Organizations must respond quickly to redeploy the monitoring
business conditions like these to be solution
successful.
WebSphere Business Monitor (shown in Figure 5-1 on page 99) raises the bar of
empowerment so that business users can customize the monitoring solution and dashboard
to react to these changes rapidly, without requiring IT to re-implement, test, and redeploy the
monitoring solution, as defined by a monitor model. Business users can modify what is
displayed, add new KPIs or change the thresholds on existing ones, and define alert
situations and determine to which alerts business users want to be alerted, without
discussing changes with a developer or portal administrator. This customization not only
provides flexibility to the business, but it relaxes the need for IT to meticulously define all KPIs
and alerts up front, enabling businesses to react quickly to changing conditions. At the same
time, the routine workload on IT is reduced, enabling them to focus on more strategic
projects.

Figure 5-1 WebSphere Business Monitor dashboard in a business space
Business spaces integrate monitoring capabilities with other process content for
comprehensive management of business processes. Business users may choose to use a
default dashboard provided by IT or build one themselves. For example, you might want to
build a business space dashboard (or business space) with a unique view configuration and
make it accessible only by a particular group of users. You can name this dashboard, select
which widgets to include, and arrange them in a unique layout.
Furthermore, business users can select which widgets cooperate with one another (that is,
indicate how a change in one widget affects another widget). Business users can also
combine widgets that are supplied with other WebSphere Dynamic Process Edition products
with business monitoring widgets to optimize the management of their business environment.
In addition, Business Space powered by WebSphere includes templates that enable business
users to easily create role-oriented business spaces to match the needs of their organization.
5.2.1 Critical insight throughout the business day

Business users do not typically look at a WebSphere Business Monitor dashboard
continuously throughout their day using a desktop monitor. They require business insight
delivered to where they work, wherever that might be. In addition to Web-based business
dashboards, business users can improve their responsiveness by gaining business
monitoring insight through common business applications and devices. For example, you can
access and monitor key performance measures from the following devices:
Mobile devices, such as BlackBerry smart phones and the Apple iPhone and iPod Touch
IBM Lotus Notes collaboration software
The IBM Lotus Sametime instant messaging client
Desktop gadgets
Common business software, such as Microsoft Excel
Chapter 5. Enabling BPM and BAM with the WebSphere Business Monitor 99
Additionally, WebSphere Business Monitor provides a rich set of Representational State
Transfer (REST) programming interfaces, facilitating the development of custom clients. For
example, developers can enable BAM insight from instant messaging clients, such as AOL
Instant Messenger.
5.2.2 Creating and subscribing to business alerts

WebSphere Business Monitor can alert business users to a particular situation (for example,
a KPI has exceeded a threshold) by sending a notification to a business dashboard, an e-mail
ID, pager, or personal digital assistant (PDA) (shown in Figure 5-2). With this notification,
business users can react to this business situation in a timely fashion so that you can prevent
problems or take advantage of opportunities immediately. Business users can set up new
alerts, change the mode in which you are alerted, and subscribe to predefined alerts, all from
your dashboard.
For example, the Order Fulfillment manager is alerted by e-mail when the average time taken
to fill orders exceeds a specific duration. However, this manager now wants to be alerted by
pager when a Gold customer order exceeds a specific duration to fill. By using the Alerts
Manager in WebSphere Business Monitor, the Order Fulfillment manager can subscribe to
alerts of interest and specify the notification mechanism, without involving IT.
Figure 5-2 Subscribing to alerts using the Alert Manager in WebSphere Business Monitor
The Order Fulfillment manager might also want notification for other situations that have not
been predefined, for example, when the end of day Order volume prediction is below target.
Using the Alerts Manager, the manager can create alerts (shown in Figure 5-3 on page 101).

Figure 5-3 Creating an alert using the Alert Manager in WebSphere Business Monitor
5.2.3 Personalizing and creating KPIs on the fly

A key theme of BAM is discovery: analyzing data to gain business insight that otherwise might
be unrealized. With the KPI Manager, business users can select one or more KPIs and
modify the display mode (Table view, Gauge view, and so on) and the visual characteristics
(color range spectrums, sizes, layout format, and so on). Figure 5-4 shows the KPI Manager.
Figure 5-4 Modifying KPI properties using KPI Manager
As the business environment changes, KPI thresholds often need to change too. Using the
KPI Manager, you can modify KPI thresholds so that you can move their success targets and
evaluate various what-if scenarios without asking IT to update and redeploy the monitor
model.
For example, a business user deems that the Order Fulfillment Duration threshold is too high.
This leader lowers the threshold value and assesses how well the business performs given
the same incoming events. If the business is not meeting the new threshold, the leader can
ask business analysts to determine how the process can be improved to ensure the new
goals can be achieved.
In addition, as you assess the state of the business, business users might realize that a new,
yet-to-be-defined KPI might be helpful. With KPI Manager, authorized users can define, copy,
and update KPIs. New KPIs can be based on calculating data from existing KPIs or on
aggregations of business metrics. Figure 5-5 shows the interface for creating a KPI.
Figure 5-5 Creating a KPI
5.2.4 Accessing KPI history and projecting future KPI values

One of the key benefits of WebSphere Business Monitor Current, historical,
is that, in addition to enabling the viewing of real-time
metrics, it helps business users understand the and future insight
historical variation for additional insight. Business users facilitates the ability to
can view the variation of a KPI (KPI history) over flexible
time periods, leverage this history for predicting future
take focused, effective
KPI values, and create alerts based on predicted future action
KPI values.
For example, while creating a staffing plan for the order-processing center, business users
might want to understand the order trends over the past six months and predict future values
based on these trends. Using the KPI History and Prediction widget (shown in Figure 5-6 on

page 103), you can control KPI history and prediction settings and view historical variances
and predicted future values.
Figure 5-6 Viewing KPI history and predicted values
To be made aware of potential future business anomalies and take proactive mitigating action,
you can create alerts that notify the business users when predicted values deviate from
baselines that you defined. For example, you might want to know when the average daily
order volume 30 days from now is projected to deviate from norms. This powerful capability
enables business users to react proactively to potential business situations that can be
detected this way so that you can prevent problems even before they occur.
5.2.5 Monitoring and managing human tasks

Human workers are an important factor in the success and efficiency of processes.
WebSphere Business Monitor provides a set of configurable views to display human tasks to
better assess workloads, identify bottlenecks, and redirect workload to prevent backlogs
(shown in Figure 5-7). Human tasks can be Business Process Execution Language (BPEL)
tasks orchestrated by WebSphere Process Server, or stand-alone human tasks in the
monitored system.
Figure 5-7 WebSphere Business Monitor Human task widget
With the WebSphere Business Monitor Human Task widget, business users can view all
WebSphere Process Server human-task events that are related to particular monitor models.
You can also choose which properties of those human-task events to show or hide, as well as
filter and define properties that can be sorted. You can also assign, claim, release, or transfer
tasks, depending on the accessibility that you were granted.
When using WebSphere Process Server, business users can use business spaces to
combine WebSphere Business Monitor human-task capabilities with capabilities that
WebSphere Process Server provides to manage human workload holistically (shown in
Figure 5-8). For example, business users can create new tasks and manage their own and
that of the team.
Figure 5-8 Workload and task management with WebSphere Process Server and WebSphere Business Monitor using
business spaces
5.2.6 Business problem root-cause analysis

Business users can now view applicable process instances (sometimes known as
drill-through) for KPIs to more easily determine the root causes of business problems. In
addition, for greater insight into business performance trends when performing historical
analyses, business users can view applicable process instances as they relate to specific
dimensions.
This capability enables business users to identify problematic Improved

situations and immediately assess the details behind the situation, for
greater insight into the problem and its solution. For example, the capability for
Order Fulfillment manager might determine that the fulfillment time for root-cause
todays orders is not meeting service-level agreements. The Order
Fulfillment manager can easily see todays orders to understand what analysis
is causing the problem, which enables focused action that will correct

the situation. Figure 5-9 shows how you traverse from a KPI to the related process instance
details, starting with the instances.
Figure 5-9 KPI show instances
Figure 5-10 on page 106 shows how you traverse from a KPI to the related process instance
details, showing you the instances updated.
Figure 5-10 KPI show instances - instances updated
5.2.7 Using monitor data for reporting

Business users often want to take snapshots of the critical business data that WebSphere
Business Monitor gathers and displays so that they can show business performance, in the
form of business reports, to a broad audience that is already familiar with business
intelligence reporting. Additionally, business users might want to use advanced business
intelligence to uncover underlying trends. WebSphere Business Monitor includes IBM DB2
Alphablox to provide historical data structure and predefined business analytics. Without
additional software, you can combine real-time insight with business analytics from within a
business space.
For snapshot reporting and advanced business intelligence, reporting tools (for example, IBM
Cognos 8 Business Intelligence) can use the open data architecture of WebSphere
Business Monitor, combined with an online analytical processing (OLAP) cubing service,
such as IBM InfoSphere Warehouse. Cognos 8 Business Intelligence, for example,
provides a data-mapping layer and metadata bridge to logically map to the WebSphere
Business Monitor data that is exposed using a cubing service. Figure 5-11 on page 107
shows an example report.

Figure 5-11 A Cognos 8 Business Intelligence report on WebSphere Business Monitor
Figure 5-12 shows the topology.
Cognos Cognos
OLAP
Framework Frame work
DB2 CubeV iews
Manager Manager
Metadata
Metadata Bridge Metadata Bridge
WebSphere Cognos 8
Business Business
Monitor Intelligence
Database Reporting
Figure 5-12 Using WebSphere Business Monitor data with Cognos 8 Business Intelligence
5.2.8 Quickly test and monitor business processes

For certain human-centric process scenarios, business Easily test business
users are empowered to go directly from modeling in
WebSphere Business Modeler to deploying on the processes without
WebSphere Process Server and (optionally) WebSphere requiring IT
Business Monitor server environments. A pre-configured
business space that is created as part of deployment can be used immediately to run,
manage, and monitor processes, enabling business users to more easily define and test
business processes, including the business monitoring of those processes, without requiring
IT involvement. Figure 5-13 on page 108 shows how you initiate the validation and a test of a
process from WebSphere Business Modeler.
Figure 5-13 Testing a business process
5.3 End-to-end process visibility

To improve business results, business users must be able to see into all aspects of the
process. For example, during an order-to-cash process, it is important to know not only how
much time a supplier took to fill the order, but also how much time it took to invoice the
customer. WebSphere Business Monitor provides this end-to-end visibility so that you can
decide to expedite invoicing when there are supplier delays filling orders, ensuring that the
overall process time meets customer service level agreements.
To effectively monitor a business, a monitoring solution must be able to use events from all
relevant event-emitting applications, processes, or data-driven solutions. Instrumenting a
heterogeneous monitoring environment can be daunting without a standardized event
infrastructure and the tools to gather events.
WebSphere Business Monitor facilitates BAM implementations by providing first-class, ready

to use support for events from the following process engines, enterprise service buses, and
mainframes (Figure 5-14 on page 109):
WebSphere Process Server
WebSphere MQ Workflow
FileNet Business Process Manager

WebSphere Message Broker
WebSphere ESB
WebSphere DataPower XI50
CICS
IMS
WebSphere Adapters
WebSphere Adapters can also be used to get event information from Enterprise Information
Systems (EISs), such as SAP, and even create user-defined functions to pull data from other
systems.
Adapters:
ESB & WebSphere Application Server
Process Server SAP, PeopleSoft, etc.
WebSphere Business
Monitor
CIC S
Bu sin e ss
Ser vice s Fa bri c
IMS
MQ
Wo rkfl ow
Sen sor Eve nts
Mes sag e Bro ker

Bu sin ess Eve nts Partn er Ga tew ay Th ird Party IBM Fi le Ne t P8
Ap pl ica ti on s
Figure 5-14 WebSphere Business Monitor support for events
5.3.1 Monitoring WebSphere Process Server and WebSphere Enterprise

Service Bus applications
Organizations can easily monitor WebSphere Process Server and WebSphere Enterprise
Service Bus applications. Graphical tools enable developers to instrument applications to
provide appropriate information for business activity monitoring and creating and deploying
business monitoring solutions, without requiring programming. Additionally, monitoring
solutions can be tested using the integrated test client in WebSphere Integration Developer.
5.3.2 Improving insight with WebSphere Business Events

A business event is an electronic signal or message that indicates that a change in the state
of the business has taken place and occurs within a business context. Business context is the
combination of time (during working hours), population (for Platinum customers), activity
(change address), state (red alert state), space (within Chicago), or other interrelated
attributes that provide a backdrop in which patterns of events can be evaluated and actions
can be taken.
Business event processing (BEP) is the ability to sense when an event or event pattern has
occurred or not occurred, indicating an actionable business situation, and to coordinate the
right response at the right time. BEP provides capabilities and tools to define and detect
business events for greater visibility and a more rapid response to opportunities and threats.
Individual events might not be significant in isolation. However, BEP aggregation and
correlation capabilities can find patterns and trends that would otherwise be undetectable.
For example, in a banking scenario, the combination (in a short Find patterns and
period of time) of a user password change, a change of
address, and a large withdrawal can be captured and trends that would
correlated to indicate an actionable situation that might require otherwise be
an investigation of fraud or the withholding of the withdrawal.
undetectable
WebSphere Business Monitor and WebSphere Business
Events are highly complementary. When WebSphere Business Events discovers an
actionable situation, it can generate notifications in the form of events for WebSphere
Business Monitor. In turn, WebSphere Business Monitor can generate events for WebSphere
Business Events when, for example, the value of a KPI exceeds or is predicted to exceed a
threshold (shown in Figure 5-15).
Figure 5-15 Achieving increased insight with WebSphere Business Events and WebSphere Business
Monitor
5.3.3 Monitoring applications with WebSphere Message Broker

WebSphere Message Broker enables information that is packaged as messages to flow
between different business applications, ranging from large traditional systems through to
unmanned devices, such as sensors on pipelines.
Because developers can configure message flows to emit event messages that can support
transaction, auditing, and business process monitoring without modifying the message flows,
existing production message flows are enabled easily and unintrusively. Figure 5-16 on
page 111 shows how you monitor WebSphere Message Broker flows.
Monitoring activity in WebSphere Message Broker now includes improved visibility of

business changes that occur inside the processing of a message flow, as well as access to
business-relevant data, such as the amount of an item in a purchase order. With WebSphere

Message Broker V6.1.0.3 or later, events can be emitted each time a message passes
through a terminal on a node. A terminal event reveals any significant occurrence inside a
message flow.
WebSphere Message Broker provides the following types of events:

Terminal events - Any terminal in a message flow can be an event source. If the event
source is active, it emits an event each time that a message passes through the terminal.
The event payload that is emitted can contain anything from the message tree.
Transaction events - Each input node in a message flow contains three transaction
events, in addition to any terminal events:
Transaction start
Transaction end
Transaction rollback
Figure 5-16 Business activity monitoring with WebSphere Message Broker
WebSphere Message Broker Toolkit V7 generates a monitor application information file for
use in WebSphere Business Monitor. The broker developer exports the file, and the monitor
developer imports the file and uses it to build the monitor model (Figure 5-17 on page 112).
Figure 5-17 Improve authoring by using monitoring application information
5.3.4 Monitoring CICS applications

Given the considerable amount of business processing that is carried out in CICS systems
across the world (over 30 billion transactions a day), CICS is a significant source of business
events.
The CICS runtime environment detects instances of events that are enabled and captures the
events and payload without the need to make application code changes. When CICS
captures events, it carries out specified filtering to enrich the event with information about the
application context in which it occurred, formats the event for WebSphere Business Events,
WebSphere Business Monitor, or another consumer, and routes it to that event consumer
(Figure 5-18 on page 113).

Development & Deployment
Tools
WebSphere
Business
Events
Existing CICS Event Processing
Business
Logic Event Capture
Filtering
Enrichment
Code Formatting
NOT Routing
Events
1
6
WebSphere
4
1
Captured
2
1
1
0
8
changed
6
4
2
Business
0
Events Monitor
Extensible
Secured
Monitored Other
etc. Event
Consumers
CICS Transaction Server for z/OS
Figure 5-18 Monitoring CICS applications
5.3.5 Monitoring events from IMS

Information Management System (IMS) is both a transaction manager and a database
manager for z/OS. As IMS developed over the years, new interfaces were added to meet
new business requirements. It is now possible to access IMS resources using a number of
interfaces to the IMS components.
Applications running on IMS V11 can generate event payload that will be forwarded to
WebSphere Business Monitor running on WebSphere Application Server. The event payload
is routed to WebSphere Business Monitor through the REST service for event emission
(Figure 5-19 on page 114).
In itia ting
C li en t
IMS IMS En te rpri se Su ite

Sta rt SOAP Gate wa y
IMS a pp lic atio n
Runtime environment
IMS app li catio n 3

- E ven t e mitte r
-
- u sin g th e
IMS R EST pro toco l
Co nne ct Event
Even t 1 paylo ad
emi ssio n Hold queue
po int (tpipe) E ven t e mitte r
u sin g th e
ISR T A LTPC B XML SOAP p rotoco l
ad apte r
Co rrel ator WSD L

XML (S OAP
co nve rter fi le p rotoco l)
We bSp he re
A pp lic atio n Serve r
We bSp he re
Bu sin ess
Ev ents
We bSp he re
A pp lic atio n Serve r
We bSp he re
Bu sin ess
Mo ni to r
Figure 5-19 Emit business event data from IMS for business monitoring
5.3.6 Monitoring FileNet processes

Because IBM FileNet Business Process Manager P8 is the key environment for
content-centric BPM solutions, it is important that WebSphere Business Monitor provide
first-class support to monitor FileNet-based processes (shown in Figure 5-20 on page 115).
FileNet provides a Common Base Event adapter that retrieves FileNet Process Engine
events, transforms those events into Common Base Events, and transmits them to the
WebSphere Business Monitor server. A monitor model that is tailored to monitor FileNet
Business Process Manager processes provides a workflow monitoring context, a work item
monitoring context, and several predefined measures (processing time, workflow maps,
queues, and so on). Many native FileNet Business Process Manager event definitions (for
workflows, work items, and activities) are also available for use in WebSphere Integration
Developer and WebSphere Business Monitor.

Figure 5-20 Steps to monitoring FileNet-based processes
5.3.7 Monitoring WebSphere MQ Workflow processes and applications

Although IBM highlights WebSphere Process Server as a strategic server technology for
running process flows, many WebSphere MQ Workflow users must monitor their process
environments while they plan for and ultimately migrate to WebSphere Process Server. In
response, WebSphere Business Monitor provides first-class support for WebSphere MQ
Workflow events (shown in Figure 5-21 on page 116).
Figure 5-21 Generating the monitor model for a WebSphere MQ Workflow audit trail
With the Flow Definition Language (FDL) to monitor model utility, part of the WebSphere
Business Monitor development toolkit, developers can import an existing FDL file so that they
can generate event definitions and a monitor model. As well, WebSphere MQ Workflow
provides a support pack that helps the runtime environment perform the following tasks:
Emit the container data from the audit trail.
Convert the audit trail data to Common Base Events using the WebSphere MQ Workflow
Event Converter.
Publish the Common Base Events to the Common Event Infrastructure (CEI).
In addition, WebSphere Business Monitor can receive events from WebSphere MQ

applications when a WebSphere MQ link between the WebSphere MQ queue manager and
the CEI that routes events to WebSphere Business Monitor is configured. WebSphere MQ
applications can then send XML-based Common Base Events to the CEI server queue.
5.3.8 Monitoring business applications with WebSphere Adapters

To extend the reach of BAM, WebSphere Adapters lets you use events that come from
various EISs and applications, including Oracle E-Business Suite, Siebel Business
Applications, mySAP.com, and JD Edwards OneWorld.

The WebSphere Adapters runtime environment can emit events to WebSphere Business
Monitor. Additionally, IBM Rational Application Developer has tooling to generate an
application to emit Common Base Events (as shown in Figure 5-22).
WebSphere Application Ser ver
Adapter WebSphere
WebSphere Adapter Business
Inbound
Monitor
Business Application Common
Objects Generated Base
Events
by CEI
WebSphere Adapter
RAD Tooling
Figure 5-22 An event message-driven bean (MDB) generated by Rational Application Developer
WebSphere Business Monitor includes SAP and Java Database Connectivity (JDBC)
samples to illustrate how to use adapters to deliver events to WebSphere Business Monitor.
5.3.9 Emitting custom events

WebSphere Business Monitor uses XML Schema Definition (XSD) to define events (shown in
Figure 5-23 on page 118), a standard for events among different distributed applications. This
standard ensures that the data elements that comprise these events are consistent.
Developers can define XSD-based user and system events in WebSphere Business Monitor
so that business objects (such as invoices and purchase orders) can be expressed as XSDs.
Figure 5-23 WebSphere Business Monitor showing XSD events
WebSphere Business Monitor REST application programming interfaces have been extended
to provide a new option for developers to make data available to WebSphere Business
Monitor. Using the REST event emitter service, you can enable applications to emit events
without having to code or generate common base events directly (Figure 5-24).
You provide the event XML; the event emitter service receives the event XML and wraps it in a
common base event so that WebSphere Business Monitor can process it. Event sources can
create an XML document and place the XML in a JMS destination or an HTTP POST URI
without having to know about the internal event format.
The REST emitter service can also be configured to use WebSphere MQ as the JMS
provider.
WebSphere Business
Monitor
3rd Party Applications
Arbitrary Event
JMS Message Queue
Source
JMS Header + Forwarded by
XML Monitor event
emitter service
Figure 5-24 Emitting events using the REST emitter service

You can also use WS-Notification as a custom event emitter, specifically the WS-Notification
client programming model, which sends events from Web service clients developed with
Java/J2EE or .NET.
5.3.10 Robust event handling

Given the heterogeneity and size of many enterprise IT infrastructures, a business monitoring
solution must provide high-quality service characteristics. The integrity of the monitoring
solution needs to ensure that reported business results are based on complete, timely, and
accurate events. For these reasons, WebSphere Business Monitor processes events quickly,
manages failover, isolates bad events, and ensures that the monitoring solution receives
events in the correct order.
When a tremendously large number of events need to be processed for monitoring and
business metrics need to be updated frequently, administrators can use WebSphere
Business Monitor to cluster event processing for scalability. They can deploy a monitor model
(shown in Figure 5-25) on multiple WebSphere Business Monitor servers for workload
balancing. If one server goes down or is unavailable, the high-availability manager ensures
that no events are lost.
MM Server Cluster
CEI Server Server 1

Events sprayed PatientVisit
across the cluster
Monitor Model
Event Stream Moderator

Events Server 2
(EJB Module)
PatientVisit
Monitor Model
Inbound event Moderator can be clustered
queue for Monitor for high availability
Model
Server 3
PatientVisit
Monitor Model
Figure 5-25 Cluster monitor model servers for workload management and high availability
When a process emits events, it is often critical that The high-availability

those events be processed in the correct order. If they
are not, incorrect business metrics are calculated. But manager ensures that
events are not always received in the correct order when no events are lost
the events are emitted asynchronously. For example, an
auditing monitor solution might identify internal requests
that have not been approved on an order. If WebSphere Business Monitor receives an On
order event before the Approved event, the monitor might raise a false alert in the dashboard
or compile incorrect data for a report. However, using WebSphere Business Monitor, the
solution can be configured to batch related events for processing, rather than processing
them in the order in which they were received. When all of the related events are received,
they are processed in the correct order, even if they arrived out of order.
5.3.11 Automating corrective and mitigating action
WebSphere Business Monitor provides a flexible and robust infrastructure for uncovering
current and potential future business anomalies, or business situations, and automating
responses to these situations.
The Action Services capability allows automated actions to be configured when the monitor
solution triggers business situations, enabling your organization to implement increasingly
effective responses to business situations that can arise as the insight into the business
environment evolves. A common automated action is to send notifications. Additionally, a
number of options exist for automated responses, including invoking Service Component
Architecture (SCA) applications (for example, a BPEL process or human task) and Web
services.

Developing robust BAM solutions involves two competing challenges: correlating data from a
broad heterogeneous environment and being able to develop a rich monitor model for that
environment quickly. The process of pulling in the correct data structures, having some
examples or templates to start with, and testing iteratively can be complex and
time-consuming without the right tools. By using the WebSphere Business Monitor
development toolkit, a developer can perform the following tasks:
Work with business analysts by leveraging a monitoring specification that is defined in
WebSphere Business Modeler as a starting point.
Reuse existing generic and industry-specific assets.
Easily monitor applications created in WebSphere Integration Developer.
Easily test a monitor model without deploying to a production environment.
5.4.1 Simplified iterative development

Effective model development is often approached iteratively: develop, test, enhance, and test.
WebSphere Business Monitor includes a full-function integrated test environment that
developers can use to assess the progress in defining monitoring models. The integrated test
client is a graphical interface that simplifies the emission of test events (shown in Figure 5-26
on page 121), so developers do not have to instrument a live production system for testing
purposes. The developer writes reusable test scripts that express both the events to be
emitted and the order in which to emit them. The integrated test client provides the flexibility
to define different combinations of test scripts to reflect various monitoring scenarios.

Load Save
New Save as
Clock
Pause
Import
Move up
Move down
Edit
D elete
Play Reset
Add Commit Canc el
Figure 5-26 Test monitoring models by using the integrated test client
With WebSphere Business Monitor, the steps required to deploy a monitor model application
are streamlined so that developers can automatically create the database tables, deploy the
generated EAR file to the monitor server, and start the monitoring solution simply by
right-clicking the monitor model to generate the monitor model application and then adding
the application to the test server, just like any other application. Developers can easily update
the monitor model and redeploy for fast iterative development.
The WebSphere Business Monitor development toolkit also simplifies the testing of Scalable
Vector Graphics (SVG) diagrams (shown in Figure 5-27 on page 122) so that developers do
not need to iteratively define the model, deploy it to the test server, emit test events, and
finally observe the behavior of the SVG diagram. They can add actions to the shape sets
directly, specify test data, and generate and render a static diagram all in the development
environment. No deployment or event emission is required.
ac tions metrics
Figure 5-27 WebSphere Business Monitor showing SVG diagrams
5.4.2 Achieve quickstart monitoring with WebSphere Process Server

The ready to use global BPEL monitor model helps monitor developers deliver quickly on
business requirements, showing the developer what BPEL and human task data is available
for monitoring, without the developer having to author a custom monitor model (Figure 5-28
on page 123).

Figure 5-28 Monitoring using WebSphere Process Server
The appearance of the global BPEL monitor model (as displayed in the WebSphere Business
Monitor dashboard) can be customized. For example, you can hide metrics (columns) that are
not important and apply filters to display only rows with certain criteria. You can create KPIs
that aggregate the values of the metrics in the global BPEL monitor model to be specific to
your business.
You can also enhance the global BPEL monitor model and further modify it using the
WebSphere Business Monitor development toolkit. The project interchange file for this
monitor model along with much more information about using the global BPEL mode is
available at this Web page:
http://publib.boulder.ibm.com/bpcsamp/monitoring/globalprocessmonitor.html
The development toolkit runs on WebSphere Business Monitor V6.2 or later, and can monitor
applications from WebSphere Process Server V6.1 or later.
5.4.3 Predefined templates and assets

WebSphere Business Monitor includes several predefined templates that support the
generation of monitor constructs in models (shown in Figure 5-29 on page 124) from several
applications and components, actions metrics such as BPEL, enterprise service bus events,
WebSphere Message Broker, WebSphere MQ Workflow events, SCA, and human tasks.
Figure 5-29 Defining monitoring models using predefined templates
5.4.4 SOA Business Catalog

The service-oriented architecture (SOA) Business Catalog is a comprehensive, online
resource for ready-made business models (or predefined assets) supplied by IBM and IBM
Business Partners that have been validated for enablement on IBM SOA products. The
catalog (shown in Figure 5-30 on page 125) holds thousands of assets, including adapters,
Web services, process models, and plug-ins that are regularly updated to keep pace with
business, technical, and regulatory changes and continually help you build your SOA
solutions. Third parties (for example, IBM Business Partners) can register licensed assets in
the catalog. The catalog provides an asset overview and details on where to get the asset
and accompanying documentation. To access the SOA Business Catalog, go to this Web
page:
http://www-304.ibm.com/jct09002c/gsdod/weblistfilter.do?prog=RFSOA&tab=0
You can search the catalog in many ways, including by using the following criteria:
Asset type (code, data, model, or tools)
Business need (for example, CRM, ER planning, business integration, or supply chain)
Industry focus (over 20 industries to choose from)
IBM SOA foundation product

Figure 5-30 IBM SOA Business Catalog
IBM provides assets that are based on a long history of developing domain expertise. For
example, assets that are associated with the Information Framework for Financial Markets
draw on over 100 person years of modeling and analysis work with the financial services
industry. Assets help you with such processes as post-trade processing and reporting,
account opening, know-your-customer initiatives, and regulatory compliance, typically
reducing analysis time by 40% and significantly accelerating the time it takes to secure
stakeholder approvals.
5.4.5 Industry accelerators

Developers can leverage sample monitoring templates and dashboards, which are aligned
with the WebSphere Industry Content Packs (ICPs), to accelerate the development of
end-to-end BPM solutions.
These industry accelerators are provided for the banking, healthcare, insurance, retail,
Product Lifecycle Management (PLM), and telecommunications industries. Figure 5-31 on
page 126 shows a business dashboard with the healthcare industry accelerator.
All WebSphere ICPs are available from the Monitoring section of the BPM samples Web
page:
http://publib.boulder.ibm.com/bpcsamp/
Figure 5-31 Business dashboard from the healthcare accelerator
5.4.6 KPI and Key Agility Indicator (KAI) libraries

KPIs are financial and nonfinancial measures that are generally expressed as cost, cycle
times, and efficiency. They are specific quantifiable values that assess the performance or
state of a business and the significant measurements used to track performance against
business objectives. A KPI has a target, ranges, or both, to measure the improvement or
deterioration in the performance of an activity that is critical to the business.
Standard key performance indicators are not enough to KPI and KAI libraries
measure how agile companies are, so business users
often look at areas such as human capital practices, and benchmarks
financial management practices, and supply chain facilitate quick ROI
operations and target areas to increase agility and meet
business challenges. What you are looking at are key agility indicators (KAIs), which are
combinations of key performance indicators, business drivers, and leading practice
statements that help evaluate how quickly and effectively a business can respond to changes,
opportunities, and threats. As such, a KAI can also be a KPI, but not all KPIs indicate agility.
KAIs determine a business ability to become a globally integrated enterprise that can sense
and respond to fluctuations in customer demand, detect and alert changes in real time, and
proactively monitor key business processes. The combination of new KAIs and traditional
KPIs gives you complete information to support business decisions.
For example, Perfect Order Performance is a KPI and a KAI. It is a measurement of agility that
reflects an organizations ability to sense and respond to the market fluctuations. This
indicator can be applied across many industries.

WebSphere Business Modeler and WebSphere Business Monitor have an embedded library
of over 800 open-standard KPIs, including more than 300 KAIs based on the APQC Process
Classification Framework (PCF). The KPI library enables KPI selection for various processes
across several functions, including financial management, human capital management,
customer relationship management, and supply chain management. Figure 5-32 shows how
a developer selects standard KPIs using the KPI library in the WebSphere Business Monitor
development toolkit.
Figure 5-32 Selecting KPIs using the KPI library in WebSphere Business Monitor
By working with IBM or APQC, benchmark values for the KPIs and KAIs can be obtained to
help define appropriate targets for the business. With the KPI library, business analysts can
quickly and easily discover and use KPIs to speed time to value when modeling business
processes and monitoring business activity.
5.4.7 Synchronization with WebSphere Integration Developer

To quickly use SCA modules from WebSphere Integration Developer and define monitor
models, WebSphere Business Monitor provides the Generate Monitor Model wizard (shown
in Figure 5-33 on page 128), which introspects an SCA module to generate a stand-alone
monitor model that is based on a predefined template for that type of SCA module (BPEL
process, human task, mediation, and so on). The generated model can then be modified.
Developers might generate the first monitor model from an application as a starting point.
Additional monitoring elements can be added as the solution grows. Or perhaps there was an
oversight to include some monitoring elements in the originally generated model, or there are
ongoing changes made to a model by a team of developers. In any case, developers maintain
the flexibility to add other monitoring elements iteratively, which allows both the application
and the corresponding monitoring solution to co-evolve. By using the integrated tools,
developers can keep the two code bases (runtime code and monitor model code) in sync,
without having to manually reconcile existing and updated monitor models.
Figure 5-33 Generating a monitor model from WebSphere Integration Developer
Changes to the names of WebSphere Integration Developer artifacts (for example, modules,
components, interfaces, namespaces, and business objects) are applied to the monitor model
through live refactoring. Other changes can be reconciled using synchronization facilities
(shown in Figure 5-34) to add or remove event sources, interface operation parameters, and
so on.
The Mon itor Mod el

Syn chro ni zatio n
wi nd ow gro ups the C ho ose the
a pp li catio n cha ng es resu ltin g ac ti on to
in to th ree take b y sel ectin g
categ or ies: added differ ent op ti on s in
el eme nts, r em ov ed the th ird co lu mn.
e le men ts, an d Fo r exa mpl e, wh en
change d el eme nts a mon itore d eve nt
sou rce i s d el eted ,
you can ch oo se to
al so de le te th e
mon itori ng
A che ck bo x i s el eme nts or
pl ace d un de r the d isco nn ect th e
ta ble so th at you ca n mon itori ng
h ide th e pa ren t tree e le men ts from the
ele me nts to fla tte n a pp li catio n.
the ch an ge tre es.
Th e b uil t-in Ecl ip se

h el p bu tto n op ens
th e he lp side -ba r
dir ectly o n th e
wi nd ow to o ffe r
i mme di ate
a ssista nce .
Figure 5-34 Synchronizing changes between WebSphere Integration Developer and WebSphere Business Monitor

5.4.8 Synchronization with WebSphere Business Modeler
Different users can provide input to a monitor model definition. The business analyst can use
the Business Measures view (shown in Figure 5-35) of WebSphere Business Modeler to
define the broad characteristics of KPIs and other business metrics. Then the WebSphere
Business Monitor developer can import these definitions into the WebSphere Business
Monitor development toolkit as a starting point to more advanced monitor model
development.
In addition, business analysts can easily define business measures and test processes
directly on a test server using business measures from WebSphere Business Modeler,
without the need to export to the development tool. Thus, business analysts can define a
business process and associated measures, test the process execution and business
measure calculations, visualize the business measures, iteratively make adjustments, and
add additional business measures and retest, all without involving IT, which greatly simplifies
solution development and reduces the time to value.
Figure 5-35 Business Measures view in WebSphere Business Modeler
With WebSphere Business Monitor, developers can iteratively review updates coming from
WebSphere Business Modeler, compare how changes affect the currently implemented
monitor model, and easily synchronize selected changes.
5.4.9 Developing using Rational Application Developer

What needs to be monitored determines which tool platform to use. With WebSphere
Business Monitor, your organization can choose from two tool platform choices:
WebSphere Business Monitor development toolkit, which is built into WebSphere
Integration Developer to help you maintain first-class integration to monitor BPEL-based
solutions, SCA, or other components, and use patterns-based monitor model generation,
refactoring, and synchronization.
For BAM solutions that do not require the ability to monitor components running on
WebSphere Process Server or WebSphere ESB, install WebSphere Business Monitor in
Rational Application Developer and benefit from the smaller footprint of Rational
Application Developer.
5.4.10 Full-function unit test environment with interactive debug

WebSphere Business Monitor enables the rapid development of monitoring solutions. A
full-function development test environment, including a comprehensive graphical debugger,
enables the complete testing of monitoring solutions before deployment to a full-fledged
production environment (Figure 5-36).
Figure 5-36 Using the WebSphere Business Monitor graphical debugger
5.4.11 Event recording and playback

Administrators and developers can configure the business monitoring solution to store
incoming events that can be replayed later, which developers can use, for example, to
iteratively test a monitor solution. Now administrators and developers can save a set of test
events, update a monitor model, redeploy the monitor model, and replay the saved events to
evaluate the changes made to the monitor model (Figure 5-37 on page 131).

Figure 5-37 Administering event recording and playback in WebSphere Business Monitor
5.5 Lowering the total cost of ownership

The time and effort required to install and administer a monitoring solution must be minimal.
To speed the installation and administration steps, WebSphere Business Monitor provides
flexible options that administrators can use to customize the configuration of the IT
environment and easy-to-use administrative capabilities to ensure that monitoring data is
properly replicated and security is effectively enabled.
5.5.1 Flexible configurations

Not all business monitoring requirements are the same. Some people want a robust portal
infrastructure that will serve as the framework for business monitoring. Some people might
need to enable dimensional analysis to generate multidimensional reports and analyze
different dimensions of data. Still others look for a lightweight infrastructure to get started.
WebSphere Business Monitor now provides a Web-based dashboard that uses REST
services for data access, JavaScript Object Notation (JSON) for data exchange, and the Dojo
open-source AJAX toolkit for dashboard rendering. Configuring a business space requires
WebSphere Application Server only.
To flexibly accommodate various configuration needs, WebSphere Business Monitor supports

four configurations:
A business space Web-based dashboard, which is a lightweight configuration
A business space Web-based dashboard plus dimensional analysis, which includes DB2
Alphablox, enabling a light configuration for both real-time and historic trend analysis
WebSphere Portal-based dashboard, which is a dashboard configuration rendered in
WebSphere Portal Server to offer integration in a broader collaboration environment
WebSphere Portal-based dashboard plus dimensional analysis, which is a portal-based
dashboard with DB2 Alphablox, providing complete monitoring capabilities in the
WebSphere Portal collaboration environment
These configurations are complementary. Therefore, a monitoring solution can be initially

deployed on a Web-based dashboard and then subsequently modified for deployment on a
portal framework. Figure 5-38 shows the end-to-end monitoring life-cycle steps for the
Web-based dashboard configuration.
1
WebSphere
Event d ata Monitor
sources Devel opme nt
Toolkit
2 9
3 Authorization REST Services
Mon ito r Model

Ap plication
6
4
Acti on
Services
8
Figure 5-38 End-to-end monitoring life-cycle steps for Web-based dashboard configuration
The numbers in Figure 5-38 correspond to the following actions:

1. The business analyst defines and deploys the monitor model using WebSphere Business
Monitor development toolkit (which is installed on Rational Application Developer or
WebSphere Integration Developer).
2. Event sources emit events that contain business-relevant data.
3. Inbound event data is received through the Common Event Infrastructure (CEI).
4. Event data is correlated through the deployed monitor model.
5. Additional data is retrieved from data sources using user-defined functions.
6. Business situation events are filtered, and relevant events are returned to the CEI.
7. Action services process the business situation events.
8. Outbound actions and events are handled and written to the WebSphere Business Monitor
database.
9. Business metrics are displayed in a business space.

5.5.2 Simplifying administration
WebSphere Business Monitor simplifies the administration of monitor models, security, and
user registries.
For deployment on a production server, WebSphere Business Monitor enables flexible control
regarding monitor models (shown in Figure 5-39). There are specific pages for monitor model
deployments that streamline running the schema and DMS scripts and setting up cube and
CEI configuration information.
Figure 5-39 Selecting monitor model options of deployment time
Using the Monitor Topology Configuration wizard, you can create flexible deployment
topologies, recommend a topology, and make it easy to install (Figure 5-40 on page 134).
Figure 5-40 Create flexible deployment topologies
5.6 Summary
With WebSphere Business Monitor, business users can assess and manage business
activity. The range of activity that can be monitored varies widely: from activity on human or
automated tasks to activity on process-oriented or data-driven solutions to obtain operational
or strategic insight. Business users can determine the kind of dashboard to use (Web-based
or portal-based) and the relevant data that you want shown on the dashboard, all in a scalable
and secure environment.

6
Chapter 6. Enabling dynamic BPM with

WebSphere Business Services
Fabric
WebSphere Business Services Fabric helps you enable business agility and provides the
following features and benefits:
Enables extremely rapid business process changes
Organizes a business process management (BPM) and service-oriented architecture
(SOA) infrastructure into flexible modules, called intelligent business services, that can be
shared
Governs changes that business users make to reflect changes in corporate policy and
ensure that the changes are proliferated across all processes
Accepts new functionality to a process without changing or redeploying the process
Improves the manageability of complex BPM projects and significantly lowers total cost of
ownership (TCO)

6.1 Introduction
Every business, regardless of its size or the industry to which it Being able to
belongs, is faced with the challenge of changing business
processes rapidly, and responding quickly to new demands for adapt rapidly
process variations. Organizations need to be able to create new and flexibly can
innovative business models, deliver new and exciting products
and services, and customize their products and services to set your
varying customer segments. Adding new geographies, channels, company apart
partners, suppliers, and products are examples of how processes
are rapidly becoming complex in the marketplace. Adding to that
from the rest
complexity are infrastructure changes resulting from system
consolidations to mergers and acquisitions or existing system modernization. Wherever the
need originates, being able to adapt to these changes rapidly and flexibly can differentiate
your company from your competitors. The faster a company can incorporate change, the
more agile it is, and the more competitive it can be in the marketplace.
Business process management (BPM) enabled by service-oriented architecture (SOA) helps

you manage and control continuous change. WebSphere Business Service Fabric builds on
the SOA foundation with support for dynamic processes, processes that account for
variances based on business process context, such as the customer making the request (for
example, a premium customer or a non-premium customer), the channel over which the
request was made (for example, the call center or the Internet), request data (for example, the
loan amount), and when the request was made (for example, during regular hours or outside
of regular hours).
6.2 A foundation for dynamic BPM

WebSphere Business Services Fabric delivers dynamic BPM capabilities to manage process
variance and change. With WebSphere Business Services Fabric, you organize business
functions into reusable business services, isolate the life cycles of these business services
from the processes that use them, and combine these business services into composite
business applications.
While organizations adopt SOA as a way to improve business agility, drive innovation, and
make the most of their IT investments, composite business applications developed using
WebSphere Business Services Fabric can help them gain improved flexibility by leveraging
distributed, loosely coupled business-level services that are exposed from existing systems,
packaged applications, outsourced service providers, custom applications, and other
third-party IT assets.
6.2.1 Business services

The building blocks of composite business applications are business services. A business
service represents a business function whose behavior can be adapted at run time. A
business service is based on the operating context of the request and the policies established
to meet the service consumers needs. Business services can also be considered
coarse-grained Web services. A business service is an abstract representation of a business
function, hiding the specifics of the function interfaces. It provides a separation of concern
between the business function and the implementation supporting it. The ability to attach

metadata to business services and processes differentiates WebSphere Business Services
Fabric from other tools and infrastructure and provides a powerful and expressive way to
maintain flexibility in service composition.
A business service is not a technical service; it does not define operations, port types, or
binding information as a technical Web service does. In contrast, a business service
addresses the remaining information that is necessary to place the service in context and
apply it correctly, such as service availability, user entitlements, lines of business supported,
and the relationship that one business service has to other services.
A business service bridges the understanding between business and IT, making it possible for
business and IT users to perform the following tasks:
Establish a consistent model for services so that they can be correctly understood.
Capture business constraints around service delivery.
Map core business functions to supporting IT capabilities.
Simplify the design, implementation, and maintenance of business processes.
Govern the assembly of services into composite business applications.
Business services can be described as the intersection of three characteristics:

Who uses them
How they are made available
What functionality and capability they provide
A business service is the encapsulation of these characteristics as illustrated in Figure 6-1.
Delivery M eth od s W eb Por tal CRM

Processes, rules, agreements, IVR
and preferred channels

Business Service
Pre- App roval
Policies
Risk Asse ss ment
Policies Policies
En titlements fo r
HOW Service Ass ertio ns
for IT asset s
Role-based process
participants Business including LOB silos
and M&A
Service
WHO WHAT
Operati onal Capabil iti es
CSR
C on sum e rs
Credit C re dit Customer Customer

Lookup : Eli gibil ity: Profi le: No tification:
3rd Party Legacy Packaged Custom
CR M J2EE
Figure 6-1 A business service describes the who, what, and how of a business function
6.2.2 Composite business applications

A composite business application (CBA) is a collection of related and integrated business
services that provide a specific business solution and support multiple business processes
built on SOA. At first glance, a CBA might look like a collection of business services. However,
a CBA is a broader, more comprehensive view of the business solution that leverages the
business services to deliver the ultimate solution, driving the process, channels, roles, and
business object model of the overall business solution.
Chapter 6. Enabling dynamic BPM with WebSphere Business Services Fabric 137
A CBA shares many of the characteristics that are associated with business services:
Delivers a specific business outcome, because it is designed at the business level
Uses business service policies and metadata to describe and explain service and solution
characteristics, such as costs, availability, supported roles, supported channels,
standards, and operational capabilities
Leverages industry models to support interoperability and common understanding
Supports multiple consumption channels, such as Web and B2B
Unlike business services, a CBA is pulled together at run time; it is dynamic and is also more
specialized, particularly when noting the solution data model, channels supported, and roles
and organizations to which it has been entitled. The following attributes and characteristics
are associated with a CBA:
Consumer channels
Business processes
Business service policies
Business object model and data model
Metadata model and extensions
A more coarse-grained business solution process model
A CBA also lets you consolidate information, creating distinct opportunities for discovery and
change over the life cycle of the application. As noted with business services, a CBA also
represents the dynamics and understanding that will be enacted when the application is
called upon.
6.2.3 Dynamic assembly

By developing and delivering CBAs and business services with WebSphere Business
Services Fabric, you can realize flexible and agile solutions, creating solutions that can be
built and managed at the pace of business, because services are dynamically assembled
while CBAs and business services run.
CBAs and business services require expressive metadata that provides a comprehensive
description of the artifacts. Additionally, business service policies or business knowledge can
be represented as metadata, which creates an understanding of the business service and
CBA that is meaningful and insightful regarding both business expectations and technical
considerations. This information is leveraged at run time to influence how CBAs and business
services run, ultimately allowing solutions to be composed in declarative terms and delivered
at run time.
Moreover, for dynamic assembly, you are not required to create programming logic by writing
procedural code. Instead, you leverage the declarative knowledge of the metadata and a
runtime capability that can digest the metadata and the current known circumstances of the
moment, such as the business context. When the metadata and business context are
processed, the guidance is provided to the CBA and business service, thereby customizing
the current instantiation.
When much of the guidance is based on metadata and business context, the guidance used
for the CBA and associated business services changes if the metadata changes. This
powerful concept is the key to realizing flexibility and agility. In WebSphere Business Services
Fabric, the guidance provided to the business service at run time is the intersection of three
concepts:
The operating context of the CBA or business service, such as which role is instantiating
the request, over which channel, at what time of day or day of year

Information in the request payload that might be relevant to the metadata authored in
policies or attached to services. For example, if the Loan Application CBA were invoked, it
would be important to know if the request was for a home loan or an automobile loan. The
content of the invocation messages typically contains this data.
The capabilities, restrictions, and preferences for a CBA or business service. This contract
is defined at run time and is a combination of the metadata and business service policies
that are relevant for the particular circumstances.
The series of events that occur at run time are pictured in Figure 6-2.
Consumers Channels Service Implementations
4
Busin ess Services
Repository Policies Customer Verify
Lo an Officer Metadata
Cred it Ch eck
3 C BA Metadata
5 Rating - Stand ard
Metadata
Metadata
Web Rating - Lu xury
Po rt al 2
Cu sto mer 1
Loan App Process Dynamic

Assembler
Figure 6-2 The series of events that occur at run time
The numbers in Figure 6-2 correspond to the following actions:

1. The endpoint implementations are defined. For example, one endpoint is for a Luxury
Home Loan rating and the other is for a Standard Home Loan rating. These endpoints are
existing capabilities that have been service-enabled. The technical specification for the
service implementations is available from a service registry, such as WebSphere Service
Registry and Repository.
2. A Loan Rating business service is created, and metadata describing the business service
is published to a metadata repository. The business service is associated with both the
Luxury Home Loan rating and the Standard Home Loan rating service implementations.
3. The Loan Process CBA is created, and metadata describing the service is published into a
metadata repository. The Loan Process CBA creates the Loan Rating business service
and other services, such as the Customer Verification service and the Customer Credit
Check service (not shown in Figure 6-2).
4. A business service policy has been created and published to the metadata repository. The
business service policy states all home loan applications that are greater than or equal to
500,000 are considered luxury homes and all home loan applications under 500,000 are
considered standard homes.
5. A home loan may be requested by a Bank Loan officer or a customer directly. Two
channels exist: a browser interface for the customer-direct loans and a branch office batch
interface for Bank Loan officer-initiated loans.
The numbers in Figure 6-3 on page 140 show the series of events that occur at run time.
Busin ess Services

Cred it Ch eck
C BA Metadata
Metadata Rating - Stand ard
Metadata
Po rt al
Cu sto mer
9 10
>600k Dynamic
6 Loan App Process
Assembler Luxury Rating meets the business
service policy criteria
7
8
Figure 6-3 The series of events that occur at run time
6. The loan application has been directly requested by the customer and the home loan
application is for 600,000.
7. The Loan Process CBA is instantiated with the loan application. Customer Verification and
Credit Steps are completed, bringing the application to the Loan Rating service.
8. The Loan Rating service has two possible process variations: Luxury Home Rating or
Standard Home Rating. The Loan Rating service defers the decision regarding the
process variation to the runtime engine, the Dynamic Assembler.
9. The Dynamic Assembler reviews the context of this request (Customer-Direct over Bank
Loan officer channel), the content of this call (Loan Application greater than 500,000), and
all metadata and policies to assemble the contract or select the business service policy.
One business service policy is applicable; it says that all loan applications greater than
500,000 are considered Luxury Home Loans.
10.The Dynamic Assembler realizes that two process variations exist for the Loan Rating
service; however, only one variation meets the business service policy criteria of rating a
luxury home. The Dynamic Assembler selects the Luxury Home variation of the Loan
Rating service, completing the loan application process.
This example illustrates the actions taken in WebSphere Business Services Fabric to
dynamically assemble business services. However, WebSphere Business Services Fabric
also ensures flexibility and agility when additional business requirements come into play, such
as if this application process required that all loans over 900,000 be underwritten by a third
party, using their XtraBigLoans rating engine.
Because this Loan Processing solution uses business services and composite business
application concepts implemented by WebSphere Business Services Fabric, only two
additions to the CBA are required to meet this new requirement:
1. A new Loan Rating process variation that supports XtraBigLoans.
2. A new business service policy stating that all loans greater than or equal to 900,000 are
XtraBigLoans.

Figure 6-4 shows that all loan applications greater than 900,000 will be rated using the
XtraBigLoan rating process variation.
Busin ess Services

Cred it Ch eck
Metadata
C BA
Metadata
Rating - Standard
Metadata
Metadata
Po rtal
Cu sto mer
Rating - XtraBigLoan
Dynamic New
>900k Loan App Process
Assembler
Add service implementation

and endpoint metadata for
XtraBigLoan rating
Figure 6-4 To accommodate changes, you can add new business service policies easily
With just a few simple additions, our Loan Process was able to adapt and react to new
business requirements, effectively managing the process at the pace of business.
6.2.4 Business service repository

Core to WebSphere Business Services Fabric is a comprehensive Business Service
Repository (BSR), which is a place to model, store, and manage the metadata, business
service policies, and entitlements necessary to describe and use business services. The BSR
is more than just a container of information. It provides the means by which information is
organized and arranged, not only for retrieval but also to clarify understanding through the
organization of metadata and relationships between business services, business service
policies, and subscriptions.
The BSR provides the basis for the governance and life-cycle management of information
with regard to creation, ownership, modification, and classification. It also incorporates
ontologies to model the business services knowledge domain. An ontology describes the
vocabulary, structure, constraints, relationships, and behaviors of business services,
providing a rich and comprehensive representation and understanding.
Ontologies enable the applications that refer to them to be standardized while allowing the
information that they contain to be changed. The WebSphere Business Services Fabric
ontology can be extended using WebSphere Business Services Fabric authoring widgets
available in business spaces. Additionally, ontologies can be modeled with Resources
Definition Framework (RDF) and Web Ontology Language (OWL), which are W3C standards,
making them extensible and allowing them to adapt to future requirements.
The BSR model is persisted to a relational database management system, enabling
enterprise-level manageability.
6.3 Enable agility with business service policies

WebSphere Business Services Fabric abstracts the logic of how Drive process
services are assembled and contextualized out of business
processes and puts it into metadata and policies. A business changes using
service policy represents how the business intends the business business
process and services to operate in a given business context or
scenario. You can accelerate your ability to act on dynamic service policies
process changes by abstracting this type of logic into metadata and avoid costly
and business service policies that are centrally stored and
coding changes
managed.
Traditionally, making changes to business processes and services required changing code,
which often required a lengthy and costly redeployment cycle. With WebSphere Business
Services Fabric, you can drive process changes using business service policies, avoiding
costly coding changes. You can also manage the life cycle of business service policies,
making business service policy changes quickly while completely controlling and visualizing
those changes, simulating them, and creating business service policy programming models
and expressions.
6.3.1 Business service policy simulation

WebSphere Business Services Fabric includes an environment on which you can simulate
how the runtime environment selects the best business service variation based on the
operating context. You can model your business service policies and run a simulation
immediately to see how the runtime environment enforces these business service policies,
which is a key advantage of the WebSphere Business Services Fabric declarative approach.
Simulation can be done before committing the policies to the BSR, which means that changes
can be tested in isolation before they are worked into the governance policy. Conversely, in an
imperative programming approach, you must write code that specifies how business service
policies are enforced, which results in longer testing cycles, because the code has to be
compiled and deployed to a runtime environment before it can be tested.
With WebSphere Business Services Fabric, you can save, share, and reuse your simulations,
which means that you can build test harnesses of simulations that you can quickly rerun to
validate and verify the changes that were made to the business service policies. Figure 6-5
on page 143 shows a simulation being created.

Figure 6-5 Creating a simulation
When you create simulations, the correct inputs are automatically generated based on the
context specification that you defined, taking the guesswork out of defining the criteria used
for a specific service-selection scenario. Simulation results provide more detailed information
about the set of policies that are triggered for a given business context, the service endpoints
considered, and the service endpoint selected. In the case of failure, the system displays the
specific point at which the simulation failed and the reason for the failure, showing how the
policies are enforced to determine the root causes of issues. Figure 6-6 on page 144 shows
simulation results.
Figure 6-6 Simulation results
6.3.2 Programming business service policy modeling using context

specifications
WebSphere Business Services Fabric significantly enhances productivity when building,
testing, and deploying business service policies using context specifications. A context
specification defines the set of dimensions required for a service-selection scenario and
serves the following purposes, among others, in the business service policy life cycle (for
example, customer type and amount assertions):
Documenting key criteria that are used for evaluating business service policies to drive a
service-selection scenario
Serving as a contract between what was modeled and the runtime environment, ensuring
that only the necessary dimensions or relevant business service policies for a business
context are present at run time and are considered for a service-selection scenario and for
evaluating business service policies
Automatically generating the simulation user interface with correct selection criteria,
ensuring that each service-selection scenario is properly tested
Enhancing performance by allowing the runtime environment to employ smart caching
strategies
Figure 6-7 on page 145 shows the context specification editor and simulation user interface
with selection criteria automatically generated based on the context specifications.

Figure 6-7 Context Specification editor and simulation user interface showing selection criteria
6.3.3 Expressive business service policy power

A key advantage of WebSphere Business Services Fabric is that the runtime environment
understands the modeled business service policies. You do not have to write code to enforce
the semantics of the service-selection business service policies when you extract content and
insert it into the context; the semantics are enforced exactly the same way as how you
modeled and simulated them in Composition Studio. WebSphere Business Services Fabric
includes assertions, comparators, and operators that you can immediately incorporate into
your modeling business service policies.
6.3.4 Authoring business applications

A composite business application represents the flow of a process from one business service
to another (shown in Figure 6-8 on page 146). It allows a business user to quickly visualize
the role of a business service in a given business process and provides meaningful scoping
for business service policies.
Figure 6-8 A composite business application showing a single browser channel input and a series of business services
Business services have at least one implementation, which is called a process variation.
A process variation can involve a human-centric process, a fully automated process, or a
callout to an outsourced service. A business service represents a business decision point that
uses policies to determine which variation to use, embodying an important value that the
WebSphere Business Service Fabric delivers: the ability to modify existing variations or
deploy new variations without modifying or redeploying the existing application.
6.3.5 Authoring business service policies

There are two tools for authoring business service policies: Composition Studio is available
for IT users to create technical policies and business spaces are available for business users
to create business service policies. Technical policies are isolated from business policies, and
the Dynamic Assembly components that are not CBA-enabled cannot access the business
policies. Components that are CBA-enabled can access both the business and technical
policies.
6.4 Web-based authoring

Business users can author business service policies in business spaces using the three
templates of the WebSphere Business Services Fabric authoring widgets. The Fabric
Administrative template provides the governance capabilities for managing access to the
artifacts in the repository. In previous releases, this ability was available only in the Fabric
Administrative Console. The Business Process Agility template supports changes to business
service policies and business variables without IT intervention. The Fabric Authoring template
helps you create applications, business services, vocabularies, and business service policies.
Using these widgets, you can demonstrate WebSphere Business Services Fabric technology
that is not only tied to the IT professional, but available to the business user, improving the
integration of WebSphere Business Services Fabric into the end-to-end BPM story.
6.4.1 Authoring vocabulary

Terminology that is tailored for a business is important to facilitate a productive business-IT
alignment. A business vocabulary describes a business domain that is composed of concepts
and relationships. Vocabularies can be reused and extended, and a business application can
rely on concepts that are drawn from several different vocabularies. WebSphere Business
Services Fabric ships with a core BPM Vocabulary that defines some basic concepts

including role, channel, and the has relationship type. This basic vocabulary can be
expanded by using the Fabric widgets in a business space.
A vocabulary is used to extend the terminology of business context and policies. The
vocabulary-building capabilities in a business space replace the need to model content-based
assertions. New vocabularies can be created to capture business domain knowledge, such as
domain-specific business concepts, definitions, and relationship types. New roles and
channels can also be added to a vocabulary. These concepts can span business services.
Figure 6-9 shows the wizard for creating a new channel in a business space. The user is
required to select an existing change set or create a new one.
Figure 6-9 Creating a new channel in a business space using WebSphere Business Services Fabric
authoring widgets
A business concept is a basic element of the vocabulary that can be used as a building block
of a business service policy. It can be a simple type, such as a date, integer, or text, or it can
be a complex object and represent the input, output, or both of a service request. The type
definition determines the control, value range constraints, and comparators that are available
when authoring policies.
Figure 6-10 on page 148 shows the wizard that is used to create a complex business concept
called Mortgage Application. Complex objects are composed by creating has relationships
between the complex object and its constituent parts. In Mortgage Application, under
Relationships, you can see many has relationships to other business concepts along with
the cardinality of the relationship.
Figure 6-10 Wizard used for creating a complex business concept
When authoring business service policies, the vocabulary that is available for creating
conditions is based on the inputs of the business services that are involved. For example, the
Mortgage Application business concept from Figure 6-10 will be defined as the input and
output of the Final Review business service, shown in Figure 6-11.
Figure 6-11 The Final Review business service has a defined input and output to the Mortgage Application business
concept

To write business service policies in a business space, define new vocabulary concepts that
represent business parameters, and then create policies that attach values to these
parameters for specific circumstances.
The business service policy model follows the For-When-Then syntax. The For clause
represents a business service or application. The When clause represents a condition; it must
be true for a business service policy to apply. It supports complex expressions using AND,
OR, or NOT and vocabulary-based conditions (shown in Figure 6-12).
Create Condition
Condition:
Select an operator:
Field Name:
AND, OR, or Not
Comparator: Damage Type
Value: Line of Business
Simple concepts derived Channel
from business service inputs Role
Conditions are based on

Role or Channel Ok Cancel
Figure 6-12 The When clause of a business service policy uses complex expressions and vocabulary
The Then clause, shown in Figure 6-13, can have two results: select a variation (business
service implementation) or establish context by assigning a value to a business concept.
Figure 6-13 The Then clause of a business service policy can assign a value to a business concept
6.5 Integrated and aligned with the WebSphere BPM portfolio

WebSphere Business Services Fabric is better integrated and aligned with other capabilities
in WebSphere Dynamic Process Edition, allowing it to be leveraged as part of a larger
BPM-based solution.
6.5.1 Programming model alignment
WebSphere Business Services Fabric leverages the same Service Component Architecture
(SCA)-based programming model as the other products in the BPM portfolio, enabling you to
create business services. Figure 6-14 shows the WebSphere Business Services Fabric
runtime component exposed as an SCA component that can be leveraged along with other
BPM runtime capabilities that are exposed as SCA components to build solutions.
Figure 6-14 WebSphere Business Services Fabric leverages an SCA-based programming model
6.5.2 Integration with WebSphere Business Modeler

Using WebSphere Business Modeler, the business analyst can import composite business
applications, services, and vocabularies that have been defined using the Fabric widgets in a
business space. The business analyst can then further define the resulting model elements
and export them to the integration developer who uses WebSphere Business Services Fabric
as a runtime environment.
WebSphere Business Modeler integrates with WebSphere Business Services Fabric so that
the business analyst can model and implement business service policy-driven processes.
When they are instantiated, the business service policies that drive these processes can be
updated without requiring the process implementation itself to be changed, allowing for
quicker and more flexible updates to the process flow.
Models intended for implementation in WebSphere Business Services Fabric can be

completely designed using WebSphere Business Modeler, but a more complete development
process is to perform the following tasks:
A technical business analyst imports the information from the repository into WebSphere
Business Modeler, which creates global processes, services, business objects, and roles.
The technical business analyst continues to refine the model, fully defining the processes
that are associated with each service, or creating new ones.
The technical business analyst then uses the WebSphere Integration Developer export to
make the model information available to the developers who implement the processes in
WebSphere Business Services Fabric. Any service that is related to a process becomes
the interface of that process.
6.5.3 Integration with WebSphere Business Monitor

The WebSphere Business Services Fabric generates several Common Base Events that can
be monitored using WebSphere Business Monitor. By monitoring the WebSphere Business
Services Fabric-generated Common Base Events, custom Key Performance Indicators (KPIs)
can be created to provide useful data about business decisions made using WebSphere
Business Services Fabric.
Table 6-1 on page 151 describes the WebSphere Business Services Fabric events that are
related to SCA component information.

Table 6-1 WebSphere Business Services Fabric events that are related to SCA component information
Event Description
Context Extraction event This event is fired whenever the Dynamic Assembler processes a
context extractor. The Context Extraction event captures the current
and parent contexts.
Dynamic Selection event This event is fired upon every successful service invocation. The
Dynamic Selection event captures details about the dynamic
selection of an endpoint, such as the endpoint ID and address.
Endpoint Not Available This event is fired when the selected endpoint is not available at the
event time the request is made, such as during specified hours. The
Endpoint Not Available event captures information about the resulting
error.
No Endpoint For Policy This event is fired when the Dynamic Assembler does not find
event endpoints that match the criteria in the policies. The No Endpoint For
Policy event captures information about the resulting error.
Technical Error event This event is fired when a plug-in, such as a Context Extraction or
Policy Guard, fails. The Technical Error event captures information
about the resulting error.
6.6 Summary
Companies need flexible solutions to support change in an environment of increasing process
complexity. Composite business applications, which are assembled from business services,
can meet these needs by dynamically adapting business functionality based on changing
business context and business service policies. Additionally, by storing business service
policies in one centralized location to govern the behavior of business services, you can more
easily change and maintain processes and perform impact analysis. WebSphere Business
Services Fabric broadens the BPM-enabled SOA approach to achieve these benefits.
7
Chapter 7. Accelerating time-to-value with

WebSphere Industry Content
Packs
You can accelerate time to value on business process management (BPM) projects by using
WebSphere Industry Content Packs (ICPs). Extensible by enterprises and their business
partners, WebSphere ICPs provide pre-built, industry-standards-based assets that help you
reach the following goals:
Speed BPM solution development with deployable end-to-end scenario solutions
Obtain consistency and reuse across solution development
Use assets influenced by industry standards and customer requirements
Simplify interoperability between disparate IT assets and reduce project risks
Standardize connectivity to disparate applications

7.1 Introduction
WebSphere ICPs, based on industry standards and certified on the WebSphere Dynamic
Process Edition portfolio, accelerate the adoption of BPM and facilitate faster realization of
the following benefits:
More rapid BPM solution development because of the industry-focused design, which
means that you can jump-start your solution development with pre-built assets that
embody common standards for your industry.
Consistency and reuse for locations, product lines, and processes because they are
optimized for industry standards and best practices. All of the constituents involved in
building your solutions will have a shared understanding and use the same terminology for
roles, business items, and service definitions. This terminology can be extended based on
the needs of your business.
Visibility into component reuse across the organization due to the method of decomposing
business capabilities into process maps and process models and linking the capabilities to
these process maps and flows.
Simplified interoperability between disparate IT assets by defining the common language
to broker the communication between these assets.
Standardized connectivity to disparate applications in the IT ecosystem with pre-built
services that are based on industry standards.
Predefined service decomposition into which clients and partners can plug their
service-oriented architecture (SOA) assets.
The ability for enterprises (and their business partners) to extend the supplied content by
adding their own content to suit unique business needs, which helps enterprises move
away from the costly rip-and-replace exercises of proprietary systems and applications.
WebSphere ICPs are currently available for the following industries:

Telecommunications
Banking
Insurance
Healthcare
Industrial Product Lifecycle Management
In this chapter, you will learn about the core tenants and structure of WebSphere ICPs, the
benefits realized when using a WebSphere ICP, how WebSphere Industry Content Pack
assets accelerate the various steps in the BPM business-driven solution implementation
approach, and the WebSphere Industry Content Packs asset navigator component. You will
also see an overview of each of the WebSphere ICPs, including examples of the provided
asset types.
7.2 WebSphere Industry Content Pack core tenants

To accelerate the return on investment for BPM projects, WebSphere ICPs follow a consistent
approach for providing pre-built assets and associated collateral, adhering to the following
core tenants:
Supplied industry-specific assets can be used quickly to address the key opportunities
and pain points that your industry faces today. For example, the WebSphere Insurance
ICP provides assets for use in the distribution, claims, policy, and customer care lines of
business.

Industry standards and best practices guide the implementation of the provided assets,
facilitating the adoption of standard practices and mechanisms and, therefore, promoting
reuse and process agility. ICP assets do not replace industry standards.
Assets are provided that support the entire business-driven BPM solution development
approach but allow you to adopt the portions of interest to you and incrementally explore
and adopt additional parts of the cycle as you see fit. You can use the assets to accelerate
any entry point in the life cycle, and then, as your organization evolves, add parts of the life
cycle.
Assets leverage the WebSphere Dynamic Process Edition portfolio. However, because the
assets can be used incrementally, you do not need to use the entire portfolio to realize
benefits. Assets or subsets of assets can be imported into the appropriate tool
components, depending on the requirements of the solutions being built.
Deployable scenarios provide entire end-to-end solutions that span the WebSphere
Dynamic Process Edition portfolio.
WebSphere ICPs include assets that support the entire WebSphere BPM solution
development cycle. Figure 7-1 describes the types of assets that are provided with each
WebSphere ICP and the associated WebSphere Dynamic Process Edition product that you
use with those assets.
Configurable and extensible BPM solution assets
Capability Models Process Models Service Models

Capability Maps & Process Maps Process Flows & Business Service Interface & Schemas
align business strategy with Measures simulate human facilitate creation & assembly of
process execution workflows & automate processes process implementations
Tooling: WebSphere Tooling: WebSphere Tooling: WebSpher e
Business Compass Business Modeler I ntegration Developer
Common Components Business Vocabulary Business Object Models

Common Services & Utilities Repository of Business Conceptual Data Models to
enable interoperability with the Concepts, Terms & Relationships provide a foundation for
application ecosystem to ensure consistency information management
Tool ing: WebSphere Tooling: WebSphere Tooling: Rational
Integration Developer Business Services Fabr ic Software Architect
BPM Solution Scenarios

Includes UI Forms, Dashboards, Business Space Skins, Process Implementation
Figure 7-1 Asset types provided with WebSphere Industry Content Packs
Table 7-1 on page 156 summarizes the targeted business domains, the standards used for
each type of asset, and the provided solution scenarios for each ICP.
Chapter 7. Accelerating time-to-value with WebSphere Industry Content Packs 155

Table 7-1 Targeted business domains, standards for assets, and solution scenarios of each ICP
WebSphere WebSphere WebSphere WebSphere WebSphere
Telecom ICP Banking ICP Healthcare ICP Product Insurance ICP
Lifecycle
Management ICP
Targeted Fulfillment, Core Enrollment, Product data Distribution,

business assurance, banking, member and management, policy, claims
domains and billing, payments group, claims engineering and customer
standards customer and and provider change care for
used interaction, securities, collaboration management, Personal,
inventory, integrated Based on bill of material Commercial
catalog and risk HL7, ASC management, and Life
media management X12 EDI and supplier Annuity LOBs
processing and customer (HIPAA) collaboration Based on
Based on care standards segments for ACORD, IAA,
eTOM, SID, Based on and best Auto, IRI, eEG7
NGOSS ISO 20022, practices Aerospace standards
standards IFW, SEPA, and
NACHA Electronics
standards Based on
OMG PLM
Services 2.0,
VDA 4965,
OA-GIS 9.2
and best
practices
Capacity Based on eTOM Based on APQC Based on HL7 Based on APQC Based on
models Process and best and best and best practices ACORD and best
Framework practices practices practices
Process Based on eTOM Based on APQC Based on best Based on APQC Based on best
models Process and best practices and best practices practices
Framework practices
Service Based on SID Based on IFW Based on HL7, Based on OMG Based on IAA, IRI
models Model and best and best ASC X12, and PLM Services 2.0, (NAVA), and best
practices practices best practices OA-GIS 9.2, and practices
VDA 4965
Common Based on OSS/J, Based on ISO Based on HL7, Based on OMG Based on
components MTOSI, and best 20022, SEPA, ASC X12, and PLM Services 2.0, ACORD and IRI
practices and NACHA best practices OA-GIS 9.2, and (NAVA)
VDA 4965
Business Based on SID Based on ISO Based on HL7, Based on OMG Based on
vocabulary model and best 20022, IFW, and ASC X12, and PLM Services 2.0, ACORD, IRI
practices best practices best practices OA-GIS 9.2, and (NAVA), IAA, and
VDA 4965 eEG7
Business Based on SID Based on ISO Based on HL7, Based on OMG Based on
object models model and best 20022 and best RIM, and best PLM Services 2.0, ACORD, eEG7,
practices practices practices OA-GIS 9.2, and and best
VDA 4965 practices
Solution Order Feasibility, Mortgage Benefits Engineering Claims Status

scenarios Incidence, and Refinancing, Eligibility, Change Request,
Problem Corporate Real-Time Product Data
Management Payments Claims Exchange
Adjudication

Another useful way to look at the asset types is to consider the organizational roles that
typically use each type of asset. Then, you can more easily envision how the work in each
part of your organization can benefit. Figure 7-2 lists the asset types collated by the roles that
will most commonly use those assets. You can see what tasks are involved in the solution
development and begin to see how the supplied assets accelerate solution delivery.
WebSphere ICPs do not provide packaged solutions but accelerate the building of BPM
enabled by SOA solutions. The green boxes in Figure 7-2 denote ICP core assets and the
orange boxes identify assets that are provided as samples in the ICP solution scenarios. The
orange boxes represent some of the additional work that is required to extend the scenario,
which you do using the core assets so that it is an end-to-end deployable solution. The blue
boxes denote what you or your partners implement when completing the solutions, for
example, the environment-specific implementation of service interfaces that are defined as
core assets in the ICP.
WebSphere BPM based industry-specific solution assets provided

with WebSphere Industry Content Packs
Model Capability Applica tion, Service

Business
Str ategy Maps Maps Service, Policies Models
Proce ss Common Manage

Manage
Business Maps Solutio n Components Se rvic e Lifecyc
Service le
Lifec ycle
Leader Architect
Implement
Forms /UI Services
Manage Interfac es
Proc ess Proc ess
Models Lifecycle Implement
Process Develo per Das hboards Mediations/
Transformations
Owner
Busines s Pr ocess Business De fine Logical

Voc abulary Models Obje ct Model Data Model
Manage Implement
Business Data Physic al Data
Business KPIs
Analyst Architect Model
C onte nt P ac k As set C onte nt Pac k Sa mple C us tome r Im ple me ntation Ta sk
Figure 7-2 WebSphere ICP assets and associated roles
Let us take a closer look at the assets provided in the WebSphere ICPs.
Capability models consist of capability maps and process maps. Capability maps describe
what an organization does whereas process maps define the high-level flow of the business
processes that support what the organization does. Together, they help link your
organizational structure to the processes that the organization supports. Capability maps link
to associated process maps, facilitating clear visibility to the processes that support the
capabilities. You can use WebSphere Business Compass, IBM BPM BlueWorks, or both to
work with capability models.
Figure 7-3 shows an Insurance Claims capability model in WebSphere Business Compass.

Figure 7-3 Example of a capability map
Figure 7-4 shows an Order Handling process map from the WebSphere Telecom ICP,
visualized in WebSphere Business Compass.
Figure 7-4 Telecom Order Handling process map
Supporting process maps can be linked directly to the supported capabilities, as shown in the
Healthcare Claims Operations capability map shown in Figure 7-5.
H ealt hca re Capab ility M odel > Claim s O per atio... 100 % Detai ls
De scri ption
T he ma nagement of the sub missio n,

cor rection , adjud icat ion, and
ad ministrat ion of claims.
Attrib utes
Owner s: <none>
Claim s F ra ud ul ent a nd
M an ag em en t Fr ivo lou s Cl aim s
S up po rtin g Proce sses
C laims Pr oce ssing

File Claim
Man age Fr audulent Claim s
Suppor ting process maps B enefit Eligibility
A djudicat e Claim
R eal-t ime claims adj udication
I nquir e Claim s
L ink s
Atta chmen ts
Figure 7-5 Healthcare claims operations linking to supporting process maps

Process models define process flows, along with roles and business items that are relevant to
those process flows, for use in WebSphere Business Modeler. ICP process models also
define standard business measures that are used to track and continuously improve business
operations. These process measures are culled from the American Productivity and Quality
Center (APQC) Process Classification Framework. Both analysis and implementation models
are provided, and implementation models are optimized for deployment to WebSphere
Process Server. An example process map in WebSphere Business Modeler from the
WebSphere Telecom Industry Content Pack is shown in Figure 7-6.
Figure 7-6 Telecom ICP process map
Service models consist of service interfaces and schemas that help you create and assemble
processes. The provided service definitions include service inputs, outputs, and operations.
Use WebSphere Integration Developer to work with service models. An example service
interface definition from the WebSphere Banking ICP is shown in Figure 7-7.
Figure 7-7 A service interface definition from the Banking ICP
Common components are implementations of common services and utilities that can enable
application integration and can be easily reused across solutions. You work with common
components (such as the NACHA validation service from the WebSphere Banking ICP) in
WebSphere Integration Developer.
Business vocabularies provide a set of common business concepts, terms, and relationships
that are specific to an industry. Common terminology and concepts drive consistent
definitions and usage across business services, business strategies, and process flows, and

make handoffs between the business analysts and IT more efficient. With business concepts,
business users can define policies and enable IT to handle the process variations using
technical policies during application run time. You use WebSphere Business Services Fabric
to work with business vocabularies. Figure 7-8 shows an example business vocabulary from
the WebSphere Banking ICP visualized in WebSphere Business Service Fabric.
Figure 7-8 The Business Vocabulary for the Banking industry
A policy from the WebSphere Telecom ICP Incident and Problem Management solution
scenario is shown in Figure 7-9 on page 161.

Figure 7-9 Trouble Ticket Type policy
Business object models implement conceptual data models and provide a starting point for
logical and physical data models. You use Rational Software Architect to work with business
object models. An example business object definition in WebSphere Integration Developer is
shown in Figure 7-10 on page 162.

Figure 7-10 Banking Balance business object
Solution scenarios are deployable starter solutions that use WebSphere ICP assets, such as
the solution scenario for Banking Mortgage Refinancing. In addition to WebSphere ICP
assets, content is provided to complete the solution, including mock service implementations,
pre-built business spaces, and WebSphere Business Monitor models. You can use the
solution scenarios to easily demonstrate a starter solution that is built with ICP assets and
extend them to create finished solutions.
Later in this chapter, you will see more examples of these assets in the context of the different
WebSphere ICP offerings.
7.3 Using WebSphere ICP assets in business-driven BPM

solution development
Figure 7-11 on page 163 illustrates the activities that are involved in BPM project
implementation and how WebSphere ICP assets can be used in each phase.

Realizing Continuous Process Improvements
Through Business Driven Activities
Discover Busi ness Process

Anal yst Own er St ory board
Capability models
Proc ess models Process mode ls
Business Bu si ness Business Solution sc enarios
vocabular y models L eader Analyst
Asset navigator
Collaborate, Iterate,
Refine & Validate
Busi ness
Busin ess Anal yst
Users
Busi ness
Users
Manage Busi ness Experience/visualize
Leader
Process
Solution Scenarios Owner Process mode ls
Dashboards Solution sc enarios
Figure 7-11 Applying WebSphere Industry Content Pack assets to business-driven BPM development
Figure 7-11 shows the following business-driven activities:

Discover your business intent by mapping intent to business capabilities and processes,
and identifying and prioritizing options.
Storyboard user interactions by capturing and defining as-is process and to-be processes,
specifying business measures and Key Performance Indicators (KPIs), and creating
mock-up forms to validate and visualize human interactions.
Experience and visualize the solution by elaborating and assessing business measures
and KPIs, adding operational characteristics to future state processes, and interactively
validating elaborated processes.
Manage real-time performance by empowering business users to customize their
experience and manage KPIs and alerts based on changing business conditions.
You can also use WebSphere ICP assets when IT works with business users on parallel
activities during the implementation cycle. These IT-oriented activities and the assets that can
be used are shown in Figure 7-12 on page 164.

Business and IT collaboration a winning partnership
IT IT IT
A rc h ite ct De ve lo p er A dm i n
Pr oc e ss
O wn e r
Bu si ne ss IT Da ta
An aly st L ea de r Ar c hi te ct UI
D ev elo p er
Bu si ne s s
U se r s
In te gr a to r
In parallel with LOB WPS So lu tio n

Ad m in De ve lo p er
activities
Develop services and Optimize solution Manage production

integration iteration and deployment solutions
Identify, bui ld, and extend Surface reusable building Monitor systems
business ser vices blocks to the business health to ensure
Enable effi cient solution pr ocess integrity
Enable busi ness networ k via
inter nal and external iteration and business-IT Partner on insight
application integration handoffs via sandbox capturing for
experience environment continuous
Service Models Partner with business to pr ocess
Business Object Mode ls improvement
Common Components deploy production solution
Figure 7-12 Parallel IT activities and asset types for acceleration
Next, let us look at each of the WebSphere ICPs.
7.4 WebSphere Telecom ICP

The WebSphere Telecom ICP provides a set of Telecom-focused assets for fulfillment,
assurance, billing, customer interaction, inventory, catalog, and media life-cycle processing
lines of business. It also provides ready to use Order Feasibility and Incidence and Problem
Management solution scenarios that serve as quick demonstrations and starting points for
solution delivery.
Currently, Communications Service Providers (CSPs) are faced with the challenge of
minimizing the order activation time: the time from service creation until billing can begin.
They also need to facilitate communication and workflows between internal organizations,
suppliers, and customers, improve customer satisfaction with improved order management,
and use open standards to gain efficiencies, ease integration, and drive value from existing
investments.
Consistent with every content pack, the assets span the entire BPM solution development
cycle. They are based on a number of Telecom standards and best practices, as summarized
in Figure 7-13 on page 165. The Telemanagement Forum (TM Forum) defines a number of
standards within the TM Forums Solution Frameworks NGOSS that the WebSphere Telecom
ICP uses. These standards include the Business Process Framework (eTOM), Information
Framework (SID), and Application Framework (TAM). Figure 7-13 on page 165 maps the
associated standards to the assets provided in the WebSphere Telecom ICP.

Sum mary of key standards leveraged
The TM Forum Solution Frameworks are the industry standard
suite of frameworks and best practices for the enhancement of
the inform ation, communications and entertainment industri es
business operations, suppor t processes and systems.
American Pr oductivi ty and
Quali ty Center Process
Soluti on Frameworks (NGOSS) Com mon compo nents Classification Framework (PCF)
OPERATI NG PROCESSES
S ervi ce Models, Business
Capabil ity m odel s, 1 .0 2 .0 3 .0 4.0
process m odels Obj ect m odels, Business D e ve l o p D e ve l o p Ma rk e t De l i ve r 5 .0
M a na g e
vocabul ary Vi s o
i n a n d M an a g e an d S el l Pro d u c ts
Cu s to me r
an d P ro d u cts a n d Pro d u cts a n d and
Stra te g y Se rv i ce s Se r vi c e s S e rvi c e s S e rvi c e
Bu sin ess
In fo rma ti on
Process Proce ss Information
Fra me wo rk
Focus Fra mew ork (SID) F ocus MANAGEM ENT AND SUPPORT PROCESSES
(e TOM)
6. 0 De velo p an d Ma na g e H um an Ca pit al
7.0 M a na ge In fo rm at ion T ec hn olo gy
8. 0 Ma na g e F in an cial Res ou rc es
A pp lic atio n 9 .0 Acq uir e, Co ns tru ct , a nd M an ag e Pro pe rt y

Inte gra ti on
Fra mew ork 1 0. 0 Ma na ge En vir on me nt al H ea lth an d Saf ety (EH S)
Fra me wo rk
(TAM)
1 1. 0 M an ag e Exter n al R ela tio nsh ips
S ervi ce Models 12 .0 M an ag e Kno wle dg e, Im pr ov em en t, an d Cha ng e
Source: TMF orum So urce: APQC Key

SOA/Application P erform ance
Focus I ndi cators
Figure 7-13 Telecom standards that the WebSphere Telecom ICP uses
As an asset example, let us look at a supplied business object model. Figure 7-14 on
page 166 shows several of the WebSphere Telecom ICP asset libraries and modules loaded
into WebSphere Integration Developer, several of the predefined data types for Fulfillment,
and the details for the Product Order business object. As with any WebSphere ICP, there is a
breadth of standards-based assets to use in your solution delivery.

Figure 7-14 Product Order business object
The WebSphere Telecom ICP is a key offering for the associated IBM Telecom Industry
Framework (Service Provider Delivery Environment).
7.5 WebSphere Banking ICP

The WebSphere Banking ICP accelerates building banking-focused BPM solutions, for both
retail and corporate banking. People in the Banking industry know that banks are creating
opportunities for change in a number of areas. The WebSphere Banking ICP provides a set of
Banking-oriented assets for use primarily in these focus areas:
Core banking - Optimizing channels, targeting customer acquisition, and dynamically
bundling products
Payments and securities - Driving straight-through processing across payment networks,
integrating with treasury operations, and improving the payments supply chain
Integrated risk - Automating regulatory compliance processes, integrating disparate fraud
applications, and proactively monitoring business activities are improving operational risk
management
Customer care - Using customer insights to optimize processes, increasing focus on
cross-selling and up-selling, and streamlining how customer complaints are processed
WebSphere Banking ICP also provides Mortgage Refinancing and Corporate Payments
solution scenarios that serve as quick demonstrations and starting points for solution delivery.
Consistent with every content pack, the assets span the entire BPM solution development
cycle. They are based on a number of Banking standards and IBM best practices, as

summarized in Figure 7-15, which maps the associated standards to the assets that are
provided in the WebSphere Banking ICP.
Summary of key standards leveraged Key

P erform ance
I ndi cators
O PERATING PROCESSES
1 .0 2.0 3.0 4 .0 5 .0
Com mon De ve ol p
Vi si o n
Dev el o p
a nd Man a ge
M ark et
an d Sel l
De il ve r
Prod uc ts Ma n ag e
Cu stom er
Com ponents an d Pro d uc ts an d Pro du cts a nd a nd Se rvi ce
Stra teg y Se rvi ce s Se rvi ce s Se rv i ce s
NACHA is a no t-for-p rofit association , led by member dep osi tory fi nancial institution s and payments
associ ati ons, that is responsib le for the administrati on, development, and governance of the ACH M ANAGEMENT AND SUPPORT PROCESSES
Network. NACHA promul gate s and enforces the NACHA Operati ng Ru les, develope s new AC H
6 .0 De v e l op a n d M a n ag e H u ma n C a pi ta l
payme nt appli cation s, and establi she s sound risk management practices for the ACH Network.
7 .0 M an a g e In for m ati o n Te ch n o l o g y
8 .0 M a n a ge Fi n a n c a
i l Re s o u rc es
Comm on
9 .0 Ac q ui re , C o ns tru c t, an d M a n a g e P ro p e rty
Com ponents
Pro vid es the fin an cia l in du stry
1 0 .0 M a n a g e En vi ro n m e n ta l H e a tl h a n d Sa fe ty (E HS)
w ith a co mmon p la tfo rm fo r th e
20022
d eve lop men t o f me ssag es i n a Th e EPC d eve lo ps the p ayme nt

1 1 .0 M a n a g e Exte rn a l Re l a ti o n sh i p s
stan da rdi zed X ML synta x, u sing : 1 2 .0 M a na g e Kn o w e

l d g e , Im p ro ve m e n t, an d C h an g e
sc he mes an d frame wo rks ne cessa ry to
re al ize the Single Euro Pay me nts Ar ea
A mod el in g metho do lo gy
IFW
(S EPA). SEPA is an EU in te g ratio n The Info rmatio n Frame Work
(ba sed o n U ML) to cap tu re
i ni ti ative in the a rea of p ayme nts (IFW) Bu sin ess Obj ect
in a syntax -ind ep en de nt d esi gn ed to a chi eve the comp le ti on o f Mo de l (BOM) is use d a s a s our ce fro m
wa y fi na nci al b usin e ss
th e EU in tern al ma rket an d mon etary w hic h th e vo cab ul ary terms for the IBM
are as, bu sin ess
u ni on . We bSp he re Ba nki ng C on tent Pac k a re
tran sactio ns an d a ssoci ated
d eri ved . Ad ditio na ll y, the IFW mod el h as
mes sag e fl ow s Th e Sin gl e Eu ro Payme nts Are a or
SE PA wi ll b e th e a re a w he re citize ns, w ell -de fine d se rvice inte rfa ces an d d ata
type s as pa rt o f the In te rfa ce D esi gn Mo de l
A set of X ML de sig n ru les to co mp ani es an d o th er e co no mic
con vert the me ssag es p artic ipa nts mak e an d rece ive p aym ents (IDM). A lo gi cal su bse t o f se rvice
de scrib ed i n U ML in to X ML i n eu ro, wh ethe r b etw een or wi th in in terfac es an d de fini ti on s h ave be en
sch ema s n atio na l bo un da rie s, un de r th e same ch ose n to de fi ne Ind ustry se rvice
b asi c con diti on s, rig hts an d in terfac es. Th ese inte rfa ces an d da ta types
Busi ness Vocabulari es,
o bl ig atio ns. In the l on g-term , the u nifo rm a re lo gi cal ly gro up ed i nto SC A lib rari es
Busi ness Ob ject Models,
Com mo n Service tha t a re use d to imp le men t the S CA
SE PA pa ymen t i nstrume nts are exp ected
to re pl ace n atio na l eu ro pa ymen t mo du le s. Business Vo cabul ary
sy ste ms no w be in g op era te d in E uro pe. Business Object Mo dels,
Servi ce M odels
Figure 7-15 Standards that the WebSphere Banking ICP uses
As we continue our tour through the different types of available assets, let us look at an
example of a process model and predefined KPIs. Figure 7-16 on page 168 and Figure 7-17
on page 168 show a process model for the payments process and KPIs specific to loan
processing. The predefined business measures give you a head start on defining how the
business tracks the business processes and which to use for continuous process
improvement. As with any WebSphere ICP, there is a breadth of standards-based assets to
use in your solution delivery.

Figure 7-16 Banking Process Payments process model
Figure 7-17 show KPIs specific to loan processing.
Figure 7-17 Banking Loan process business measures
The WebSphere Banking ICP is a key offering for the associated IBM Industry Framework
(Core Banking, Payments, and Customer Care) for deploying BPM and SOA Banking
solutions.
7.6 WebSphere Healthcare ICP

The WebSphere Healthcare ICP accelerates building healthcare-focused BPM solutions.
The problems faced currently in the healthcare and life sciences ecosystem are significant.
The economic downturn has created problems that reverberate significantly in the healthcare
industry, particularly among health plans. As with most other enterprises, health plans
encounter limits on rate increases and cost pressures, which are beginning to translate into
plans with higher deductible amounts, resulting in a subtle shift from broad-scope insurance
to something more like catastrophic coverage. An alternative, or at least a complement to
insurance, is wellness management, in which the health plan member becomes a partner
with the plan for health maintenance. This approach requires an even greater need for health
analytics than currently is the case, to assess and authorize the health services provided
under traditional coverage.

Given this business environment, health plans are faced with various challenges and are
responding with change in the following areas of the health plan or payer business:
Membership enrollment - Avoiding declining membership and improving member
recruitment and retention rates with self-service portals and customized and
consumer-directed plans
Employer and other group insurance customer relations - Providing new services and
product offerings and Web-based facilities for patient maintenance of personal health
records
Claims processing - Improving claims management efficiency and dealing with the
mandated migration of care and billing coding schemes to achieve full International
Classification of Diseases Version 10 (ICD-10) and the companion Health Insurance
Portability Act (HIPAA) Transaction Rule/Regulation 5010 modification
Collaboration with healthcare providers - Exchanging and using electronic medical
records, in addition to the industrys long-standing use of electronic data interchange
networks
The WebSphere Healthcare ICP provides a set of assets for use in the enrollment, case
management, employer and group management, claims management, and provider
collaboration industry segments. In addition, two solution scenarios are provided that you can
deploy immediately for quick demonstrations and use as starting points for solution
development: Benefits Eligibility and Real-Time Claims Adjudication. Benefits Eligibility
illustrates whether a payer or health maintenance organization (HMO) has a subscriber or
dependent on file, the status of the subscriber or dependent, and the current health care
eligibility, and the benefit information for the subscriber or dependent. Real-Time Claims
Adjudication illustrates the adjudication of a healthcare claim upon receipt by the payer from a
provider. Unlike the current method of submitting and processing claims in batches over a
period of weeks to months, Real-Time Claims Adjudication ensures that the complete
process from billing to patient payment occurs during the patients visit to the healthcare
providers office or facility.
The assets are based on ASC X12 EDI, HL7 industry standards, and best practices, as
summarized in Figure 7-18 on page 170.

Summary of Key Standards Leveraged
Busi ness Vocabulari es,
Busi ness Object Models,
Com m on Compo nents
The Accredited Standards Committee (ASC) X12, chartered by the American National
Standards Institute in 1979, develops electronic data interchange (EDI) standards and
related documents for national and global markets. With more than 315 X12 EDI
standards and a growing collection of X12 XML schemas, ASC X12 enhances business
processes, reduces costs and expands organizational reach.
Health Level Seven International (HL7) is the global authority on standards

for interoperability of health information technology with members in over
55 countries. HL7's vision is to create the best and most widely used Busi ness
standards in healthcare. V ocabulari es,
Busi ness Ob ject
M odels,
HL7 provides standards for interoperability that improve care delivery, S ervice Mod el s
optimize workflow, reduce ambiguity and enhance knowledge transfer
among all of our stakeholders, including healthcare providers, government
agencies, the vendor community, fellow SDOs and patients. In all of our
processes we exhibit timeliness, scientific rigor and technical expertise
without compromising transparency, accountability, practicality, or our
willingness to put the needs of our stakeholders first.
Figure 7-18 Healthcare Industry standards that the WebSphere Healthcare ICP uses
Let us look at an example of a healthcare business vocabulary that is supplied with the
content pack, as illustrated using WebSphere Business Service Fabric in Figure 7-19 on
page 171. The vocabulary is based on the HL7 Data Dictionary, ASC X12 EDI for HIPAA, and
best practices, and it includes standard terms in the calendar cycle, probability distribution
type, country, state, claim information, premium, claims status, account employee, and
transmission.

Figure 7-19 Healthcare vocabulary
7.7 WebSphere Product Lifecycle Management ICP

The WebSphere Product Lifecycle Management (PLM) ICP accelerates building
manufacturing product life-cycle-focused BPM solutions for the Automotive, Aerospace, and
Electronics industries.
Software and integrated product failures continue to plague automotive, aerospace, and
electronics manufacturers, driving them to create the following opportunities for change and
improved efficiency:
Product data - Improving data timeliness and accuracy, integrating product data
management systems, using industry standards, and driving effective collaboration
Engineering change - Streamlining change processes, improving stakeholder
collaboration and communication, and improving decision making
Bill of Material - Automating Release to Manufacturing, synchronizing PDM-ERP Data,
and using industry standards
Supplier collaboration - Implementing centralized data exchange, standardizing interfaces,
and automating business flows

The WebSphere Product Lifecycle Management ICP provides a set of assets for use in
Automotive, Aerospace, and Electronics product data management, engineering change
management, bill-of-material management, and supplier collaboration segments. In addition,
two solution scenarios are provided that you can deploy immediately for quick demonstrations
and use as starting points for solution development: Engineering Change Request and
Product Data Exchange.
The Engineering Change Request solution scenario is based on the Verband der
Automobilindustrie (VDA) 4965 specification for Engineering Change Management. The
specific focus of this solution scenario is the Engineering Change Request (ECR) Interaction
Scenario 4 (IS4), called Participant Detailing and Comments, which describes a joint
engineering change process where the coordinator and the participant work closely together
throughout all the process phases. The Product Data Exchange solution scenario uses the
Product Data Exchange (PDX) to update design information for specific components within a
product.
WebSphere Product Lifecycle Management ICP assets are based on OMG PLM Services
2.0, VDA 4965, OAGIS 9.2, and best practices, as summarized in Figure 7-20, which shows
the map of the supplied assets types to the standards that are used in their implementation.
Summary of Key Standards Leveraged
American Productivity and

Quality Center Process I nq uir y Cr ea tio n
Te ch nic al
Ana lysis C om me nt ing Ap p ro val
of ECR o f EC R on ECR o f EC R
Classification Fram ework (PCF) of ECR
M3: M3.4: M4 :
OPERATING PROCESSES Pote ntial M3.1: M 3.2: M3. 3: ECR ECR
Solution ECR ECR ECR
Initiated Cr eated Detailed Comm ented Appro ved
1 .0 2 .0 3 .0 4 .0
5.0
Def n
i ed
De ve l o p D e ve l o p M a rk e t De l vi e r
M an a g e
Vi s o
i n a n d Ma n a g e a n d Se l l Pro d u c ts
and P ro d u cts a n d Pro d u cts a n d and Cu s tom e r
S er vi c e
Stra te g y Se rv i ce s Se r vi c es S er vi c e s
Source: Verband der Automobilindustrie (VDA) 4965 specification
Service Mo del s,
Busi ness Object
MANAGEMENT AND SUPPORT PROCESSES
model s, Com mon
6. 0 De velo p an d Ma na ge H um an Ca pit al Com ponents,
Busi ness vocabul ary,
7.0 M a na ge In fo rm at ion T ec hn olo gy
Sol uti on scenarios
8. 0 Ma na g e F in an cial Res ou rc es
9 .0 Acq uir e, Co ns tru ct, an d M an ag e Pro pe rty

Object Management Group (OMG): Product
1 0.0 M a na ge En viro nm e nt al H ea lth an d Saf ety (EH S)
Lifecycle Management Services
1 1. 0 M an ag e Exter n al R ela tion sh ips
This specificati on defines a Platfor m
12 .0 M an ag e Kno wled g e, Im pr ov em en t, an d Cha ng e Independent Model (PIM) for Product Lifecycle
Management Services
S ervi ce Model s, Business
Sou rce: APQC Capabil ity Model s, Obj ect model s, Comm on
P rocess M odels, com ponents, Busin ess
Key Performance
Open Applications Group I ntegration vocabul ary
I ndicators Specification (OAGIS)
Figure 7-20 Standards that the WebSphere Product Lifecycle Management ICP uses
Consistent with all WebSphere ICPs, service models are provided to help you build
integration solutions. Service models define standard service interfaces and data structures
that improve cross-component and system interactions. In the WebSphere Product Lifecycle
Management ICP, service models are based on the OMG PLM Services 2.0, VDA 4965,
OAGIS 9.2 standards, and best practices. The sample service interfaces that are provided in
this ICP are Query BOM, Sync Item Master, Response BOM, Query Product Component
Structure, and Delete Parts. Figure 7-21 on page 173 shows several of the service model
projects in WebSphere Integration Developer and the receiveProductData service interface.

Figure 7-21 WebSphere Integration Developer showing service model projects and the receiveProductData service
interface
The WebSphere Product Lifecycle Management ICP is a key offering of IBM PLM Framework
(Product Data Management, Engineering Change Request) for deploying BPM and SOA PLM
solutions.
7.8 WebSphere Insurance ICP

The WebSphere Insurance ICP accelerates building insurance-focused BPM solutions, for
personal and commercial lines, life, and annuities. The assets and solution scenarios
accelerate solution delivery for the following key areas of challenges and opportunities facing
insurers:
Distribution - Optimizing distribution channels, seeking faster time to market for new
products and offerings, and gaining greater insight into product configurations to help
meet customer needs
Policy - Optimizing underwriting, rate, quote, and issue processes, improving customer
and producer loyalty by enabling seamless policy inquiries and changes, implementing
loss-prevention services, and automating and improving the efficiency of renewals
Claims - Accelerating claims processing and end-to-end visibility as a key to satisfactory
customer experience, automating the claims process, improving customer satisfaction and
loyalty by providing transparency to the claim process, improving settlement time, and
optimizing the use of all types of service providers
Customer care - Improving customer loyalty and retention, identifying and using cross-sell
and up-sell opportunities, providing multi-channel customer experience options, and
improving complaint processing

The Claims Optimization and Status for Property and Casualty solution scenario is
immediately deployable for quick demonstrations and use as a starting point for solution
development.
WebSphere Insurance ICP assets are based on ACORD, IAA, IRI, eEG7 standards, and best
practices, as summarized in Figure 7-22, which maps the supplied asset types to the
standards used in their implementation.
Summary of key standards leveraged

The A CORD Fr am ework is the ne xt ev olution of sta nda rds Capab ili ty
de ve lopme nt a nd a ne w e ra in what AC ORD de liv er s to the Mod el s,
Business
insura nce industry . The industr y is be c om ing more Vo cabul aries,
dive rs e and the ma rke tpla ce more globa l. The A COR D Comm on
Fr am ework r epre se nt s a single s tre am lined bus ine ss Comp onents,
Bu s in es s m ode l for s tandar ds cr ea tion tha t is fle xible e nough to Business Obj ect
Di ct io n ar y Mod el s
c ros s lines of business and ge ogr aphic bor ders .
Pr oc es s
M aps
C a pa bility
M ode l Se rvic e
Maps
Inform a tion
M ode l Bu si ness
Com pone nt
M ode l Vocabul ari es,
Bu si ness
Object Mod el s,
Da ta Service M odels
M ode l Under its ne w vis ion, IRI will be t he a uthor ita tive
sourc e of k nowledge per taining to a nnuitie s,
ins ur ed re tir em ent produc ts a nd re tir em ent
pla nning.
IB M Ins ur anc e Applic ation

Arc hite ct ur e (IAA )The Insur ance Busi ness
Busi ness
Vocabulari es,
Applic ation Ar chitec ture (IA A) is V ocabulari es,
a c om pr ehe ns iv e se t of insura nce S ervice Model s
Busi ness
Object Models spec ific m ode ls that re pre sents
be st pra ctice s in insura nce a nd is
a natura l e xte nsion to t he
Component Bus ine ss Model.
Figure 7-22 Summary of standards that the WebSphere ICP uses
To complete the tour of several of the specific types of assets provided with the WebSphere
ICPs, let us look at the common components provided by the WebSphere Insurance ICP.
These components are common services and utilities that enable interoperability within the
application ecosystem. For the Insurance industry, they are based on ACORD and HR-XML
industry standards and best practices and include implementations for sign-on, file extraction,
bulking, de-bulking, not in good order, validation, rules, and error identification. Figure 7-23 on
page 175 shows the WebSphere Insurance ICP common component Service Component
Architecture (SCA) libraries that were imported into WebSphere Integration Developer.

Figure 7-23 Selected WebSphere Integration Developer common component projects
The WebSphere Insurance ICP is a key offering of IBM Insurance Framework (Claims Status)
for deploying BPM and SOA Insurance solutions.
7.9 WebSphere ICP asset navigator

Using the asset navigator, you can explore and locate the assets that you can use to
jump-start your solution development.
The welcome panel of the asset navigator (Figure 7-24 on page 176) shows what you see
when launching the asset navigator, in this case, the WebSphere Telecom ICP asset
navigator. From here, you can access the asset navigator capabilities.

Figure 7-24 Main panel of the asset navigator
One of the main things that you can do with the asset navigator is to search for assets based
on various criteria that you specify, such as name and business area. Figure 7-25 illustrates
using the asset navigator to find assets in the WebSphere Insurance ICP. In the resulting
asset list, you see the type of asset and applicable lines of business and business areas.
These search capabilities help you to quickly identify a set of assets, used at different phases
of a BPM project, in one view.
Figure 7-25 Searching for assets in the WebSphere Insurance ICP
Figure 7-26 on page 177 also illustrates using the asset navigator to find assets in the
WebSphere Insurance ICP.

Figure 7-26 Searching for Life Quote Management assets using the keyword Apply
By clicking the asset, you can see its details. In the example shown in Figure 7-27, you can
see the standard on which the asset is based and the WebSphere Dynamic Process Edition
tool that is used to work with this asset.
Figure 7-27 Information about the Order Handling process map in the WebSphere Telecom ICP

You can access associated assets, as shown in Figure 7-28, to find groups of related assets.
When you have identified the assets that you need, you can import the artifacts into the
WebSphere Dynamic Process Edition tool and begin using and extending them.
Figure 7-28 Traversing to subprocesses from the Order Handling process map
Using the asset navigator, and the BPM tools to look at the actual assets, helps you locate
specific assets that you can use to jump-start your solution development.
7.10 Summary
The WebSphere Industry Content Packs (ICPs) provide a wealth of pre-built assets to
accelerate development of BPM solutions that you can use to address the challenges facing
your business today. Standards-based assets improve time-to-value for BPM solutions,
ensure consistency across the application ecosystem, facilitate reuse of solution assets, and
reduce project risks. You can extend the supplied content to suit unique business needs and
use existing assets to facilitate integration across your application ecosystem.

Related publications
The publications listed in this section are considered particularly suitable for a more detailed
discussion of the topics covered in this paper.
IBM Redbooks publications

For information about ordering these publications, see How to get IBM Redbooks
publications on page 180. Note that some of the documents referenced here may be
available in softcopy only.
Building Solutions with Business Space powered by WebSphere V7, SG24-7861
WebSphere Business Process Management V7 Production Topologies for System z,
SG24-7831
WebSphere Business Process Management V7 Production Topologies, SG24-7854
Leading Practices for WebSphere Dynamic Process Edition V6.2, SG24-7776
WebSphere Business Process Management V6.2 Production Topologies, SG24-7732
IBM Software Supporting ACORD Insurance Standards, SG24-7649
z/OS: WebSphere Business Process Management V6.1.2 Production Topologies,
SG24-7703
WebSphere Business Process Management V6.1.2 Production Topologies, SG24-7665
Getting Started with IBM WebSphere Business Services Fabric V6.1, SG24-7614
Migrating WebSphere InterChange Server and Adapters to WebSphere Process Server
V6.2 and Best Practices, SG24-7415
z/OS: WebSphere Business Process Management V6.2 Production Topologies,
SG24-7733
WebSphere Business Process Management 6.2.0 Performance Tuning, REDP-4551
Business Process Management Enabled by SOA, REDP-4495
Integrating WebSphere Service Registry and Repository with WebSphere Process Server
and WebSphere ESB, REDP-4557
Case Study: Smart SOA Approaches for Green Solutions: Business Process
Management and Resource Optimization, REDP-4490
IBM WebSphere Process Server Best Practices in Error Prevention Strategies and
Solution Recovery, REDP-4466
BPM Solution Implementation Guide, REDP-4543
The Process Architect: The Smart Role in Business Process Management, REDP-4567

Other publications
These publications are also relevant as further information sources:
John Jeston and Johan Nelis, Business Process Management: Practical Guidelines to
Successful Implementations, Butterworth-Heinemann, 2006, ISBN-13: 9780750686563
Online resources
These Web sites are also relevant as further information sources:
IBM BPM - Business Process Management
http://www.ibm.com/software/info/bpm/
IBM BPM Suite
http://www.ibm.com/software/info/bpm/offerings.html
How to get IBM Redbooks publications

You can search for, view, or download IBM Redbooks publications, Redpapers, Web Docs,
draft publications and Additional materials, as well as order hardcopy Redbooks publications,
at this Web site:
ibm.com/redbooks
Help from IBM

IBM Support and downloads
ibm.com/support
IBM Global Services

ibm.com/services

Back cover
IBM Business
Process Management
Reviewers Guide Redpaper
Work smarter through Market demand for business process management (BPM) has grown
significantly in recent years and shows no sign of abating. Based on INTERNATIONAL
business-IT
consultations with our clients, a set of capabilities that IBM makes TECHNICAL
collaboration
available enables you to build robust and holistic BPM solutions, SUPPORT
whether they are integration-centric, human-centric, or ORGANIZATION
Enable content-centric.
business-driven
design and realize In this IBM Redpaper publication, we provide an overview of the IBM
business agility BPM portfolio to BPM market watchers who have a keen interest in
understanding the most current BPM technology releases and how BUILDING TECHNICAL
they can be used together. Specifically, we review the key benefits and INFORMATION BASED ON
Achieve continuous capabilities of the WebSphere Dynamic Process Edition of the IBM PRACTICAL EXPERIENCE
process improvement BPM Suite.
IBM Redbooks are developed
by the IBM International
Technical Support
Organization. Experts from
IBM, Customers and Partners
from around the world create
timely technical information
based on realistic scenarios.
Specific recommendations
are provided to help you
implement IT solutions more
effectively in your
environment.
For more information:

ibm.com/redbooks
REDP-4433-02

Redp 4433

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Redp 4433

Uploaded by

Copyright:

Available Formats

Front cover

Enable business-driven design

Achieve continuous process

IBM Business Process Management Reviewers Guide

Third Edition (April 2010)

Copyright International Business Machines Corporation 2010. All rights reserved.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1. Charting the BPM vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2. BPM interaction with Business Space powered by WebSphere . . . . . . . . 11

Copyright IBM Corp. 2010. All rights reserved. iii

Chapter 3. Enabling BPM with WebSphere Business Compass and WebSphere

Chapter 4. Enabling BPM with WebSphere Integration Developer and WebSphere

iv IBM Business Process Management Reviewers Guide

Chapter 7. Accelerating time-to-value with WebSphere Industry Content Packs . . . 153

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

vi IBM Business Process Management Reviewers Guide

Copyright IBM Corp. 2010. All rights reserved. vii

The following terms are trademarks of other companies:

viii IBM Business Process Management Reviewers Guide

The team who wrote this paper

Copyright IBM Corp. 2010. All rights reserved. ix

Joe Pappas is a Consulting IT Specialist in the Business Performance and Service

Thanks to the authors of the previous edition of this paper:

Now you can become a published author, too!

x IBM Business Process Management Reviewers Guide

Stay connected to IBM Redbooks

April 2010, Third Edition

Copyright IBM Corp. 2010. All rights reserved. xiii

Chapter 1. Charting the BPM vision

Copyright IBM Corp. 2010. All rights reserved. 1

1.2 The characteristics of BPM success

2 IBM Business Process Management Reviewers Guide

Chapter 1. Charting the BPM vision 3

1.2.5 Business and IT alignment

1.2.6 Continuous process improvement

1.3 The IBM BPM Suite

4 IBM Business Process Management Reviewers Guide

1.3.1 WebSphere Business Compass

1.3.2 WebSphere Business Modeler

Chapter 1. Charting the BPM vision 5

1.3.4 WebSphere Process Server

1.3.5 WebSphere Business Monitor

1.3.6 WebSphere Business Services Fabric

1.3.7 WebSphere Industry Content Packs

6 IBM Business Process Management Reviewers Guide

1.3.8 Business Space powered by WebSphere

1.3.9 Additional offering capabilities

1.4 Unifying focus areas across WebSphere Dynamic Process

1.4.1 Linking strategic intent to processes

Chapter 1. Charting the BPM vision 7

1.4.2 Workflow support

1.4.3 Business rules and policy support

1.4.4 BAM enablement

1.4.5 Accelerated time to value

8 IBM Business Process Management Reviewers Guide

1.5 Building on open standards

Object Busi ness Process Modeling Notation (BPMN)

IBM also participates in or co-leads standards initiatives for BPEL4People, WS-HumanTask,

1.6 Supporting global solutions

Chapter 1. Charting the BPM vision 9

As an international company, IBM understands and operates in a global environment. The

Figure 1-2 IBM Development Lab locations for BPM

10 IBM Business Process Management Reviewers Guide