Overview of scripts called during application migration

Migrating the WebSphere Commerce application involves the following steps, which can be seen in the file WC_installdir/migration/xml/build.xml:

<target name="-migration" depends="-setprops">
    <antcall target="-checkdb" />
		<antcall target="-migratedb" />
		<antcall target="-backupapp" />
		<antcall target="-migrateapp" />
		<!-- config ws -> config app-->
		<antcall target="-configapp" />
		<antcall target="-installapp" />
</target>

where

• -migratedb is for the database migration task
• -backupapp is for application backup task
• -migrateapp is for application migration task,
• -configapp and -installapp are for application configuration task

For more details about -migrateapp, refer to the file WC_installdir/migration/xml/app.xml. The main tasks called by app.xml are:

1. Creating the V7 profile
2. Migrating the instance
3. Running WASPostUpgradeWithoutApp
4. Running SyncNode if the environment is clustered
5. Copying the V7 EAR template into a temporary directory, which is included in the target migrated in the file WC_installdir/migration/xml/features/BASE/app/561/build.xml

For more details about -configapp, refer to the file WC_installdir/migration/xml/ws.xml. The main tasks called by configapp are:

1. Updating the related WebSphere Application Server xml file
2. Replacing wc-server.xml with the migrated WebSphere Commerce instance xml file.

More details about-installapp are also in the file WC_installdir/migration/xml/ws.xml. The main tasks called by installapp are:

1. Make profile configuration changes, such as CreateVirtualHosts, modifyVirtualHosts, modifyDataSource, remapAppServer.
2. Deploying the migrated EAR to the WebSphere Commerce V7 server
3. Rebuilding the cluster
4. Regenerating the Web server plugin xml file