56 WebSphere InterChange Server Migration Scenarios
However, repository migration, especially large repository migrations, will
fully utilize CPU capacity and be much quicker with faster hardware and
more memory.
Even though WebSphere InterChange Server 4.3.0 incorporates
significant performance improvements, a timely and successful migration
requires the availability of more CPU or processing power and memory
above the minimum level cited in the installation guides. Table 4-2 lists the
recommended hardware configuration.
Table 4-2 Recommended hardware configuration
򐂰 Depending on the migration method, additional hardware and machines may
be required. For example, if a test or staging migration is performed before
migrating, the production repository will require additional hardware or
In general, the migration hardware environment must be modeled to at least the
WebSphere InterChange Server V4.3 minimum hardware environment with more
memory and increased hard disk space storage made available for the migration
process and backups.
4.3 Software considerations
Most third-party software dependencies have been removed in the WebSphere
InterChange Server V4.3 environment. In previous versions, a WebSphere ICS
environment deployed the Inprise VisiBroker product as the object request broker
agent. Version 4.3 uses the IBM ORB agent. The Version 4.3 environment can
be configured as a total IBM software solution under:
򐂰 IBM AIX V5.1 or 5.2
򐂰 IBM WebSphere MQ 5.3
򐂰 IBM WebSphere InterChange Server V4.3
򐂰 IBM WebSphere Application Server 5.1
򐂰 IBM Universal Database Enterprise Edition V8.1
AIX Windows
Processor Dual Processor IBM
pSeries 610 6E1 class or
375 Mhz minimum
Pentium IV
1 Ghz
Memory 1024 MB 1024 MB
Hard disk drive space 40 GB 40 GB
Chapter 4. General planning 57
Table 4-3 briefly highlights the change progression in the software stack
supported to run a typical WebSphere InterChange Server environment for AIX.
Table 4-3 Software changes in the WebSphere InterChange Server environment
In a Windows environment, software versions follow the same progression as in
Table 4-3. Refer to 3.3, “System architecture changes” on page 49 for a detailed
overview of the specific operating system levels supported for each version.
More software changes that should be considered during migration planning:
򐂰 Major operating system migrations may be required in some AIX WebSphere
InterChange Server environments.
򐂰 Changing the object request broker replaces the Object Activation Daemon
with WebSphere MQ triggering and requires some modification to Server
Access Interface configurations.
򐂰 Changing the object request broker means replacing the VisiBroker naming
service (osagent) with CosNaming service, which is shipped with IBM object
request broker transient naming server (tnsnameserver). The major
difference between these two is that osagent is a dynamic naming service
(object request broker client can automatically find the object request broker
service) and tnsnameserver is static naming service.
򐂰 The major new object request broker features listed above are covered in
detail in Chapter 5, “Technical impact of major design changes” on page 67 of
this redbook and must be thoroughly reviewed prior to migration.
OS level and
DB2 version WebSphere
ORB Agent
and XML
AIX 4.3.3 patch 9
UDB 7.2FP6 5.2 Inprise
4.2.1 AIX 4.3.3 patch 9
UDB 8.1FP2 5.3.01 3.2 Inprise
VisiBroker and
Xerces 1.4.3
4.2.2 AIX 5.1 ML 4
AIX 5.2 ML 1
UDB 8.1FP2 5.3.02 CSD 5 3.2 IBM ORB and
Xerces 1.4.3
4.2.3 AIX 5.1 ML 5
AIX 5.2 ML 2
UDB 8.1FP5 5.3.02 CSD 7 3.3 IBM ORB and
XML4J 4.2.3

Get WebSphere InterChange Server Migration Scenarios now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.