IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Create monitor models > Generate monitor models > Generate from applications in the workspace

Types of applications for generating monitor models

You can generate monitor models from Process Server applications and WebSphere Enterprise Service Bus applications in your workspace. The Monitor Model editor must be running on Integration Designer.

Before generating a monitor model from an application, make sure that the application is as complete as you can make it. Changes made to the application can be most easily propagated to the monitor model if the application changes are small. Therefore, it is a good idea to complete the design and implementation as much as possible before generating the monitor model.

Process Server applications

After you have created a module in the Business Integration perspective, you can generate monitor models from the following constructs:

• SCA interface operation
• Business Process Execution Language (BPEL)

  • Process, Assign, Compensate, Empty, Flow, ForEach, Invoke, Link, Pick, Receive, RepeatUntil, Reply, Rethrow, Scope, Script (Snippet), Sequence, Staff, Switch, Terminate, Throw, Variable, Wait, While

• Business state machine
  • Business state machine definition, State, Transition, Guard, Action, State entry action, State exit action, Timer

• Business object map
  • Map, Transformation

• Interface map
  • Operation binding, Parameter mediation

• Business rules operation

• Selector operation
• Import

If the application has not yet been deployed, you might want to make all the events available before generating the monitor model. To make events available:

1. In the Business Integration perspective, go to the Business Integration view and open one of the constructs previously listed.

2. Click the Event Monitor tab in the Properties view.

3. In the Global Event Settings, click WebSphere Business Monitor 6.1, 6.2 or 7.0 format (XML with schema support). For the constructs of interest, click All in the Event Monitor to enable all events.

Any BPEL monitor model needs a parent monitoring context. Since monitor models are meant to be monitored at the process level, make sure that you have selected some events (at least the events that indicate the start and finish of the process) from the top-level process.

Restriction: When you plan to generate a model from BPEL and you are choosing a transaction behavior to control rollbacks when an event fails, do not mix Existing and New. Otherwise the order of events is not guaranteed and monitoring errors can result.

WebSphere Enterprise Service Bus applications

You can monitor a mediation flow that emits events.

In a mediation flow, you can create an event emitter primitive node that is capable of emitting an event on the service bus. You specify the content of the event by providing an XPath expression that navigates a Service Message Object (SMO) structure all the way to the element that will be the payload of the event. The following default choices exist for this XPath: ‘/', ‘/headers', ‘/context', ‘/body'

The actual event structure does not exist anywhere in the file system. It can only be dynamically derived.

The ‘/body' element is typed according to the message payload that flows into the event emitter primitive. This message payload is defined in a Web Services Description Language (WSDL) file and is subject to the many variations of WSDL (such as doc/lit wrapped, RPC, and so on).

For information about the base SMO structure for 6.1, see "Overview of information primitives" in the WebSphere Enterprise Service Bus information center.

Generate monitor models from applications located in the workspace