Upgrading existing adapters

For each existing adapter you are upgrading, perform the tasks listed in the topics below:

Upgrading business objects

Upgrading from releases 2.0.1, or 2.1.0, 2.2.0, or 2.3.1

It is not necessary to upgrade business objects if you are upgrading from WebSphere Business Integration Adapters versions 2.0.1, or 2.1.0, 2.2.0, or 2.3.1.

Upgrading from release 2.0

Note:
Perform this step only if upgrading existing adapters from WebSphere Business Integration Adapters version 2.0.
For each adapter being upgraded, perform the following actions.
  1. Using the new version of Business Object Designer that you have installed, load the adapter's existing business object definitions and save them using the same names. The business object definitions will be saved in the latest format used by WebSphere Business Integration Adapters.
  2. Note:
    If you are upgrading using WebSphere Business Integration Message Broker 5.0 as the integration integration broker, skip this step. Instead, update the business objects by reimporting them with System Manager, as described in "Deploying to a message broker workspace".
    Import the revised business object definitions into WebSphere MQ Integrator Broker's MRM using the XML Schema Importer with reset mode, which removes all existing information from the message set before the import of the updated XML Schema is started. To re-import the business object definitions, issue the following command for each definition:
     mqsiimpxmlschema -c -f parameter_file -o filename 
     
    

    Where:

    parameter_file
    is the name of the XML Schema importer parameters file.
    filename
    is the file in which the importer is to write the message set name followed by the message set identifier, separated by an equal sign (=). If the file already exists the line will be appended to this file.
    For more information on importing XML schemas and using the mqsiimpxmlschema command, see WebSphere MQ Integrator Broker: Working with Messages
  3. If Business Object Designer and the WebSphere MQ Integrator Broker Control Center are on separate machines that do not use a shared file system, copy the generated files to the machine where the integration broker is running.
  4. From WebSphere MQ Integrator Broker's Control Center, replace the existing message sets and messages in your workspace.
  5. Replace the existing assigned message sets with the new ones.
  6. Re-deploy the message sets on the integration broker.

Updates to the connector configuration files

New releases of WebSphere Business Integration Adapters include certain changes to the connector configuration files. Refer to the sections below depending upon the release from which you are upgrading.

Upgrades from release 2.3.1

If you are upgrading from WebSphere Business Integration Adapters versions 2.3.1, be aware that there is a new standard configuration property XMLNameSpaceFormat. The default value for this is short. If you want the XMLNameSpaceFormat to be long, you must explicitly specify this in the connector configuration file. You might also have to change the value of the RFH2messagedomain property, depending on which message broker you are using. Refer to Choosing XML Namespace lengthfor instructions on choosing the correct XMLNameSpaceFormat.

Upgrades from release 2.2.0

WebSphere Business Integration Adapters versions 2.3.0 and later include the following change to the connector configuration file . A new property, RFH2MessageDomain, has been added to the standard configuration properties. This property allows you to set the message domain to xml, if desired (default is mrm). Refer to Appendix A, WebSphere MQ message formats and Appendix C, Standard configuration properties for connectors for more information.

When you open your existing connector configuration file using the new version of Connector Configurator, the necessary changes to the file are made automatically. However, you may wish to verify that the new property is present and set as desired. To do so, perform the following actions:

  1. Using the new version of Connector Configurator that you have installed, open the adapter's connector configuration file.
  2. Click the Standard Properties tab.
  3. Make any additional configuration property changes specific to the connector as specified in its adapter user guide.
  4. Save the file using its existing name.

Upgrades from releases prior to 2.2.0

WebSphere Business Integration Adapters versions 2.2.0 and later include the following changes to the connector configuration file :

Tip

For information about using the Connector Configurator and to learn about changes to connector configuration properties in the new version of the adapter, refer to the adapter 's user guide.

When you open your existing connector configuration file using the new version of Connector Configurator, the necessary changes to the file are made automatically. However, you should still verify that the changes are correct as described below.

For each upgraded adapter, perform the following actions.

  1. Using the new version of Connector Configurator that you have installed, open the adapter's connector configuration file.
  2. Click the Standard Properties tab.
  3. Ensure that the values for the following properties are set correctly for the business integration system:
    1. CharacterEncoding
    2. jms.MessageBrokerName (formerly called QueueManagerName)
    3. jms.Password (formerly QueueManagerPassword)
    4. jms.UserName (formerly QueueManagerLogin)
    5. jms.NumConcurrentRequests (formerly ConcurrentRequests)
    6. Locale
    7. SynchronousRequestTimeout (formerly Timeout).
  4. Make any additional configuration property changes specific to the connector as specified in its adapter user guide.
  5. Save the file using its existing name.

Configuring the new connector startup scripts

The startup scripts for connectors have changed sufficiently in WebSphere Business Integration Adapters 2.2.0 that you need to use the new versions. Customize the startup scripts, as described in Configuring the connector startup files, shortcuts, and environment variables.

Important

The current version of the WBIA Installer creates shortcuts in a Windows installation only. If you have existing CDE shortcuts, they are not updated.

Copyright IBM Corp. 1997, 2004