428 WebSphere InterChange Server Migration Scenarios
AIX: in-place database migration
This section provides the steps required to perform an in-place database
migration of WebSphere InterChange Server 4.1.1.9 to WebSphere InterChange
Server 4.3.0. on AIX.
Pre-migration steps
Table A-7 details the pre-migration steps for an in-place database migration of
WebSphere InterChange Server 4.1.1 on AIX.
Table A-7 AIX in-place database pre-migration steps for 4.1.1
Migration steps
Table A-8 details the migration steps for an in-place database migration of
WebSphere InterChange Server 4.1.1 on AIX.
Table A-8 AIX in-place database migration steps for 4.1.1
2. Install Adapter Framework 2.6 and upgrade adapters.
3. Update any Server Access Interface clients.
4. Test the WebSphere InterChange Server.
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 WebSphere InterChange Server.
c. Back up the database.
d. Shut down the Inprise VisiBroker Agent.
e. Back up the WebSphere MQ environment.
1. Upgrade the Database System.
Appendix A. WebSphere InterChange Server migration checklist 429
a. Upgrade Database.
b. Check the database parameters.
c. For DB2 test the c-compiler.
d. For DB2 Catalog database with Loopback Node.
e. Restart database.
2. Upgrade WebSphere MQ.
3. Installation.
a. Install WebSphere InterChange Server 4.3.
b. Configure the WebSphere InterChange Server with
ICSConfig.sh.
4. 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.
e. Modify and verify the environment variables and make sure
the latest settings are in effect.
f. Install the Toolset on a supported Windows client.
5. Starting the new Server.
a. Start WebSphere MQ Queue Manager and Listener.
b. Start Database.
c. Start the Persistent Name Server.
d. Run the DDL script in Appendix B, “Sample code” on
page 465.
6. Start the WebSphere InterChange Server in design mode.
430 WebSphere InterChange Server Migration Scenarios
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 the maps and templates in the integration component
libraries.
12.Examine/Modify Adapters that use 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 any of the other 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.
14.Create a new user project and populate it the component from
the integration component library.
15.Resolve any collaborations that are in transactional status.
16.Delete the repository.
17.Deploy the modified components.
a. Perform compilation on 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.

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.