Preparing the existing system

Before upgrading any system, you must perform the following steps:

Preserving existing user projects

Any user projects defined in your existing WebSphere Business Integration Server Express or Express Plus system are stored locally with the tools. When you run the installer to upgrade to another version of WebSphere Business Integration Server Express or Express Plus, the newly upgraded tools will not automatically recognize the path to the System Manager workspace in which your existing user projects reside.

To make the existing user projects available in your upgraded system, you can do either of the following:

Migrating existing projects

To migrate existing projects, first export them as a solution to a temporary location, then import them back into your newly upgraded System Manager.

Exporting user project solutions

To export a user project and the integration components it references as a solution, perform the following steps:

Note:
Exporting a solution migrates only the integration components and shortcuts are included in the user projects that you select for that solution. If you want to also migrate additional integration components that have not been included as shortcuts in any user project, then also follow the procedures for Exporting components to a package using System Manager in the System Implementation Guide.

  1. In the WebSphere Business Integration System Manager view, expand the User Projects folder, then right-click the InterChange Server Projects folder and choose Export Solution from the context menu. System Manager displays the Export Solution wizard.
  2. To select the components you want to export, perform one of these options:
  3. Either type the full path and name of the directory into which the solution should be exported in the text field at the bottom of the wizard screen, or click Browse to navigate to the desired directory.
  4. Click Finish. The System Manager does the following to export the solution in the directory specified in Step 3:
    1. Creates a User directory that contains the shortcuts in the user projects selected during the export of the solution.
    2. Creates a System directory that contains the directories of the integration component library referenced by the shortcuts in the user projects selected during the export of the solution.
  5. When prompted that the export operation completed successfully, click OK.
Importing user project solutions

With InterChange Server Express running, connect System Manager to your InterChange Server Express instance and perform the following steps:

  1. Expand the User Projects folder, right-click InterChange Server Projects, and select Import Solution.
  2. Either type the full path and name of the directory in which the exported solution exists into the Solution directory name field, or click Browse to navigate to the desired directory.
  3. Click Finish. The System Manager creates the integration component libraries and user projects defined in the exported solution in your environment.

Upgrading software prerequisites

