A focused compilation of links to documents and resources to help you plan and perform your migration to IBM Rational Application Developer for WebSphere Software v7.0.
|Rational Application Developer|
The Rational Application Developer v7.0 automatic workspace and project migration supports migrating content created in either WebSphere Studio Application Developer v5.1.2 and Rational Application Developer v6.0.x. Refer to the Migration Support information found on the Overview page for more information on the migration support available or alternatives if the recommended migration support path is not possible. It is strongly recommended to apply the Rational Application Developer v18.104.22.168 fix pack at a minimum before migrating any content to Rational Application Developer v7.0 as there were many migration related fixes in this fix pack release.
See the Compatibility with v6.0.x and v5.1.2 article for more information on the compatibility of workspaces and projects between v5.1.2, v6.0, and v7.0.
After the migration is complete it is recommended to disable compatibility with earlier product versions to ensure that additional migration activities do not occur while using Rational Application Developer v7.0. As mentioned in this article, this step should only be followed if there you do not intent to have these projects used in a Rational Application Developer v6.0 or WebSphere Studio Application Developer v5.1.2 environment.
Migrating workspaces and projects from WebSphere Studio Application Developer v5.1
Information on migrating workspace and project contents from WebSphere Studio Application Developer v5.1.
Migrating workspaces and projects from Rational Application Developer v6.0
Information on migrating workspace and project contents from Rational Application Developer v6.0.
Rational Application Developer v7.x Migration validation
A tool for validating the structure and displaying potential errors found in migrated J2EE projects.
Rational Application Developer v7.0 Information Center
The Rational Application Developer product documentation
Rational Application Developer for WebSphere Software Product support lifecycle
Product lifecycle information for Rational Application Developer for WebSphere Software v7.0.
The Database tooling provides the ability to pull in a representation of the physical database and store it within a project. In WebSphere Studio Application Developer v5.1 and Rational Application Developer v6.0 this information was stored using individual files for each table (*.tblxmi), schema (*.schxmi), and database (*.dbxmi). In Rational Application Developer v7.0 and v7.5 all of this information is stored in one file with a file extension of *.dbm. The migration of database definitions except for ones in an EJB project used by the CMP Mapping functionality are not migrated automatically.
|EJB Deployment Code Generation|
EJB CMP beans rely heavily on the EJB Mapping functionality which maps a bean field to a database column. The EJB Mapping functionality uses the Database Tools for providing a representation of the physical database to allow mapping a CMP bean to a table or view column. If an EJB project is being migrated from either WebSphere Studio Application Developer v5.1 or Rational Application Developer v6.0 then the database metadata will be migrated to the new format. If the CMP Mapping editor is unable to open the mapping file or the 'Prepare for Deployment' functionality fails to generate the EJB deployment code after migrating the EJB project then either the mapping file or database model failed to migrate successfully. In this situation the error messages will be written to either the workspace .log file or the SQLModelMigration.log file found in the directory containing the database definition; To resolve this problem you can either:
- Create a new CMP EJB backend. This option is typically only a reasonable path to follow if a CMP back-end was created in a top-down fashion and neither the Database or CMP mapping information was modified from it's original structure.
- Contact IBM Rational Application Developer support and ask for information as to why the migration failed. In order for the support organization to diagnose this problem they will need a binary copy of the EJB project before migration occurred (source code is not required for replicating CMP backend migration problems).
WebSphere Application Server v5.1 or 6.0
If an EJB project is targeting a WebSphere Application Server v5.1 or 6.0 runtime then the Map.mapxmi file is created to use the database definition model (dbm file) as expected; However, if the resulting EJB-JAR is used by the WebSphere Application Server v5.1 or v6.0 EJBDeploy code generation tool then the process will fail as these versions of the EJBDeploy tool do not understand the new database format. WebSphere Application Server v5.1 EJBDeploy was built using WebSphere Studio Application Developer v5.1 technology while WebSphere Application Server v6.0 EJBDeploy was built using Rational Application Developer v6.0 technology. In both of these EJBDeploy versions the expected database format is the older file format mention in the Database Tools section (individual files for each table (*.tblxmi), schema (*.schxmi), and database (*.dbxmi)). Therefore, if you are using Rational Application Developer v7.0 and targeting a WebSphere Application Server v5.1 or v6.0 runtime and will be using the EJBDeploy code generation tool provided by the WebSphere Application Server product, then it is strongly recommended that the information in the following article is reviewed:
PK57362: EJBDeploy v6.1 for WebSphere Application Server v5.1/v6.0
If using Rational Application Developer v7.0 is not a requirement for your organization then it is recommended to upgrade to v7.5 as support has been added in the product to automatically generate a backend Map and database definition that is compatible with the latest fixpack release of WebSphere Application Server v6.0 EJBDeploy. Rational Application Developer v7.5 does not provide support for WebSphere Application Server v5.1 so this information is only applicable when targeting WebSphere Application Server v6.0.
The EJBDeploy tool that is invoked on EJB projects as a result of running the 'Prepare for Deployment' is tied very tightly to the targeted WebSphere Application Server of the EJB project. It is important to remember that the Rational Application Developer database tooling may provide support a set of database vendors and versions; However, each version of WebSphere Application Server may only support a subset of those vendors and versions. When migrating Rational Application Developer versions and / or WebSphere Application Server versions it is important to ensure that your Database is supported in both products. For information on the databases that Rational Application Developer v7.0 supports see the information in the Database Tooling section. For information on the supported database that WebSphere Application Server supports see the following:
WebSphere Application Server v6.0
WebSphere Application Server v6.1
If a scenario is found where the targeted WebSphere Application Server supports a Database vendor and/or version that Rational Application Developer does not support then please contact IBM Rational Application Developer support for assistance on how to resolve generating the deployment code for this Database vendor and/or version.
|WebSphere Test Environment and WebSphere Application Server Integration|
Rational Application Developer v7.0 provides support for the following WebSphere Application Server and WebSphere Portal runtime environments:
- WebSphere Application Server v5.1
- WebSphere Application Server v6.0
- WebSphere Application Server v6.1
- WebSphere Portal Server v5.1
- WebSphere Portal Server v6.0 and v6.0.1
- WebSphere Portal Server v6.1 (only for JSR 168 portlet API)
Migration information for any server related information can be found in the WebSphere Test Environment and WebSphere Application Server Integration section of the Overview tab.
|Workspace Migration FAQ|
WebSphere Application Developer v5.1.2 and Rational Application Developer v6 to v7 Migration problems FAQ
A collection of frequently asked questions compiled by the Rational Application Developer support organization.
|Java EE Specification Migration|
Java EE Migration is as separate task from the project and workspace migration functionality. For more information on Java EE migration see the following:
Java EE Migration Wizard
The Java™ EE Migration Wizard supports migrating from either the 1.2 or 1.3 J2EE specification level to either the 1.3 or 1.4 J2EE specification level for any of the Java EE module types. For more information on specific module types, see the following:
- Web Project Migration (Servlet level 2.2 to Servlet level 2.4)
Additional information about converting Web projects containing 2.2 level Servlets to 2.4 when using the Java EE Migration Wizard.
- Web Project Migration (Servlet level 2.3 to Servlet level 2.4)
Additional information about converting Web projects containing 2.3 level Servlets to 2.4 when using the Java EE Migration Wizard.
- J2C Project Migration
Additional information about J2C project migration when using the Java EE Migration Wizard.
- Web Service Migration
Additional information about Web Service migration when using the Java EE Migration Wizard.
- EJB 1.x to 2.x Project Migration
Additional information about migrating an EJB 1.1 project to 2.x when using the Java EE Migration Wizard.
- EJB 2.0 to 2.1 Project Migration
Additional information about migrating an EJB 2.0 project to 2.1 when using the Java EE Migration Wizard.
|APARs and Fixes|
Fixed APAR list for IBM Rational Application Developer for WebSphere Software version 7.0 fix packs
A comprehensive list of recommended, generally available (GA) fixes for Rational Application Developer v7.0.
|28 Jul 2009||Original draft published.|
04 February 2020