If you want to customize events when you are designing the message
flow, use monitoring properties. If you want to customize events after
a message flow has been deployed, but without redeploying, use a monitoring
profile. This topic gives information about both methods.
Using monitoring properties to configure events
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 broker archive
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 only by
creating reusable subflows.
- Monitoring properties are deployed in a BAR file as part of the
message flow.
- You use the mqsichangeflowmonitoring command
to activate the message flow to emit monitoring events.
- You can 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.
To configure monitoring events using monitoring properties,
see this information: Configuring monitoring event sources using monitoring properties.
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.
Using a monitoring profile to configure events
Using
operational commands, you can create a monitoring profile configurable
service directly on the broker, 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 has already been deployed and for which no events
have been configured.
- Use a monitoring profile to override the monitoring properties
of a message flow that has already been deployed, as an alternative
to redeploying the BAR file. The monitoring profile completely replaces
all monitoring properties.
- A single monitoring profile can be applied to many message flows,
provided that the message flows contain the same event sources.
- Monitoring profiles are created directly on the broker using the mqsicreateconfigurableservice command
and the mqsichangeproperties command.
They are not deployed in a BAR file.
- You use the mqsichangeflowmonitoring command
to associate the monitoring profile with a message flow.
- You use the mqsichangeflowmonitoring command
to activate the message flow to emit monitoring events.
- You can use the mqsichangeflowmonitoring command
to enable or disable individual event sources in a message flow.
To configure monitoring events using monitoring properties,
see this information:
Tip: Use the mqsireportflowmonitoring command
to report a list of event sources for a message flow. You can then
use the names of these event source in a subsequent mqsichangeflowmonitoring command
to enable and disable individual event sources from the command line.
Tip: Use the mqsireportflowmonitoring command
to report the monitoring profile for a message flow. You can edit
the profile, to add or change event sources, then update it using
the mqsichangeproperties command.
Tip: Use the mqsireportflowmonitoring 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
using the mqsicreateconfigurableservice and mqsichangeproperties commands.
You can then associate the new profile with the original flow 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.
Last updated Friday, 21 July 2017