Moving Forward with the On Demand Real-time Enterprise

196 Moving Forward with the On Demand Real-time Enterprise

The business measures editor is used to open the process models created in

WebSphere Business Modeler and to create business measures models. For

each business measures model, you can define the metrics and KPIs, event

emission points, event filters, event composition rules, and situations that will

trigger specific actions at runtime.

Once the business measures model is complete, work can be performed to

enable it to be recognized by WebSphere Business Monitor. Then the Business

Monitor understands the measurements to be captured from incoming events.

In addition, continuous business process improvement metrics, such as task

working durations and process decision percentages are calculated and can be

exported to update their corresponding business process models in the

WebSphere Business Modeler. This improves simulation and analysis results

because now the actual metrics (versus assumptions) are factored into the

model. These capabilities provide for processes running in WebSphere Process

Server, which is described in more detail in 4.4.7, “WebSphere Process Server

and Integration Developer” on page 208.

Many business process modeling efforts stop at developing flow diagrams or

process maps. With WebSphere Business Modeler Advanced, this effort is

extended to include simulation, analysis, and redesign.

4.4.3 Architecture

The architecture of WebSphere Business Monitor 6.0 comprises a set of internal

components and a group of external components.

The diagram shown in Figure 4-49 represents the overall logical reference

architecture and the components of Monitor V6.

Chapter 4. IBM technologies supporting real-time 197

Figure 4-49 WebSphere Business Monitor architecture

Internal components overview

The following is a list of the internal components:

򐂰 Monitor server—Receives events, handles monitoring-context instances,

and stores and persists runtime and historical metrics and KPI values of those

instances.

򐂰 Dashboards—Display the monitored data. They provide a predefined set of

views that can be customized to support different representations of data and

offer enhanced data analysis.

򐂰 Schema generator—Generates database scripts to be used for creating

databases tables in state, runtime, and historical databases. These

databases contain the business measures models data. The schema

generator also generates the DB2 Cube Views metadata description of the

historical database and generates the metadata mappings for the replication

manager.

򐂰 Databases—Provide the Monitor server with information for event

processing. They also provide the dashboard client with information for

populating views. Information is transferred across the databases through

another monitor component, the replication manager.

198 Moving Forward with the On Demand Real-time Enterprise

򐂰 Adaptive action manager—Provides different types of business responses

resulting from situations expressed within the incoming events.

External components overview

The following is a list of the external components:

򐂰 Business measures editor (BME)—It is used to create the business

measures model that defines what should be monitored, for example,

monitoring contexts, key performance indicators, metrics, and business

situations.

򐂰 Common event infrastructure (CEI)— WebSphere Business Monitor uses

the Common Event Infrastructure (CEI) and the Common Business Event

(CBE) format. This means that the WebSphere Business Monitor leverages

the CBE format for consuming and emitting events.

It participates in event management by receiving events from event sources

and transferring them to the event consumers that have expressed interest in

those events.

򐂰 DB2 Alphablox and DB2 Cube Views—Provide enhanced data analysis for

dashboards.

Figure 4-50 summarizes the overview of the components.