![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/0/59/05952034-8c0c-4662-beae-aecaece40d19/05952034-8c0c-4662-beae-aecaece40d19-bgdf.png)
Chapter 11. Migrating WebSphere Commerce components 205
Draft Document for Review July 28, 2004 7:33 pm 6320ch_migrating.fm
– The WebSphere Application Server home directory <was35_home>.
– The WebSphere Application Server administration node name.
– The WebSphere Application Server node name.
– Whether the IBM HTTP Server is installed locally or not.
– The IBM HTTP Server home directory <ihs_home>.
On the WebSphere Commerce Suite V5.1 system, run the WCIM tool with the
following parameters to backup your existing instance:
wcim.bat -component wc -from 51 -backup remote -instance <instance_name>
from the following directory:
<wc51_home>\temp\bin\
In our example:
wcim.bat -component wc -from 51 -backup remote -instance demo
– Enter the previous WebSphere Application Server home directory:
D:\WebSphere\AppServer
– Enter the previous WebSphere Application Server administration node
name:
wcs51
– Enter the previous WebSphere Application Server node name:
wcs51
– Is a previous IBM HTTP Server installed locally? [DEFAULT yes]
yes
– Enter the previous IBM HTTP Server home directory:
D:\WebSphere\HTTP
Running the above command will produce the following file:
<wc51_home>\temp\instance_backup.zip
The instance_backup.zip file contains a single file,
backupwc_51_<instance name>.zip, which is used to deploy the instance
on WebSphere Commerce V5.6.
5. Transfer and unpack the backup file
Note: all the information required for this step is derived from the
WebSphere Commerce Suite V5.1 system.