420 WebSphere InterChange Server Migration Scenarios
Migration checklist for WebSphere ICS 4.1.1
This section lists the steps that are required to migrate WebSphere InterChange
Server 4.1.1.9 to WebSphere InterChange Server 4.3.0. It is divided into sections
for Windows and AIX and for in-place database migration and for without in-place
database migration.
Windows: in-place database migration
This section provides the steps necessary to perform an in-place database
migration of WebSphere InterChange Server 4.1.1.9 to WebSphere InterChange
Server 4.3.0 on Windows.
Pre-migration steps
Table A-1 details the pre-migration steps for an in-place database migration of
WebSphere InterChange Server 4.1.1 on Windows.
Table A-1 Windows in-place database pre-migration steps for 4.1.1
1. Put the environment in a quiescent state.
a. Stop all adapters from polling.
b. Resolve transactional status of transactional collaborations.
c. Resubmit failed events or discard the events.
d. Stop all collaborations.
2. Backing Up and Shutting Down Components.
a. Back up the current InterChange Server repository using the
repos_copy utility.
b. Shut down the InterChange Server.
c. Back up the database.
d. Shut down the VisiBroker Service.
e. Back up WebSphere MQ environment.
f. Save environment settings.
Appendix A. WebSphere InterChange Server migration checklist 421
Migration steps
Table A-2 details the migration steps for an in-place database migration of
WebSphere InterChange Server 4.1.1 on Windows.
Table A-2 Windows in-place database migration steps for 4.1.1
1. Preparing the Database System.
a. Upgrade Database.
b. Check the database parameters.
c. For DB2 test the c-compiler.
d. Restart database.
2. Upgrade WebSphere MQ.
3. Uninstall Software.
a. Uninstall Windows services (if any are present for example:
WebSphere Business Integration Adapters, WebSphere
InterChange Server).
b. Uninstall the Object Request Broker (VisiBroker).
c. Uninstall Java Development Kit (JDK) if this is not required for
other products.
d. Uninstall WebSphere InterChange Server.
4. Install and Configuration.
a. Install WebSphere InterChange Server 4.3.
b. Configure the WebSphere InterChange Server with
ICSConfig.bat.
5. Preparing the environment for the first WebSphere InterChange
Server startup.
a. Copy DLMs and collaboration directories to new installation.
b. Apply any custom configuration settings to
%CROSSWORLDS%/InterchangeSystem.cfg.
c. Modify any custom startup or other scripts that reference
VisiBroker ORB.
d. Copy external jar files and include them in the WebSphere
InterChange Server CLASSPATH.
422 WebSphere InterChange Server Migration Scenarios
e. Modify and verify environment variables: CROSSWORLDS,
MQ_LIB, PATH.
6. Start the new Server.
a. Start WebSphere MQ Queue Manager and Listener.
b. Start Database.
c. Start the PeristentNameServer.bat.
d. Run the DDL script in Appendix B, “Sample code” on
page 465.
e. Start the WebSphere InterChange Server in design mode.
7. Create a new integration component library and import the
components from the server.
8. Include custom .jar files in the Toolset CLASSPATH.
9. Set the compliance of the compiler to Java 1.4.
10.Examine custom code in maps or collaboration templates for
Java 1.4 compliance.
11.Compile all maps and templates in the integration component
libraries.
12.Modify Adapters and queues for JMS delivery transport.
a. Examine/Modify queue names in Connector Configurator.
b. Create new queues in the queue manager.
c. Save the configuration file to the project, and save a copy to
file.
13.Reconfigure components that require modification.
a. Reconfigure or create any connection pools and relationship
definitions.
b. Reconfigure any custom code that uses Server Access
Interface.
c. Reconfigure any custom code or property that references a
specific queue manager, queue name, or file location that has
changed.
Appendix A. WebSphere InterChange Server migration checklist 423
Post-migration steps
Table A-3 details the post-migration steps for an in-place database migration of
WebSphere InterChange Server 4.1.1 on Windows.
Table A-3 Windows in-place database post-migration steps for 4.1.1
14.Create a new user project and populate it the component from
the integration component library.
15.Resolve any collaborations that are transactional status.
16.Delete the repository.
17.Deploy the user project.
a. Perform compilation on WebSphere InterChange Server
machine.
b. (Optional) Select Create Schema option if the relationship
location has changed or is not working.
c. Restart the WebSphere InterChange Server if prompted.
1. Security.
a. Create the admin user.
b. Use previous password.
c. Assign to Administrator role.
2. Update any Server Access Interface clients.
3. Install Adapter Framework 2.6 and upgrade adapters.
4. Test the WebSphere InterChange Server.

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.