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 monitor models with applications located in the workspace

When you make changes to applications in Integration Designer using the Refactor option, you are immediately given an opportunity to synchronize the monitor models in the same workspace that are affected by the changes. For changes that are made to applications without using the Refactor option, your monitor model is not automatically synchronized. In that case, you might see warnings in the Problems view and can choose to synchronize the model with the application.

Whenever possible, use refactoring in Integration Designer to make changes to an application that affects a monitor model in the same workspace. Refactoring changes a value, such as an ID, while preserving the behavior of the element and its relationships to other elements. Otherwise the results are not as reliable.

For example, renaming a component without using refactoring causes the synchronization to detect the change as the removal of one component and the addition of another. Existing monitor model constructs that were linked to the previously named component will be disassociated.

Refactoring of element and attribute names of XML Schema Definition (XSD) types used for event parts is not supported. This is the case whether the refactoring is performed in the IBM Integration Designer Business Object editor, or the Rational Application Developer XSD editor. Updates must be manually performed on any monitor model that is affected by changes made to XSD element or attribute information.

For example, expressions within the monitor model that refer to the updated element or attribute must be changed manually to refer to the new element or attribute.

There are two types of changes in Integration Designer that can affect the monitor model, and synchronization can happen at different times, as shown in the following table.

Types of changes in Integration Designer Available synchronization
Changes that are made using the Refactor option in Integration Designer, such as changes to an event source name (module name, component name, interface name, or operation name), business object namespace, or business object name. If the monitor model is in a saved and consistent state (that is, it can be opened in the form editor) in the same workspace, these changes can be automatically applied, as described in Refactoring in IBM Integration Designer. If the monitor model is not in a consistent state at the time and not all of the changes can be applied, you can add the changes later as described in Synchronizing in the Monitor Model editor. You can apply refactor-based changes even if other changes that are not refactor-based are still outstanding.
Changes that are outside the scope of refactoring, such as changing a Business Process Execution Language (BPEL) activity name within a process, changing a valid from attribute, changing a business object payload type, adding or removing event sources, adding or removing interface operation parameters, or changing an interface operation parameter type. When you open a monitor model with elements that you generated from Integration Designer and the corresponding application in Integration Designer has changed, you might see warnings in the Problems view. You can choose to synchronize the models, as described in Synchronizing in the Monitor Model editor.

Generate monitor models from applications located in the workspace