Applying service to IBM Integration Bus

Install IBM® Integration Bus fix packs and convert your integration nodes to run the new code.

About this task

Service updates and other fixes are delivered occasionally in the form of fix packs. You can find information about the fix packs available on the IBM Integration Bus support web page.

IBM Integration Bus fix packs are complete IBM Integration Bus installations and are installed in the same way as the initial product release; see Installing IBM Integration Bus software. You can install a fix pack on the same computer as a previous release, or on a different computer; for information about installing more than one fix pack (at the same or different levels) on a single computer, see Coexistence of IBM Integration Bus Version 10.0 with previous versions.

After you install a fix pack, you can enable new features by changing the function level of your integration nodes; see Changing the function level of your integration nodes. Before you change the function level, review the function that is new in the fix pack that you installed (and in any previous fix packs) to understand the behavior changes that might occur when you change the function level; see New function added in Version 10.0 fix packs.

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.

If you installed the fix pack on the same computer as an existing installation of IBM Integration Bus Version 10.0, complete the following steps to convert your integration nodes to run with the new code.

Note: These methods are valid only for switching the integration node between different fix pack levels that are associated with the same product code version. You must use the mqsimigratecomponents command to migrate an integration node to a different version and release.

Procedure

On Windows, complete one of the following steps:
- Start the IBM Integration Console for the new fix pack level, and then start the integration node by using the mqsistart command.
- Start the IBM Integration Toolkit for the new fix pack level. Any local integration nodes that are stopped and configured to start automatically with the IBM Integration Toolkit use the product code that is associated with the version of the IBM Integration Toolkit.
- Start the integration node by using a script that first runs the mqsiprofile for the new fix pack level.
- If your integration node is configured to start as a WebSphere® MQ service, you must manually update the MQ Service definition on the queue manager that is associated with the integration node so that the integration node uses the new code. For more information, see Applying service to an integration node that starts under the control of a WebSphere MQ queue manager.
On Linux®:
- Start the IBM Integration Toolkit for the new fix pack level. Any local integration nodes that are stopped and configured to start automatically with the IBM Integration Toolkit use the product code that is associated with the version of the IBM Integration Toolkit.
- Run the mqsiprofile command from the new fix pack level, and start your integration node by using the mqsistart command.
- If your integration node is configured to start as a WebSphere MQ service, you must manually update the MQ Service definition on the queue manager that is associated with the integration node so that the integration node uses the new code. For more information, see Applying service to an integration node that starts under the control of a WebSphere MQ queue manager.
On UNIX:
- Run the mqsiprofile command from the new fix pack level, and start your integration node by using the mqsistart command.
- If your integration node is configured to start as a WebSphere MQ service, you must manually update the MQ Service definition on the queue manager that is associated with the integration node so that the integration node uses the new code. For more information, see Applying service to an integration node that starts under the control of a WebSphere MQ queue manager.
On z/OS®, consult the Program Directory for IBM Integration Bus for z/OS; see Finding the latest information.

What to do next

You can use any Version 10.0 fix pack level of the IBM Integration Toolkit to deploy integration solutions to an integration node that runs any Version 10.0 fix pack level.