Migrate > Migrating WebSphere Commerce Developer
|
| |
|
|
Migrate custom assets
The second phase of the migration process is the migration of custom assets.
After a store has been published, it is considered to be custom code.
Migrate non-EJB projects
Complete the tasks listed on this page for the non-EJB projects you have in the workspace. Published stores, SDOs, Management Center customizations, commands, and databeans are all considered non-EJB projects.- Migrate EJB projects
There are two types of EJB projects you can migrate: Independent EJB projects. These are original created projects. Dependant EJB projects. These projects are built on top of existing projects. - Copy the encrypted passwords for the WebSphere Commerce tools
To log on to the WebSphere Commerce Accelerator, Administration Console, or Organization Administration Console after migrating to WebSphere Commerce Developer v7.0, modify a configuration file to include the old encrypted passwords.
Previous topic:
Migrate the WebSphere Commerce Developer database
Next topic:
Verify the migrated WebSphere Commerce Developer application