Migrate > Migrating WebSphere Commerce Developer > Migrating custom assets
|
| |
|
|
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.
Before migrating EJB projects, ensure that the EJB projects function correctly in the previous version of WebSphere Commerce, and can be deployed successfully. This gives you a baseline of successful testing before you proceed with migrating the custom code.
Migrate independent EJB projects
Custom EJB beans from WebSphere Commerce v5.6.1 or 6.0 must be exported as a EJB JAR file and imported as a EJB jar into the WebSphere Commerce v7.0 J2EE perspective > EJB Projects > WebSphereCommerceServerExtensionsData , project or into the own project. After exporting and importing, the EJB beans can be migrated.- Migrate dependent EJB projects
If you have customized ready to use EJBs in a previous WebSphere Commerce release, you cannot import them into the new workspace as they might be modified in the new WebSphere Commerce version. You must customize the new version of the EJBs again. - Update the DataSource value
In WebSphere Commerce releases prior to WebSphere Commerce 6.0, a global default DataSource reference was defined. All independent EJB projects that did not explicitly define a DataSource would use the default DataSource. In WebSphere Commerce 6.0 this default value is not set and all EJB projects must now define a specific DataSource. - Migrate EJB projects to use optimistic locking
Use the optimistic locking migration plug-in to enable optimistic locking in an EJB project.