Draft Document for Review July 28, 2004 7:33 pm

6320ch_DEV_before_migration.fm

“Migrating custom EJBs” on page 118 and 8.2.6, “Configuration and code changes for migrated EJBs” on page 144.

Overview

VisualAge for Java provided a source control feature through the concept of a repository. This feature allowed typical source control functionality such as restoring previous editions of code and marking releases etc.

VisualAge for Java also has the concept of projects that are used to logically group code for applications or components. These projects, and the packages and files within them, could be versioned in the repository.

WebSphere Studio Application Developer V5.1.1 does not include any source code management features as standard. However, various plug-ins are widely available to allow the use of external systems, such as CVS.

As the migration script cannot cater for all possible source control solutions under WebSphere Studio Application Developer V5.1.1, it does not migrate all historic versions of code from the VisualAge repository. Only the code which is currently available in the workbench will be ported.

Tip: If you need to migrate all versions of your code to your new environment, you can do this by manually exporting the source code for each edition from VisualAge for Java, importing this into WebSphere Studio Application Developer, and then commit the imported source code to the new source control management system.

As this is a very tedious and lengthy process, we recommend that you keep at least one installation of VisualAge available to access previous versions of code and only export the latest version to WebSphere Studio Application Developer V5.1.1.

Exporting the Java code

The WebSphere Commerce V5.6 migration script requires that all of the custom code source that is to be migrated must be packed in a single JAR file. You will be prompted to enter the location of this JAR when the script is run.

In order to export your code, locate the projects in VisualAge where it resides and complete the following steps:

1.With the Projects tab selected, select all of the projects that contain your custom code.

2.Right-click on one of these selected projects and click Export... from the menu.

Chapter 6. Pre-migration steps 101

Page 119
Image 119
IBM SG24-6320-00 manual Overview, Exporting the Java code