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 > Synchronizing models with applications

Synchronizing in the Monitor Model editor

When you open a monitor model that you generated from Integration Designer, and the corresponding application in Integration Designer has changed in the workspace, you see warnings in the Problems view. To remove the warning, synchronize the models.

If you are synchronizing with an application that was created in WebSphere Integration Developer 6.0.2, 6.1, or 6.2, first export the application monitoring information for the updated application. See Export application monitoring information for more information.

WebSphere Integration Developer is the previous version of IBM Integration Designer, for versions 7.0 and earlier.

To synchronize the monitor model with the Integration Designer application:


Procedure

  1. In the Project Explorer view, right-click the monitor model and select Synchronize with Application. This option is available only for monitor models that were generated from Integration Designer.

  2. If the monitor model is based on an application that was created in WebSphere Integration Developer, you are prompted for the application monitoring information file that is associated with the updated application. Click Browse and locate the compressed file that was exported from WebSphere Integration Developer.

    If the monitor model is monitoring more than one application, you might be prompted for several application monitoring information files.

    You also see this screen if the monitor model was based on an application that is no longer in the workspace. In that case, you must cancel the Synchronize wizard and restore the application to the workspace before you can synchronize the monitor model.

  3. If the changes to the associated application do not affect the monitor model directly, you are given the option to synchronize. Click Yes so that you have the latest synchronized version. Synchronization is complete.

  4. If the changes do affect the monitor model, you see a Synchronization window with a list of changes. The changes are grouped into three categories: elements added, elements removed, and elements changed.

    The first column of the table shows the pending application changes. The second column shows the monitor model elements that are affected by the changes. In some cases, such as when a value is modified in an application that is used as a component in a filter condition, there can be more than one affected monitor element. In these situations, all of the affected elements are displayed in the cell, separated by commas. To see all of the contents, hover over the cell.

    The third column displays the action to be taken to update the monitor model. In some cases, you can choose the action to take.

    For example, when a monitored event source is deleted, you can choose either to delete the monitoring elements or to disconnect the monitoring elements from the application. If you choose to disconnect, the monitor model elements (monitoring contexts, event groups, and inbound events) remain in the monitor model but are no longer associated with the application element (which no longer exists). If you choose to delete, the elements are deleted even if other elements in the monitor model refer to them.

    If you delete elements from the monitor model, other elements that refer to them are not deleted and the resulting monitor model contains errors. To resolve these errors, edit your monitor model to delete any elements that refer to deleted elements, or modify them to refer to different elements.

  5. To find the changes that require you to select an action, click Show Next Change to move through the changes.

  6. To see only the actions for which you have a choice, select the Hide changes that have only one possible resulting action check box.

  7. When you have finished selecting actions, click OK. If the monitor model was based on an application that was created in WebSphere Integration Developer, you might receive repeated prompts to overwrite files in your workspace. These prompts occur because when you import the application monitoring information compressed file, you are creating a new monitor model and also importing the files from the associated application.

  8. If you edited the monitor model and the potential exists for the monitor model to no longer monitor the application correctly, the Reset from Application window opens and you can resolve any discrepancies between the monitor model and the application by completing the following steps:

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

    2. In the Pending changes column, browse the pending changes that are associated with the affected monitor elements.

    3. 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

The monitor model is synchronized with the application that it is based on.

Synchronizing monitor models with applications located in the workspace