IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Create monitor models > Importing monitor models from IBM WebSphere Business Modeler

Update imported models

You can compare a monitor model in the workspace with a monitor model in the file system. Typically, the monitor model in the workspace was imported from WebSphere Business Modeler (and possibly changed in the monitor model editor) and the monitor model in the file system was updated in WebSphere Business Modeler and exported again. You can merge the two monitor models so that your previous updates are not lost.

The models to be compared must be valid monitor models.

If one of the models is not valid, you are given the option of making the comparison using a text editor.

Changes to event groups (which are not part of the model) are not shown in the comparison editor.

To view the changes and update the monitor model in the workspace with the changes from the monitor model in the file system:

Procedure

1. In the Business Integration view of IBM Integration Designer, right-click the module that the monitor model monitors and then select Synchronize with the IBM WebSphere Business Modeler Export. The Synchronize wizard opens.

2. Use the Synchronize wizard to synchronize the module with the project interchange file exported from IBM WebSphere Business Modeler, which is described in the topic Developing iteratively with IBM WebSphere Business Modeler.

3. In the Project Explorer view of the Business Monitoring perspective, right-click the monitor model that you want to update and click Synchronize with File. The Synchronize with File window opens.

4. Click Browse and navigate to the .mm file or the project interchange compressed file that was exported from WebSphere Business Modeler. Select the file and click OK. All monitor models that have a matching monitor model ID are displayed in the Matching monitor models tree.

5. Select the updated monitor model to merge with the current model in the workspace and click OK. The two monitor model files open in a monitor model comparison editor, with the changes highlighted.

   • The Structural Changes pane on the upper left shows the differences between the two monitor models. The changes are described in terms of the actions that must be performed on the model in the workspace (shown on the right side) to make it identical to the model in the file system (shown on the left side). Typically, you will want to update the model in your workspace with any added or changed metrics contained in the file system model, without removing any changes you have made in the workspace since the file was originally imported.

     Suppose that the monitor model in the file system (called FROM_FILE_SYSTEM/ <monitor_model_name>) has an additional metric that is not in the workspace file (called <monitor_model_name>). The change required to merge the models is displayed as add <new_metric> to <destination_monitoring_context>.

     Selecting a difference in the Structural Changes pane affects what is shown in the rest of the editor.

   • The lower panes show the structures of the monitor models.

   • The Merged Result pane on the upper right provides a constantly updated view of the monitor model that will result if the changes are saved at the present moment.

6. In the Structural Changes pane, find each of the changes that you want to apply to your workspace model (such as new metrics, measures, or name changes), and accept them.

   1. Click an individual change listed in the Structural Changes pane. The lower panes display annotations to show how the difference affects the tree structures, for example where an element has been removed or added.

   2. Accept or reject each change from the left contributor (the model in the file system).

      • To accept a change, right-click the change and select Accept Change, or click

        .

      • To reject a change, right-click the change and select Reject Change, or click

        .

      • To accept all changes from the left contributor, right-click the top line in the Structural Changes pane and click Accept All Changes from Left, or click

        .

      When you accept a change, the Merged Result pane is updated to show the resulting monitor model.

7. When you have viewed all changes, save the new merged results file by overwriting the monitor model in the workspace. Right-click in the Merged Result pane and click Save as Right Contributor, or click

   . Be careful not to save as the left contributor, or the changes will not show up in the workspace.

8. Close the monitor model comparison editor.

9. If the merged monitor model contains definitions that are not derived from the application and the discrepancies between the definitions and the application cannot be corrected automatically, the Reset from Application window opens, and you can resolve the discrepancies by completing the following steps:

   1. In the Reset from Application window, click Yes. The Reset from Application window opens.

   2. In the Affected monitor elements column, browse the list of affected monitor elements.

   3. In the Pending changes column, browse the pending changes that are associated with the affected monitor elements. The pending changes include any updates that you have manually made to the monitor model.

   4. If you want to implement all of the pending changes for the affected monitor elements, click OK to reset the monitor model from the application.

Results

You have updated the monitor model in the workspace with the changes from the monitor model in the file system.

What to do next

To incorporate the changes into an associated Integration Designer application, use Synchronize with IBM WebSphere Business Modeler Export, which is described in the topic Developing iteratively with IBM WebSphere Business Modeler.

Importing monitor models from IBM WebSphere Business Modeler