Filter
Top Products
Chapter 7. Migrating the development environment 123
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_migration.fm
3. Choose a path and file name for the JAR file and enter it into the JAR file text
box.
4. Ensure that DB2 for NT, V7.1 is selected in the target database list.
5. Check the options for .class and .java. Uncheck resource if it is selected.
6. Click Finish to start the export.
Even with small numbers of EJBs, this can take a long time.
Once you have exported all of your EJBs, you should move the JAR file you
exported to either the system containing your installation of WebSphere Studio
Application Developer V5.1.1, or into a directory that is visible from that system.
7.5.6 Import the EJBs into WebSphere Studio Application Developer
The next step is to import your EJB 1.1 JAR file into WebSphere Studio
Application Developer. Once this is done, there will be some code changes to
make before the EJBs will function correctly.
To import the EJB 1.1 JAR file into WebSphere Studio Application Developer
V5.1.1, complete the following steps:
1. If it is not already open, launch WebSphere Studio Application Developer
V5.1.1.
2. Switch to the J2EE Perspective by with clicking it’s icon or clicking Window
-> Open Perspective -> J2EE.
3. Click on the Project Navigator tab.
4. Right-click on the WebSphereCommerceServerExtensionsData project
and select Import... from the menu.
The Import window will appear.
5. Select EJB JAR file from the list of sources and click Next.
6. Next to the EJB JAR file list, click Browse... and select the EJB 1.1 JAR file
that you exported in the previous section.
7. Click on the EJB project list and select
WebSphereCommerceServerExtensionsData from the list and click Next.
8. Ensure that Import all enterprise beans and files is selected and click
Finish.
When you have imported all your EJBs there are still several more steps you
need to take for the EJBs to work properly. At this point, you will notice there are
errors and warnings in your EJB code. These errors will be fixed when you follow
the post migration steps in 8.2.6, “Configuration and code changes for migrated
EJBs” on page 144.