The upgrade of the InterChange Server system involves the following
steps:
Backing up the InterChange Server 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 31..
To back up the system, do the following:
Table 31 summarizes how to back up the different ICS
components.
Table 31. Backup methods for InterChange Server data
Type of data
| Backup method
|
Static data
|
|
Repository
| Use the
repos_copy utility to save some or all of the customized
InterChange Server components. For more information, see the
description of how to back up InterChange Server components in the System
Administration Guide.
|
| Custom
collaboration Java class files (.class), and message files
(.msg)
| Include the collaborations subdirectory of the
ProductDir directory in your system backup:
ProductDir/collaborations
|
|
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 configuration file (InterchangeSystem.cfg)
| Include in your system backup the ICS 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 InterChange Server
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/logs
|
Before you upgrade your InterChange Server system to version
4.3, you must make sure that the system 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 InterChange Server system in a
quiescent state:
- Resubmit failed events or discard the events (this step is
optional). The enhanced failed event management APIs in the 4.3
release allow you to upgrade failed events and process them after the system
upgrade.
- Stop all adapters from polling the event tables by setting the adapter
PollFrequency property to No and restarting the
adapter.
- Let all events run through the system, including all in-process
events. All in-doubt transactions must be resolved.
- Stop the collaborations. This task ensures that no events are
running through the InterChange Server during the upgrade.
- Clear the queues by removing any old events from
the queues.
- Note:
- Perform step 5 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. If you choose to
upgrade failed events and you are using WebSphere MQ transport, do not clear
the queues. Instead, back up the queues and restore them after the
upgrade. See the WebSphere MQ documentation for details.
See the System Administration Guide for more information about
how to stop a running system gracefully.
After backups are complete, you can shut down the InterChange Server system
as follows:
- Shut down InterChange Server and its related components.
- Shut down the database server.
- Shut down the Object Request Broker (ORB). If you are
upgrading from version 4.2.2 then the ORB is the IBM Java
ORB. If you are upgrading from a pre-4.2.2 version then
ORB is the VisiBroker version.
- Shut down WebSphere MQ.
- Note:
- In version 4.1.1 of InterChange Server, the WebSphere MQ
product was called IBM MQSeries.
For more information on system shut down, see the System
Administration Guide.
If any InterChange Server components are running as services on a connected
Windows machine, uninstall those services before performing the
upgrade of WebSphere Business Integration Tools on the Windows machine.
Because the new release will reside in a different location, existing service
definitions will be incorrect. When the upgrade is complete, see the
System Installation Guide for Windows for instructions on
configuring InterChange Server components as services.
