6320ax01.fm

Draft Document for Review July 28, 2004 7:33 pm

If you are prompted to restart your computer, do so at this point.

After a few seconds, the First Steps window will appear. Close this window.

Moving the database

In order to move the database to the remote database node it is necessary to backup, transfer and restore the current database into the remote node.

These steps are summarized as follows:

take the production WebSphere Commerce node offline. Ensure the commerce engine is stop and there are no active connections to the commerce database.

stop the commerce server

<WAS_home>\bin\stopServer <WC_server_name>

stop all connections to the database

DB2 terminate

DB2 force application all

backup the current production database

DB2 backup db <WC_db> to <backup_dir>

transfer the backup directory to the remote database node

restore the database from the backup directory

DB2 restore db <WC_db> from <backup_dir>

Connecting to the remote database

In order to access the remote database you just restored first you have to drop the actual production database from the WebSphere Commerce node and then create a connection and an alias for the remote database node.

These steps are summarized as follows:

on the WebSphere Commerce node drop the commerce database

DB2 drop db <WC_db>

create a connection from the WebSphere Commerce node (DB2 client) to the remote TCP/IP node

DB2 catalog tcpip node <node_name> remote <remote_db_hostname> server <server_port>

270Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Page 288
Image 288
IBM SG24-6320-00 manual Moving the database, Connecting to the remote database, Stop all connections to the database