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

Adding application elements to monitor models

Whether you generated a monitor model from an application or created the model from scratch, you can later choose to monitor additional elements.

Before you can add elements based on an application to an existing monitor model, the following prerequisites must be met:

• If you generated the monitor model from an application in Integration Designer, the application is still loaded in the workspace.

• The Monitor Model editor is opened on the monitor model.

• The monitor model is synchronized with the application.

To add new application elements to a monitor model, complete the following steps:

Procedure

1. Click the Monitor Details Model tab of the editor, right-click the monitor model in the model tree, and click New > Create from Application. You must be at the root of the monitor model.

   Remember: You are looking at the last synchronized version of the application. If the model has not been synchronized with the application, you are looking at outdated information, and could, for example, choose to monitor an element that no longer exists in the application.

2. In the Generate Monitor Model window, select the application from which to create the new element.

3. Select the elements that you want to monitor. In the tree showing the application to be monitored, click any node to see the template and event information for that element. The Monitoring Templates tab shows the common monitoring templates that are available for the selected element. Choose one or more templates to create the appropriate monitoring constructs in the generated model. (See Common monitoring templates for IBM BPM Advanced and WebSphere Enterprise Service Bus for more information.) The Emitted Events tab shows all of the events that the selected element can emit. You can either select events individually, or you can right-click in the tree at any level and click Select all events at this level or Select all events at this level and below.

   Events that can carry business information, which is often called the business payload (see Events that can carry business payload), are shown with a flag and package icon

   . Events that can never carry business information are shown with a flag icon

   .

   You cannot remove an event if you have chosen a template that requires that event. The event is shown as selected but unavailable.

   By default, the Include all selected events option is selected. If you select an event that is not currently emitted, you will see a warning in the Problems view after you have generated the monitor model. Using the information in the warning message, you can find the event that is currently turned off and update the application to turn on the event. To remove the synchronization warning from the Problems view, you can then synchronize the monitor model with the application.

   After you have finished selecting events and templates, click Next.

4. Select how the monitored elements will be implemented. In general, accept the default implementations. The tree on this page shows only the elements you have chosen to monitor. Specifically, the tree shows the event sources that you selected events for and the event sources that are ancestors of those event sources. If you did not select any templates or events for the ancestor event sources, the default implementation is None whenever possible. (It is not always possible to specify None because some event sources contain information that is needed by events that are emitted from descendent event sources.) In the second column, select the monitoring implementation that you want for each element. Based on the element, you might have some or all of the following choices:
   • None. The element will not be represented in the generated monitor model. This option is available only if there are no inbound events at the selected or descendant levels that require the selected element to be present. If you click this option, all descendant levels are also set to None.
   • Monitoring context. A monitoring context will be created for the element, complete with keys and a corresponding cube. This option is available only if the selected application element has a lifecycle and an identity that events can use to find it.
   • Event group. An event group will be created for the element. All inbound events at the selected level and all descendant levels will be collected in this new event group (that is, they will all be at the same level in the event group). This option is available only if there are no templates chosen that require a monitoring context at the selected or any descendant levels.

     If you choose this option, all descendants are set to "–" because all of the associated events will be collected into the event group. (See When to choose monitoring contexts versus event groups for more information.)

5. To see a preview of the monitor model that you chose to create, click Next. To make changes and see how they affect your model, click Back to make changes and then click Next.

6. When satisfied with your selections, click Finish. You are asked whether you would like to switch to the Business Monitoring perspective to begin editing the newly created monitor model. To open the new monitor model in the Monitor Model editor, select Yes.

   Important: Confirm that the Build Automatically option on the Project menu is enabled. If it is not, perform a clean build on the monitor model project after it is generated to ensure that the monitor model is validated.

Results

The newly created monitor model element (either a monitoring context or an event group) is added to the monitor model. Any templates that you selected have been applied, resulting in the creation of a set of monitor model constructs. Inbound events have been created for any events that you selected.

What to do next

The Application element field on the monitoring context or event group page shows the display name of the event source that is linked to this monitoring context. To remove the association, you can click Clear.

Important: Removing the association also removes all associations with application elements from all descendant monitor model elements.

Generate monitor models