The Launchpad installation interface will automatically upgrade some software prerequisites. However, if you have a version of the prerequisite that is prior to one supported for upgrade by the current version of WebSphere Business Integration Server Express or Express Plus, you will have to manually upgrade the prerequisite before upgrading WebSphere Business Integration Server Express or Express Plus. (Refer to http://www.ibm.com/software/integration/wbiserverexpress for information about the supported versions of prerequisite software.) You can also choose to manually upgrade the prerequisite for any other reason. If you manually upgrade a prerequisite to a version that is supported by the current release (WebSphere Business Integration Server Express 4.4), the Launchpad will detect that you have a current version of that prerequisite when you perform the rest of the upgrade. Follow the upgrade instructions provided with a particular prerequisite if you manually upgrade it.

The following sections describe steps that must be done for any database and the upgrade scenarios for several software prerequisites. Make sure to follow the steps in Backing up the system before uninstalling or upgrading any software.

Database migration options

In preparing your WebSphere Business Integration Express system for an upgrade, you have two options for migrating the database: an in-place database migration and a without in-place database migration. An in-place database migration means re-using the old repository and letting WebSphere Business Integration Express do the upgrade of the repository during the first WebSphere Business Integration Express server startup. A without in-place database migration means upgrading with a brand new and empty repository database. Make sure to follow the special instructions in Backing up the system for in-place database migration.

IBM DB2 Universal Database

The following sections apply to IBM DB2.

Prior DB2 versions

If you uninstall a prior version of DB2, so that no DB2 version is present, the Launchpad will prompt you to install DB2 version 8.2 Express.

If you have a version of DB2 that is below the required version (is below 8.1.5), the Launchpad will prompt you to install DB2, version 8.2 Express.

If you have DB2 version 8.1.5 or higher installed, the Launchpad will not prompt you to install a newer version of DB2. In this case, if you are on a version of DB2 prior to 8.2, and wish to upgrade to version DB2 8.2, you must upgrade it manually.

Note:
If a supported version of DB2 (8.15 or higher) is already installed, follow the instructions for "in-place" migration as explained in Backing up the system.
Transferring the previous user login

If you are upgrading from a previously supported DB2 version (8.1.2 Express - 8.14 Express) by means of the Launchpad you will need to use the same username and password that was used for WebSphere Business Integration Express with the old version of DB2 with the new version of DB2 that is installed. The username and password supported with WebSphere Business Integration Server Express or Express Plus version 4.3.1 was smbadmin, with password smbP4$$word so if this DB2 instance was used with WebSphere Business Integration Server Express or Express Plus version 4.3.1, the username/password must again be this combination.

To do this:

  1. Stop all DB2 services.
  2. Add the username smbadmin with password smbP4$$word to the Windows "Administrator" group.
  3. During the upgrade procedure, the Launchpad will prompt you for the database username and password. Use the same username/password as above.

Microsoft SQL Server

If you are using Microsoft SQL Server 2000 as your database, you must manually upgrade it according to the Microsoft SQL Server upgrade instructions. The Launchpad will not upgrade it automatically.

IBM WebSphere Application Server

WebSphere Business Integration Server Express or Express Plus version 4.4 supports WebSphere Application Server Express version 5.1.1 or higher. Version 6.0 is the version that the Launchpad installs. You should uninstall any version of WebSphere Application Server prior to 5.1.1. If you have 5.1.1 already and wish to upgrade to 6.0, you must do so manually as the Launchpad will not prompt you to do so.

Note:
Installing WAS 6.0 Express via Launchpad over previous WebSphere Application Server Express versions (WebSphere Application Server Express 5.1, or 5.1.1 for example) may result in two co-existing installations of WAS on the machine. In this case, LaunchPad will deploy Web-based tooling onto the WAS 6.0 Express installation.

IBM WebSphere MQ Server and Client

If you have an older version of IBM WebSphere MQ installed that was supported by a previous version of WebSphere Business Integration Express, Launchpad will do an automatic upgrade to the supported version. For example, if you have MQ 5.3 CSD 05 installed, Launchpad will do an automatic upgrade to CSD 07.

IBM Java Development Kit

The Launchpad installs the appropriate version of the IBM JDK (version 1.4.2). It is not necessary to remove the previous version.

Putting the system in a quiescent state

Before you upgrade your system, you must make sure it is in a quiescent state. This means that all in-progress events are completed and all in-doubt transactions are resolved before backing up the environment and performing the upgrade procedure.

The following steps describe how to put the system in a quiescent state:

  1. Resubmit failed events or discard the events (this step is optional).
  2. Stop all connectors from polling the event tables by setting the connector PollFrequency property to No and restarting the connector.
  3. Let all events run through the system, including all in-process events. All in-doubt transactions must be resolved.
  4. Clear the queues by removing any old events from the queues.
    Note:
    Perform step 4 only if you are not processing your failed events and choose to resubmit the events from the application. Otherwise, the queues should be empty, but double-check to be sure.
  5. Shutdown all Windows programs and stop all processes related to InterChange Server Express.

See the System Administration Guide for more information about how to stop a running system gracefully.

Backing up the system

Backing up the system allows you to recover any files that might be overwritten inadvertently during the installation of the new version. Before performing the upgrade procedure, back up both static data and dynamic data (changeable data that you back up on a regular basis, regardless of upgrades). For examples of static and dynamic data, see Table 3.

To back up the system, do the following:

Table 3 summarizes how to back up the different components.

Table 3. Backup methods for data
Type of data Backup method
Static data
Repository Use the repos_copy utility to save some or all of the customized system components. For more information, see the description of how to back up components in the System Administration Guide.
Custom map Java class files (.class) To include these files in your system backup, make sure the following directory is in your system backup:
ProductDir\DLMs
Custom connectors Include the following directory in your system backup: ProductDir\connectors\connector_name, where "connector_name" is the name of the custom connector.
Customized startup scripts If you have customized any startup scripts, make sure that they are included in your system backup.
ICS Express configuration file (InterchangeSystem.cfg) Include in your system backup the ICS Express configuration file, which resides in the ProductDir directory.
Dynamic data
Cross-reference, failed events, and relationship tables Use the database backup utility for the database. For more information, see the description of how to back up system components in the System Administration Guide.
Connector event archive tables Use the database backup utility for the database that contains these tables.
Log files Include the following directory in your system backup:
ProductDir\log

Shutting down the system

After backups are complete, you can shut down the system as follows:

  1. Shut down InterChange Server Express and its related components.
  2. Shut down the database server.
  3. Shut down WebSphere MQ.

For more information on system shutdown, see the System Administration Guide.

Copyright IBM Corp. 2004, 2005