Generate monitor models based on application monitoring information from WebSphere Integration Developer

IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Create monitor models > Generate monitor models > Generate from applications outside the workspace > Earlier versions of WebSphere Integration Developer and IBM Integration Designer
Generate monitor models based on application monitoring information from WebSphere Integration Developer

After exporting the required application monitoring information, you can use it to generate a monitor model to monitor an application that was created in WebSphere Integration Developer 6.1 or 6.2.

You must have exported the application monitoring information from WebSphere Integration Developer 6.1 or 6.2.
WebSphere Integration Developer is the previous version of IBM Integration Designer, for versions 7.0 and earlier.

To generate a monitor model:

Procedure

In the Business Monitoring perspective, right-click the Project Explorer view and click Import.
In the Import wizard, select Business Monitoring > Application monitoring information .zip file.
Click Browse and navigate to the file that was exported from WebSphere Integration Developer. Click Next.

Select a location for the new monitor model. You can select a project from the list of existing business monitoring projects or type a name to create a new business monitoring project. After you have selected or created a project, type a name for the new monitor model and click Next.
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.
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.)

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.
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 contains automatically generated elements that correspond to the common monitoring templates and inbound events that you selected. The Application element field shows the display name of the event source in the application that is linked to this monitoring context. If any of the elements in the monitoring context were generated from templates, the templates are shown in the table. Open a template to see the managed elements.
For example, if you open a Start Time template, you see a Start Time metric and inbound events for each event that can create a monitoring context.

What to do next
If the application changes, you can export the application monitoring information from WebSphere Integration Developer again and then use Synchronize with Application to synchronize the monitor model with the application.

Generate monitor models from WebSphere Integration Developer and IBM Integration Designer 7.5

Previous topic: Export application monitoring information

Next topic: Testing monitor models created in earlier versions