IBM SG24-6320-00 manual File name of the log will be in the following format

Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm

Event: Starting to execute command com.ibm.commerce.migration.wcim.command.WCIMMigrateStudioCommand Event: Method: migrateDevEnv

Enter the previous WebSphere Commerce home directory: D:\WebSphere\WCS

Enter the home directory of VisualAge for Java: D:\WebSphere\VAJava

Enter the name of the custom code JAR file: D:\MyStoreCommands.jar

Event: MethodId: updateProductXML

Event: MethodId: updateProductXML

Event: MethodId: setNewVersionsEditions

Event: MethodId: invokeAnt - executing ant task: MigrateStudioInstanceBoth

Event: MethodId: setOldVersionsEditions

Event: MethodId: migrateConfigs - migrating demo.xml

Event: MethodId: getInstMigrateXmls - getting XML files to update instance.xml

Event: MethodId: getInstanceUpdatePath

Event: WCIM has successfully completed command com.ibm.commerce.migration.wcim.command.WCIMMigrateStudioCommand Event: WCIM has completed the job(s) assigned successfully.

When the WCIM tool has completed, you should check the WCIM logs located in the following directory:

<wctoolkit_home>\temp\logs

The file name of the log will be in the following format:

wcim.migration.toolkit.instancename.51.YYYY.MM.DD.HH.MM.SS.ssssss.log

Where instancename is the name of the instance and YYYY.MM.DD.HH.MM.SS.ssssss is a timestamp.

When you have validated that the migration was successful, you should open WebSphere Studio Application Developer V5.1.1 and refresh your workspace in order to make the new imported code visible.

To start WebSphere Studio Application Developer V5.1.1 with the WebSphere Commerce V5.6 Toolkit, select Start -> Programs -> IBM WebSphere

Commerce Developer Professional Edition -> WebSphere Commerce development environment.

To refresh the WebSphereCommerceServerExtensionsLogic project, right-click the project and select Refresh.

Chapter 7. Migrating the development environment 115