Applying service to IBM App Connect Enterprise

Install IBM® App Connect Enterprise fix packs to get the latest service updates and fixes.

About this task

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

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

When you have installed a fix pack, see New function added in Version 13.0.1 for information about the function that is provided in that fix pack and in any previous fix packs.

IBM App Connect Enterprise supports interoperability between different fix packs of the same version. However, errors might occur if you create (or edit) an artifact or enable a new feature, and then use the artifact with a component that is using an earlier fix pack. For example, the following situations might generate errors:

  • Editing source artifacts in the IBM App Connect Enterprise Toolkit that were created on an IBM App Connect Enterprise Toolkit that is using a later fix pack.
  • Building BAR files from artifacts that were created on an IBM App Connect Enterprise 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 server.
  • Connecting a REST administration application (including the IBM App Connect Enterprise Toolkit and commands) to a remote integration server that is using a later fix pack.

It is good practice to ensure that downstream components (such as integration servers and build systems) are using the same or later fix pack as upstream components (such as the IBM App Connect Enterprise 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 App Connect Enterprise 13.0, complete the following steps to convert your integration nodes to run with the new code. These methods are valid only for switching an integration node between different fix pack levels that are associated with the same product code version. You must use the ibmint extract node command to migrate an integration node to a different version and release.

Procedure

  • Windows platformOn Windows, complete one of the following steps:
    • Start the IBM App Connect Enterprise Console for the new fix pack level, and then start the integration node by using the mqsistart command.
    • Start the IBM App Connect Enterprise Toolkit for the new fix pack level. Any local integration nodes that are stopped and configured to start automatically with the IBM App Connect Enterprise Toolkit use the product code that is associated with the version of the IBM App Connect Enterprise 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 an IBM MQ service, you must manually update the IBM MQ Service definition on the queue manager that is associated with the integration node. This update enables the integration node to use the new code. For more information, see Applying service to an integration node that starts under the control of an IBM MQ queue manager.
  • Linux platformOn Linux®:
    • Start the IBM App Connect Enterprise Toolkit for the new fix pack level. Any local integration nodes that are stopped and configured to start automatically with the IBM App Connect Enterprise Toolkit use the product code that is associated with the version of the IBM App Connect Enterprise 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 an IBM MQ service, you must manually update the IBM MQ Service definition on the queue manager that is associated with the integration node. This update enables the integration node to use the new code. For more information, see Applying service to an integration node that starts under the control of an IBM MQ queue manager.
  • AIX platform On AIX® :
    • 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 an IBM MQ service, you must manually update the IBM MQ Service definition on the queue manager that is associated with the integration node. This update enables the integration node to use the new code. For more information, see Applying service to an integration node that starts under the control of an IBM MQ queue manager.

What to do next

You can use any Version 12.0 fix pack level of the IBM App Connect Enterprise Toolkit to deploy integration solutions to an integration server that runs any Version 12.0 fix pack level.