Changing a message flow to point to a different map

When you design a message flow to use either a source map or a compiled map, consider whether you might change the message flow later to point to a different map. There are fewer steps required to point to a different a compiled map than to point to a different source map. To dynamically change a message flow to point to a different map, design the message flow to use compiled maps.

To change a message flow to point to a different source map:
  1. In the TX map node, select a new source map or executable map.
  2. Recompile the broker archive (BAR) file.
  3. Deploy the new BAR file.
You cannot dynamically change the TX map node's executable map or source map properties by using the the BAR file override properties in IBM® Integration Toolkit or by using the IBM Integration Bus mqsiapplybaroverride command.
To change a message flow to point to a different compiled map, you can do one of the following:
  • Change the map server location property:
    1. In the TX map node, change the Map Server Location property to point to a different compiled map.
    2. Recompile the broker archive (BAR) file.
    3. Deploy the new BAR file.
  • Override the BAR file:
    1. Use the BAR file override properties in IBM Integration Toolkit or the IBM Integration Bus mqsiapplybaroverride command to change the map server location.
    2. Redeploy the BAR file. You do not have to recompile the BAR file.
  • Specify a dynamic binary map or a dynamic path to a map in the IBM Integration Bus local environment tree

    This method takes precedence over the map name or map location specified in the IBM Integration Toolkit or by the BAR file. When you use the local environment tree to specify the map, you do not have to recompile or redeploy the BAR file.