Use the mqsichangeflowmonitoring command on Windows, Linux and UNIX systems to enable monitoring of message flows.
>>-mqsichangeflowmonitoring----integrationNodeName--------------> >--+-+---------------+--+-----------------------------+-+-------> | '- -c --Control-' '- -m --MonitoringProfileName-' | | .-,------------------. | | V | | '- -i --EventState-- -s ----EventSourceAddress-+-----' (1) >--+- -e --IntegrationServerName--+- -f --MessageFlow-+-+-------> | '- -j --------------' | '- -g -- -j -----------------------------------------' >--+-----------------------+--+-------------------+------------>< '- -k --applicationName-' '- -y --libraryName-'
You must specify either -f or -j. If you do not specify one of these arguments you receive an error message.
You must specify either -e or -g. If you do not specify one of these arguments you receive an error message.
You must specify either -f or -j. If you do not specify one of these arguments you receive an error message.
When you set this parameter, you must also set either the -f (message flow) parameter, or the -j (all message flows) parameter. To enable monitoring for a named message flow in a specific application, set the -k and -f parameters. To enable monitoring for all message flows in an application, set the -k and -j parameters.
You can use this parameter with the -y (library name) parameter to specify that the message flow is contained in a library referenced by the application.
If there is no monitoring profile with the specified name on the specified integration node, the command completes successfully, and the message flows attempt to use the specified monitoring profile. Each message flow logs a warning in the User Trace to indicate that it was instructed to use a nonexistent monitoring profile. No event message is created. If a monitoring profile with the specified name is later deployed to the integration node, the message flows do not immediately begin to use it. A refresh of the monitoring state can be triggered by issuing the command again with the -c option to activate or reactivate monitoring.
If a message flow contains two or more nodes with identical names, the event sources on those nodes cannot be accurately addressed. If this is attempted, behavior is undefined.
<node name> is the label of the node as known by the IBM® Integration Bus runtime components. If the node is in a subflow, the label reflects this. For example, flow A contains an instance of flow B as a subflow that is labeled 'myB'. Flow B contains an instance of a Compute node that is labeled 'myCompute'. The <node name> for the Compute node is 'myB.myCompute'.
If you issue this command with a comma separated list to enable or disable individual event sources, and you have not already issued the command with the -c parameter, monitoring is not activated for these event sources. To enable monitoring, reissue the command with the -c parameter set to active.
When you set this parameter, you must also set either the -f (message flow) parameter, or the -j (all message flows) parameter. To enable monitoring for a named message flow in a specific library, set the -k and -f parameters. To enable monitoring for all message flows in a library, set the -k and -j parameters.
mqsichangeflowmonitoring IBNODE -e default
-f messageFlow1 -m monitoringProfile1
mqsichangeflowmonitoring WBRK_BROKER -c active -g -j
mqsichangeflowmonitoring IBNODE -c active -e default -k application1 -j
mqsichangeflowmonitoring IBNODE -c active -e default -y library1 -k application1 -f myflow1
mqsichangeflowmonitoring IBNODE
-e default
-f myMessageFlow
-s "Node1_Label.terminal.out,Node2_Label.terminal.in"
-i enable