Activating and de-activating the exit

Activating and de-activating the exit can be done on different levels:

• broker level: this would make the exit active/inactive for all execution groups and all flows
• execution group level: this would make the exit active/inactive for all flows in the assigned execution group
• flow level: this would make the exit active/inactive exit for only the assigned flow

To activate or de-activate the exit

• On the broker level run the mqsichangebroker command (See below for examples.)
• On the execution group level or on the message flow level run the mqsichangeflowuserexits command. (See below for examples.)

The broker maintains lists for active and inactive exits for every broker, every execution group and every message flow. These lists have different priorities depending on the object level chosen:

• Activation on the execution group level takes precedence over activation on the broker level and
• Activation on the flow level takes precedence over activation on the execution group level.

For example, if the exit is set to inactive for a specific flow activating the exit on the broker level has no effect.

The list of active and inactive exits on the execution group level and on the flow level aren't mutual exclusive. That is, the exit might appear on both of these lists. In this case the exits is considered to be active by the broker. Maintaining the lists of active and inactive exits is crucial to activate or de-activate the exit in the intended way. To verify the list of active or inactive exits:

• On the broker level the mqsireportbroker command can be used for WMB 6.1 and higher. (See below for examples)
• On the execution group level and on the message flow level run the mqsireportflowuserexits command. (See below for examples.)

See the related IBM documentation for WebSphere Message Broker for more details on user exits and on the commands listed in this section.

Activating and de-activating the exit on the broker level

To verify the exits are active on the broker level for broker BROKER run:

mqsireportbroker BROKER

To activate the exit on the broker level for broker BROKER run:

mqsichangebroker BROKER -e MQSoftwareBTMExtension

To de-activate the exit on the broker level for broker BROKER set the list of active exits to be empty running:

mqsichangebroker BROKER -e ""

Activating and de-activating the exit on the execution group level

To get a list of all exits active or inactive for the default execution group for broker BROKER run:

mqsireportflowuserexits BROKER -e default

Note that this gives you the list of exits being active or inactive on the broker and on the execution group level but not on the message flow level.

To add the exit to the active exits list and to make sure the exit does not appear on the inactive exits list on the level of the default execution group for BROKER run:

mqsichangeflowuserexits BROKER -e default -a MQSoftwareBTMExtension -i ""

To de-activate the exit the exit must be added to the list of inactive exits and must not appear on the list of active exits:

mqsichangeflowuserexits BROKER -e default -a "" -i MQSoftwareBTMExtension

Activating and de-activating the exit on the message flow level

To get a list of all exits being active or inactive on the level of the message flow SIMPLE running in the default execution group on BROKER run:

mqsireportflowuserexits BROKER -e default -f SIMPLE

This gives you the list of exits active or inactive on the broker, on the default execution group level but not on the message flow level.

To activate the exit for the flow SIMPLE running in the default execution group BROKER make sure it is added to the active list and is removed from the inactive list:

mqsichangeflowuserexits BROKER -e default -f SIMPLE -a MQSoftwareBTMExtension -i ""

Vice-versa to de-activate the exit for just the flow SIMPLE run:

mqsichangeflowuserexits BROKER -e default -f SIMPLE -a "" -i MQSoftwareBTMExtension