Monitoring properties or monitoring profile

Customize the events that are produced by a message flow by using monitoring properties or a monitoring profile configurable service. To customize events when you are designing the message flow, use monitoring properties. To customize events after a message flow is deployed, but without redeploying, use a monitoring profile.

Monitoring properties

By using the IBM® Integration Toolkit Message Flow editor, you can configure event sources on most nodes in a message flow. A node that supports the configuration of event sources has a Monitoring tab on its Properties view. Use this tab to add events and to set their properties. When you deploy the message flow in a BAR file, the monitoring properties are included as part of the message flow.
Key facts about monitoring properties:
  • Use monitoring properties when you want to configure events at message flow design time.
  • Monitoring properties apply only to the message flow in question. You can share monitoring properties between message flows by creating reusable subflows.
  • Monitoring properties are deployed in a BAR file as part of the message flow.
  • Use the mqsichangeflowmonitoring command to activate the message flow to emit monitoring events.
  • Use the mqsichangeflowmonitoring command to enable or disable individual event sources in a message flow.
  • To change any other properties of an event, you alter the monitoring properties in the flow, then redeploy the BAR file.
Tip: Use the mqsireportflowmonitoring command to report a list of the names of the event sources for a message flow. You can then use these event source names in a mqsichangeflowmonitoring command to enable or disable individual event sources from the command line.

Monitoring profile

By using operational commands, you can create a monitoring profile configurable service directly on the integration node, and associate it with one or more message flows.

Key facts about monitoring profiles:
  • Use a monitoring profile when you want to configure events for a message flow that is deployed and for which no events are configured.
  • Use a monitoring profile to override the monitoring properties of a message flow that is deployed, as an alternative to redeploying the BAR file. The monitoring profile replaces all monitoring properties.
  • A single monitoring profile can be applied to many message flows if those message flows contain the same event sources.
  • Monitoring profiles are created directly on the integration node by using the mqsicreateconfigurableservice command and the mqsichangeproperties command. Profiles are not deployed in a BAR file.
  • Use the mqsichangeflowmonitoring command to associate the monitoring profile with a message flow.
  • Use the mqsichangeflowmonitoring command to activate the message flow to emit monitoring events.
  • Use the mqsichangeflowmonitoring command to enable or disable individual event sources in a message flow.
Tip: Use the mqsireportflowmonitoring command in the following situations:
  • To report a list of event sources for a message flow. You can then use the names of these event sources in a subsequent mqsichangeflowmonitoring command to enable and disable individual event sources from the command line.
  • To report the monitoring profile for a message flow. You can edit the profile, by adding or changing event sources, then update it by using the mqsichangeproperties command.
  • To create the equivalent monitoring profile for a message flow for which monitoring properties are configured. You can edit the profile, then use it to create a new monitoring profile configurable service by using the mqsicreateconfigurableservice and mqsichangeproperties commands. You can then associate the new profile with the original flow by using the mqsichangeflowmonitoring command. You can use this technique to override the monitoring properties for a message flow, without having to edit the flow and redeploy the BAR file.