This section describes the migration paths that the J2C migration
tool supports, and outlines the known limitations in the migration tool.
Migration Paths
Table 1. From Version |
To Rational® Studio Application Developer
Version |
Platforms |
Comments |
Visual Age for Java™ 4.0 |
V601 |
Windows®, Linux |
Not supported. |
WebSphere® Studio Application
Developer Integration Edition 5.0.x |
V601 |
Windows, Linux |
Upgrade to V5.1 first and then from WebSphere Studio
Application Developer Integration Edition V5.1 to Rational Application Developer V601 |
WebSphere Studio Application Developer
Integration Edition 5.1 |
V601 |
Windows, Linux |
Direct migration support |
Limitations
The following limitations exist in the J2C migration tools:
- If you are migrating multiple services in a folder and you specify a single
output project, any generated artifacts that have the same name, may overwrite
each other. Save each migrated service under a different project to prevent
this problem.
- If you have both WebSphere V6 server and WebSphere V5.1 server installed
in your RAD environment, and you are migrating multiple services in a folder,
the default server runtime will be Version 5.1 runtime for the created projects.
If you only have WebSphere V6 server installed, then all migrated projects
will be targeted for V6 runtime. In the migrate by folder case, you cannot
specify the server runtime versions. To specify a server runtime version,
you need to create the projects beforehand, specify the server runtime version,
and select these projects to be used for migration.
- The J2C migration tools do not support migration from Visual Age for Java.
- The J2C migration tools support migration to different window platform
supported, for example from Windows 2000 to Windows XP,
or from Windows NT® to Windows 2000.
- The J2C migration tools migration the WSDL files only.