WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Activating monitoring

Use the mqsichangeflowmonitoring command to activate monitoring after you have configured monitoring event sources.

Before you start:
You must have configured monitoring event sources by using either monitoring properties or a monitoring profile; see these topics:
The use of a monitoring profile configurable service overrides the monitoring properties of a message flow.

If monitoring is activated for a message flow, and neither monitoring properties nor a monitoring profile configurable service have been configured for the flow, the default behavior is for transaction events to be emitted from each input node of the message flow. The events contain the bit stream of the input message.

Activating monitoring from the command line

Use the -c active parameter. You can activate monitoring for all message flows in all execution groups, or specify the execution groups and message flows for which monitoring is to be activated.
  • To activate monitoring for all message flows in all execution groups on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring myBroker -c active -g -j
    To activate monitoring for all message flows in all execution groups on z/OS®: z/OS platform
    F MI10BRK,cm c=active,g=yes,j=yes
  • To activate monitoring for all message flows in the default execution group on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring myBroker -c active -e default -j
    To activate monitoring for all message flows in the default execution group on z/OS: z/OS platform
    F MI10BRK,cm c=active,g=default,j=yes
  • To activate monitoring for the myFlow message flow in the default execution group on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring myBroker -c active -e default -f myFlow
    To activate monitoring for the myFlow message flow in the default execution group on z/OS: z/OS platform
    F MI10BRK,cm c=active,g=default,f=myFlow
  • To activate monitoring for all message flows in application application1 in execution group default on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring MB8BROKER -c active -e default -k application1 -j 
    To activate monitoring for all message flows in application application1 in execution group default on z/OS:z/OS platform
    F MB8BROKER,cm c=active,e=default,k=application1,j=yes 
  • To activate monitoring for message flow myflow1 in library library1, referenced by application application1, in execution group default, on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring MB8BROKER -c active -e default -y library1 -k application1 -f myflow1
    Activate monitoring for message flow myflow1 in library library1, referenced by application application1, in execution group default, on z/OS:z/OS platform
    F MB8BROKER,cm c=active,e=default,y=library1,k=application1,f=myflow1

Deactivating monitoring from the command line

Use the -c inactive parameter. You can deactivate monitoring for all message flows in all execution groups, or specify the execution groups and message flows for which monitoring is to be activated.
  • To deactivate monitoring for all message flows in all execution groups on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring myBroker -c inactive -g -j
    To deactivate monitoring for all message flows in all execution groups on z/OS: z/OS platform
    F MI10BRK,cm c=inactive,g=yes,j=yes
  • To deactivate monitoring for all message flows in the default execution group on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring myBroker -c inactive -e default -j
    To deactivate monitoring for all message flows in the default execution group on z/OS: z/OS platform
    F MI10BRK,cm c=inactive,g=default,j=yes
  • To deactivate monitoring for the myFlow message flow in the default execution group on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring myBroker -c inactive -e default -f myFlow
    To deactivate monitoring for the myFlow message flow in the default execution group on z/OS: z/OS platform
    F MI10BRK,cm c=inactive,g=default,f=myFlow
  • To deactivate monitoring for all message flows in application application1 in execution group default on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring MB8BROKER -c inactive -e default -k application1 -j 
    To activate monitoring for all message flows in application application1 in execution group default on z/OS:z/OS platform
    F MB8BROKER,cm c=inactive,e=default,k=application1,j=yes 
  • To deactivate monitoring for message flow myflow1 in library library1, referenced by application application1, in execution group default, on Linux, UNIX, and Windows: Linux platformUNIX platformWindows platform
    mqsichangeflowmonitoring MB8BROKER -c inactive -e default -y library1 -k application1 -f myflow1
    Activate monitoring for message flow myflow1 in library library1, referenced by application application1, in execution group default, on z/OS:z/OS platform
    F MB8BROKER,cm c=inactive,e=default,y=library1,k=application1,f=myflow1
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:27


Task topicTask topic | Version 8.0.0.7 | ac60388_