IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Create monitor models
Combining or merging monitor models
You can choose to combine two unrelated models or have them communicate through events. You can also merge an updated or changed model with an earlier version.
- When to use combine versus merge
When you combine or merge two models, you end up with a single monitor model, reducing the work required for separate management and deployment.- Combining monitor models
You might want to build a monitor model that monitors more than one application at a time, by combining two monitor models that were generated from different applications.
- Comparing and merging monitor models
You can compare two monitor models to see their differences and merge them. This capability is most useful when one of the monitor models started as a copy of another, and hence they have some ID similarities. If you export a monitor model from WebSphere Business Modeler, make changes to the model in the Monitor Model editor, and then update the process in WebSphere Business Modeler and export again, you can merge the two models so that your previous updates are not lost.
- Connecting low-level and high-level models
High-level and low-level monitor models communicate through events. The low-level monitor model (possibly generated from Integration Designer) captures system-level inbound events and creates outbound events as the input for the high-level monitor model. The high-level monitor model (possibly imported from WebSphere Business Modeler) receives those events and generates the metrics, stopwatches, and counters for the KPIs.