Changing the function level of your integration nodes

You can change the function level of your integration nodes to enable the use of functionality that is supplied in the latest fix pack.

About this task

When a new fix pack is installed, it might include new functionality or message flow nodes that you can add to your message flows to provide or enable specific capabilities.

Message flow nodes that are added in later fix packs are available in the IBM® Integration Toolkit, and you can include these nodes in a message flow. You can deploy the message flow to an integration node only if you set the function level of that integration node to the value that represents the fix pack in which the message flow nodes are included.

Because you can control the function level of each integration node, you can try out new capabilities on test integration nodes without affecting the operation of your production integration nodes. When you are satisfied that the capabilities provide the function that you require, and work as you expect, you can set the function level of other integration nodes in your domain, when appropriate.
Note: IBM Integration Bus supports interoperability between different fix packs of the same version. However, runtime errors might occur if you create (or edit) an artifact, enable a new feature that was added in a fix pack, and then attempt to use the artifact with an IBM Integration Bus component that is using an earlier fix pack. For example, the following situations might generate errors:
  • Editing source artifacts in the IBM Integration Toolkit that were created on an IBM Integration Toolkit that is using a later fix pack.
  • Building BAR files from artifacts that were created on an IBM Integration Toolkit that is using a later fix pack than the build system.
  • Deploying BAR files that were built by using a component that is using a later fix pack than the target integration node.
  • Connecting a Java™ administration application (including the IBM Integration Toolkit and commands) to a remote integration node that is using a later fix pack.

A good practice is to ensure that downstream components (such as integration nodes and build systems) are using the same or later fix pack as upstream components (such as the IBM Integration Toolkit). An alternative option is to ensure that you install the earliest common fix pack on the build systems so that you are warned about any incompatible options as early as possible.

To identify the function level of an integration node, use the mqsireportbroker command and check the value of Fixpack capability level.

To change the function level of an integration node, use the mqsichangebroker command, specifying the -f flag with the appropriate value; for example:
mqsichangebroker IBNODE -f 10.0.0.2
or
mqsichangebroker IBNODE -f all
where IBNODE is the name of the integration node where you want to use new function.

For more information about message flow nodes added in fix packs, and the use of the mqsichangebroker command, see mqsichangebroker command.