Filter
Top Products
6320ch_DEV_migration.fm Draft Document for Review July 28, 2004 7:33 pm
120 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
Figure 7-2 Process for converting from EJBs from version 1.0 to 1.1
Before you continue, you must have installed and configured a VisualAge for
Java V4.0 system as described in 5.7.1, “Installing VisualAge for Java V4.0” on
page 87.
7.5.2 Export the EJB project from VisualAge for Java V3.5.3
Once you have installed and configured the VisualAge for Java V4.0 remote
node you may continue migrating your custom EJBs, the following step is to
export EJBs from VisualAge for Java V3.5.3. There are several ways you could
export the code, but the simplest method for importing into VisualAge for Java
V4.0 is to export as a VisualAge repository.
In order to export the EJB code, complete the following steps:
1. If not already open, launch VisualAge for Java V3.5.3.
2. Select the Projects tab in the Workbench
3. Select the project that contains custom EJB code from the All Projects pane.
Note: There may be other tools available to migrate EJBs between the two
specification levels that you may consider. However, it is unlikely that these
tools would successfully be able to compile the code and verify it as there are
dependencies on WebSphere Commerce libraries.
VisualAge for Java
V3.5.3
VisualAge for Java
V4.0
WebSphere Studio
Application
Developer V5.1.1
EJB 1.0 Repository
EJB 1.1 JAR