IBM SG24-6320-00 manual Migrating custom EJBs, Summary

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

7.4.3 Summary

At this point, you should be at the following stage of migration:

You have installed and configured the new WebSphere Commerce test environment in WebSphere Studio Application Developer V5.1.1.

Your development WebSphere Commerce instance is migrated to the new test environment in WebSphere Studio Application Developer V5.1.1.

Your existing development database has been migrated from DB2 Universal Database V7.2.5 to DB2 Universal Database V8.1.

Your development database has been migrated to the new schema for

WebSphere Commerce V5.6.

Any encrypted data will be re-encrypted using the new algorithm and new merchant key (if required).

Before your store will work correctly in the new development environment, there are several steps that must be taken to modify your custom code. These steps are explained in the following chapter. If you have any custom EJBs you will now need to migrate these to WebSphere Studio Application Developer V5.1.1.

Important: If you dropped any foreign key constraints before performing the migration, you must remember to recreate these before testing your migrated store.

7.5 Migrating custom EJBs

The EJBs in WebSphere Commerce Suite V5.1 complied to the EJB 1.0 standard. In WebSphere Commerce V5.6 EJBs should conform to the EJB 1.1 standard. While WebSphere Application Server V5.0.2 is capable of running EJBs at either level, it is not recommended that EJBs of different specifications are mixed. As a result, any existing EJBs that you may have must be migrated to the new specification.

118Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide