This documentation provides instructions for migrating from WebSphere® Studio
Application Developer V5.1.x to Rational® Application
Developer V6.0.
Additional information can be found on the following topics:
This migration documentation is also available
in an HTML version (migrate.html file) which is located at the root of the
first product CD.
Refer to www.ibm.com/developerworks/rational for
updated documentation.
For information on migrating from prior versions
of WebSphere Studio
to v5.x or migrating from VisualAge® for Java™ to WebSphere Studio, go to www.ibm.com/software/awdtools/studioappdev/support/ and
search for "migration guide".
To migrate from WebSphere Studio V5.1.x:
- Before installing, read about compatibility
with Eclipse V2.x and WebSphere Studio V5.1.x. Note that
backward compatibility is not supported for portlet application projects migrated
from Portal Toolkit V5.0.2.2 with WebSphere Studio V5.1.2.
- Back up your WebSphere Studio V5.1.x workspace.
- Install Rational Application
Developer.
Refer to the Installation Guide (install.html file) which is available
at the root of the first product CD.
- Recommended: By default, the first time you start Rational Application
Developer,
you are prompted to confirm that you want to use a workspace called rationalsdp6.0\workspace.
That is, the Workspace Launcher dialog box points to a directory that is not
your WebSphere Studio
workspace. To explore the new environment before migrating your old workspace,
accept the default or specify some other new directory name when you start Rational Application
Developer. You might do this,
for example, so you can create one or two test projects, read about what's
new (), do some of the new tutorials (), or experiment with
some of the new samples ().
- Migrate your projects to V6.0. Projects created in WebSphere Studio
V5.1.x can be automatically migrated to V6.0 as follows:
- Migrating a workspace: When you are ready to migrate
your V5.1.x workspace for good, start Rational Application
Developer with
your old workspace. A progress indicator confirms that your projects are being
automatically migrated.
Notes: During workspace migration
a Problems dialog box opens with the message Could not restore
workbench layout. Reason: Problems occurred restoring workbench. The
error messages have no impact on the successful migration of the workspace.
Note the name of perspective that could not be restored by clicking the Details button
in the error dialog box, then click OK to close the
dialog box.
To restore the perspective:
- Close the perspective by selecting
- Reopen the perspective by selecting .
Note: For Enterprise Generation Language (EGL) projects that used
EGL Web perspective in WebSphere Studio V5.1.2: this perspective
has been removed in
Rational Application
Developer V6.0.
All EGL projects are safely migrated without this perspective in
Rational Application
Developer V6.0.
Do the following if you used the EGL Web perspective:
- Close the EGL Web perspective.
- Enable EGL capabilities in the Preferences (). Refer to the online help
for details on enabling EGL capabilities.
- Select and choose the Web perspective.
- Migrating projects loaded from a SCM (source code management)
system: Projects from WebSphere Studio 5.1.x that exist in a SCM
system are automatically migrated to V6.0 when they are loaded into Rational Application
Developer.
- Migrating projects imported using Project Interchange: Projects
exported from WebSphere Studio V5.1.2 or V5.1.1 and imported into Rational Application
Developer V6.0 using the Project
Interchange feature are automatically migrated to V6.0. The Project
Interchange feature was available in WebSphere Studio V5.1.2 and was an optional
plug-in for V5.1.1.
Notes:- If you used the Portal Toolkit V5.0.2.2 with WebSphere Studio
V5.1.2 to develop portlet projects, your workspace will be automatically
migrated to be compatible with Rational Application
Developer.
See Migrating to the portal tools in Rational Application Developer V6.0 for more information.
- For each V5.1.x project migrated to V6.0, the migration program automatically
adds a .compatibility file to the project folder in V6.0. This file is used
for the purpose of backward compatibility with WebSphere Studio V5.1.x. Do not edit or delete
this file. Refer to the section on compatibility
with WebSphere Studio
V5.1.x for more information.
Important:- If there are debug launch configurations associated with the workspace
you are migrating, you should note that some launch configuration will not
migrate automatically. For information on how to restore launch configurations
to a migrated workspace, refer to Debugger changes in V6.0.
- If you used the XSLT debugger or EGL debugger on projects in your migrated
workspace, you will need to change the Java runtime environment (JRE) that is
installed with Rational Application
Developer V6.0.
Refer to Debugger changes in V6.0 for details on how to
make this change.
- If you have programs developed using the Enterprise Generation Language
that were migrated to V6.0, you should note that there are new reserved words
for EGL in version 6.0. If you use these words as variable or part names you
will need to change them. Refer to EGL reserved words in V6.0
- The DB2® Net JDBC Driver is not supported in Rational Application
Developer V6.0.
If you created JDBC connections using the DB2 Net JDBC Driver, you will not be able
to reconnect in Rational Application
Developer V6.0.
You will need to change the connection to use one of the supported JDBC drivers.
Refer to the online help for more information on the JDBC drivers supported
in V6.0.
- If you have Web or XML file content migrated from WebSphere Studio
Application Developer V5.1.x
that used the Shift_JIS character set and included vendor selected characters,
you must specify the Windows-31J character set instead.
- If you installed any vendor plug-ins with WebSphere Studio
Application Developer V5.1.x,
you need to get the corresponding plug-ins for V6.0 and reinstall them.
- If you installed any back-level WebSphere V5.x unit
test environments when you installed Rational Application
Developer,
and if you use the embedded messaging service, upgrade it by installing the
version provided with Rational Application
Developer.
Refer to the installation guide for details on installing the embedded
messaging service.
- If you use features that require Agent Controller, upgrade it by
installing the version provided with Rational Application
Developer.
For details, refer to the installation guide.
- To migrate from VisualAge Generator, consult the VisualAge Generator
to Enterprise Generation Language (EGL) Migration Guide that is available
in PDF format in the "Installing and migrating" section of the online help
under the help topic "Accessing the VisualAge Generator to EGL Migration Guide."
The most recent copy can be obtained from http://www.ibm.com/developerworks/rational/library/egldoc.html.