Upgrading hardware and supporting software

When you upgrade your system, you must consider potential upgrade needs of both hardware and supporting software. For hardware and software requirements, refer to Installation requirements.

This section summarizes upgrades to the following supporting software:

Important:
If you must upgrade any supporting software, be sure to arrange for a System Administrator to back up the supporting software before upgrading.

Upgrading the Object Request Broker

As of the 4.2.2 release, the WebSphere InterChange Server system no longer uses the VisiBroker Object Request Broker (ORB) to handle communication between ICS and its clients (such as connectors, WebSphere Business Integration tools, SNMP agents, and access clients). Instead, the InterChange Server system uses the IBM Java ORB. The 4.3 ICS Installer automatically installs the IBM Java ORB as part of the Java Runtime Environment (JRE). The IBM Java ORB supplied with the 4.3 release is upgraded from the version supplied with 4.2.2. Therefore this step is necessary regardless of which version of ICS you are upgrading from.

InterChange Server now uses the IBM Transient Naming Server instead of the VisiBroker Smart Agent to provide its naming service. This change has also been in effect since version 4.2.2. To upgrade your system to use the new naming server, do one of the following, depending on whether the VisiBroker Smart Agent is installed on the same host machine as the IBM Transient Naming Server and must remain on this same host machine:

Note:
For a general overview of the IBM Java ORB, see the System Administration Guide.

Use of properties to set up the IBM Java ORB has been set in the startup scripts that 4.3 installation provides. However, if you customized any ORB properties, you might need to make similar changes to the new scripts to accommodate the migration to the new version of the IBM ORB. For more information on IBM ORB properties and their VisiBroker equivalents, refer to Configuring the Object Request Broker.

Upgrading the Java software

The WebSphere InterChange Server system now uses the Java Runtime Environment (JRE) that IBM provides. Also, if you are using the Java Development Kit (JDK), you will need to upgrade your version to the supported level listed in Table 5, Table 6, Table 7 or Table 8, depending on your platform. The steps to install the JDK depend on the particular UNIX system you are using. For detailed instructions, see Installing the Java software. It is a good idea to uninstall your existing JRE and JDK before you install the new version of the JDK and the latest version of InterChange Server.

Note:
If you have customized the server startup scripts CWSharedEnv.sh, you must back this up before upgrading to version 4.3. The script is changed in order to support the use of JDK 1.4.2 in the 4.3 release. The alterations can be merged into the new script after the installation is completed and tested.

Upgrading WebSphere MQ

Important:
The need to perform the steps in this section depends on the version of your current InterChange Server:

When you upgrade WebSphere MQ, you can take either of the following paths:

When you have upgraded to WebSphere MQ 5.3, you should apply WebSphere MQ CSD07 patch. If you have elected to upgrade failed events and are using WebSphere MQ transport, then you will have backed up the previous data. At this point you should restore this backed up information. Please consult the WebSphere MQ documentation on how to restore queue data.

After you have upgraded the WebSphere MQ software, you need to configure it for use with InterChange Server. For more information, see the description in Configuring WebSphere MQ properties using the wizard.

Upgrading the database software

The migration procedure can optionally include an "in-place" database upgrade. If in-place migration is preferred then the newly installed InterChange Server will read in the existing repository information and perform necessary upgrades during the first server startup. If in-place migration is not chosen, then when InterChange Server is launched it will be with a completely new and empty repository. In the remainder of this section differences in procedure for in-place migration are explicitly stated.

Compare the version of your existing database software with the version that the 4.3 version of the product supports (Software requirements). For example, the version 4.1.1 supports version 7.2 of DB2 whereas version 4.3 supports version 8.1 of DB2.

If you are migrating from older versions of InterChange Server, check to see if you must also upgrade your database software. Compare the version of your existing database software with the currently supported versions (Software requirements). Using DB2 users as an example: if you are migrating from 4.2.x, you only need to apply FP5, but if you are migrating from 4.1.1, you must follow the migration procedure in DB2 manuals to migrate from DB2 7.2 to 8.1 and then apply FP5.

If you must upgrade your database software, make sure the database administrator (DBA) takes the following steps:

Consult your database server documentation for instructions on how to perform backups and upgrade database software. For more information on how to migrate the database, proceed to Importing the database.

Copyright IBM Corp. 1997, 2004