IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Monitoring events
Co-existence of monitor models
In WebSphere Integration Developer 7.0, you cannot use the IBM Business Monitor development toolkit to create version 6.0.2 monitor models. However, you can use existing 6.0.2 monitor models with the IBM Business Monitor development toolkit.
Integration modules (including mediation modules)
In WebSphere Integration Developer 7.0, if you open a version 6.0.2 monitor model in the Monitor Model editor of the IBM Business Monitor development toolkit, the 6.0.2 monitor model will automatically be migrated to the 7.0 format when you save it in the Monitor Model editor. However, the migrated monitor model is still configured to receive 6.0.2-style style events to be emitted at run time. (If that 6.1, 6.2, and 7.0 formats are identical.)
Any WebSphere Integration Developer project that was created in version 6.0.2 and that emits events will continue to use the version 6.0.2 event format in later versions of WebSphere Integration Developer. (The one notable exception to this rule are mediation modules, which require user intervention as described in the "Mediation modules" section below.) As a result, you can edit, save, and deploy your WebSphere Integration Developer project and it will still work with a monitor model that you previously deployed. Similarly, you can edit, save, and deploy your monitor model and it will continue to work with 6.0.2-format events.
The Monitor Model editor allows you to add modules to a monitor model that was originally created in 6.0.2, regardless of whether the module emits events in the 6.0.2 format or the 7.0 format. Alternatively, you can create a new 7.0 module and configure it to use the 6.0.2 event format.
You will still be able to generate event definitions for the business process, inline or stand-alone human task, SCA, and mediation components in the module and add them to an existing monitor model. However, you cannot create a new 6.0.2 monitor model in WebSphere Integration Developer 7.0.
In WebSphere Integration Developer 7.0, you do not require event definitions for 7.0 monitor models. However, if you want to work with event definitions, you will find that existing event definitions are displayed in the Events folder that is nested under the module name in the Business Integration view.
You can double-click these event definitions to open and edit them in the event definition editor. And you can still create new event definitions by right-clicking a module and selecting New > Other > Business Monitoring > Event definition.
When you change a version number for any single resource in a module, every other resource in the module will also be changed. Thus, you can change a 7.0 module to a 6.0.2 module, or change a 6.0.2 module to a 7.0 module, by selecting either 6.0.2 or 7.0 in the Global Event Settings page of the Event Monitor tab, which is found in the Properties view of many of the IBM Integration Designer component editors. The default selection is 7.0.
Mediation modules
For mediation flows in 7.0, you must explicitly choose the 6.0.2 format if you want to emit 6.0.2 style events. In short, the version of events emitted from mediation flow emitters is dependent on the properties selected in the Global Event Settings page of the Event Monitor tab in the assembly editor. (To open this tab, you select the mediation flow in the assembly editor and click the Properties > Details tab, then expand the interfaces in the Details page and select your operation.) If you have selected the 6.0.2 event format, then this event format is read and used at run time. If you have not selected the 6.0.2 event format, then the 7.0 format is used by default for the mediation flow.
Depending on whether you previously selected SCA events for a 6.0.2 mediation module that you now want to import into WebSphere Integration Developer 7.0, the mediation module will exhibit one of the following two behaviors:
- If you previously selected SCA events for the 6.0.2 mediation module in the General page of the Event Monitor tab, then all of the events will be emitted in 6.0.2 format.
- If you did not previously select SCA events for the 6.0.2 mediation module in the General page of the Event Monitor tab, then all of the events will be emitted in the default 7.0 format.
As stated earlier, you can change the event format in the Global Event Settings page of the Event Monitor tab. (If that the Legacy hexBinary selection is not applicable for mediations.)