Overview of Adapter Framework changes

Unlike previous releases of the adapter framework, Adapter Framework 2.6 software is bundled separately from the InterChange Server integration broker. This makes possible separate installations and a more flexible enhancement path for both the adapter framework and InterChange Server. It also isolates the adapter framework from releases prompted solely by server enhancements, and vice versa. This section discusses these and other changes to the adapter framework that may affect adapter installation by discussing the following topics:

.jar files and directories

Through release 2.4.x the adapter framework was shipped in a CrossWorlds.jar file that also contained ICS. ICS continues to be packaged and delivered in the CrossWorlds.jar file; however, the adapter framework, beginning with version 2.6, is packaged and delivered in wbiart.jar.

Note:
The change in .jar file names may have implications if you are upgrading from a 2.3.x to a 2.4.x adapter prior to migrating to Adapter Framework 2.6.

Environment variables

Previously released adapters and adapter frameworks were installed in the same directory as ICS. The task of migrating adapters and ODAs to the new adapter framework begins with changing environment variables in adapter and ODA scripts to point to the new file and location of the 2.6 version of the adapter framework (where you install the wbiart.jar file). Because the new adapter framework resides in a file and in a directory other than that of ICS, the environment variables in start scripts for adapters and ODAs issued as part of previous releases must be modified. For further information and links to TechNotes containing updated start scripts, see Migrating adapters to Adapter Framework 2.6.

If you are configuring Adapter Framework 2.6 with an integration broker that resides on a separate machine, you must also modify the adapter start script to point to the remote integration broker. Alternatively, you can modify the adapter configuration file to point to the queue manager of the remote integration broker. For further information, see the Connector Development Guide and the Connector Configurator section of any adapter guide.

JRE 1.4.2 compatibility

Adapter Framework 2.6 uses Java Runtime Environment (JRE) 1.4 and higher. Adapters released with previous versions of the framework used earlier versions of the JRE. For example, Adapter Framework 2.4.x supported JRE 1.3.1. Some previously released adapters cannot be migrated because their application or technology libraries are not supported on JRE 1.4.2

Start scripts

If you want to migrate adapters and ODAs released with Adapter Framework 2.4.x, you must substitute modified start scripts that point to the new location and file name of Adapter Framework 2.6. For a high-level description of these changes, see Environment variables. For a detailed account of adapter- and ODA-specific changes to those scripts, see Overview of migrating adapters to Adapter Framework 2.6.

Connector agent parallelism CAP deprecation

The connector agent parallelism (CAP) feature that some C++ adapters used is deprecated in the 2.6 version of Adapter Framework. If your 2.4.x or earlier framework adapters are configured to use the CAP feature, you may want to consider a Java-based adapter as a solution.

Copyright IBM Corp. 1997, 2004