IBM Support

Migrating to Rational Application Developer v7.5

Product Documentation


Abstract

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.5.

Content

Tab navigation





Rational Application Developer
Product Lifecycle
Database Tools
EJB Deployment Code Generation
WebSphere Test Environment and WebSphere Application Server Integration
Java EE Specification Migration
APARs and Fixes
Change History



Rational Application Developer

Migration Support

The Rational Application Developer v7.5 workspace and project migration wizard supports migrating content created in either Rational Application Developer v6.0.x or v7.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.
  • If the migration is being done for content from WebSphere Studio Application Developer v5.1 to Rational Application Developer v7.5 then the supported migration path is a two step process to get to v7.5: First migrate the workspace to Rational Application Developer v7.0 and then to v7.5.

See the Compatibility with version 7.0.x and version 6.0.x article for more information on the compatibility of workspaces and projects between v6.0, v7.0, and v7.5.

After the migration is complete it is recommended to remove obsolete metadata from migrated projects to ensure that additional migration activities do not occur while using Rational Application Developer v7.5. 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 v7.0 environment.

Migration Information

Rational Application Developer v7.5 Migration overview
An overview of the migration to Rational Application Developer v7.5.

Rational Application Developer v7.x Migration validation
A tool for validating the structure and displaying potential errors found in migrated J2EE projects.

Migrating workspaces and projects from version 6.0.x or version 7.0.x
Information on migrating workspace and project contents from Rational Application Developer v6.0 or v7.0.

Rational Application Developer v7.5 Information Center
The Rational Application Developer v7.5 product documentation

Product Lifecycle

Rational Application Developer for WebSphere Software Product support lifecycle
Product lifecycle information for Rational Application Developer for WebSphere Software v7.5.
Database Tools

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. Reference the following article title Migrating database definitions for information on how to migrate these files.

For the list of Database vendor and versions that Rational Application Developer v7.5 supports see the following page:

Compatible software for Rational Application Developer version 7.5
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 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:
  1. 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.

    or

  2. 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 v6.0

If an EJB project is targeting a WebSphere Application Server v6.0 runtime then the Map.mapxmi file is created to use the database definition model (dbm file) as expected; However, in addition a Map.v6mapxmi file is also created with a Data definition model that is compatible with Rational Application Developer v6.0. WebSphere Application Server EJBDeploy is based on Rational Application Developer v6.0 technology so these additional files will be used by the server copy of EJBDeploy for code generation, while Rational Application Developer will use the Map.mapxmi for EJB deployment code generation. Only the Map.mapxmi file should be modified within Rational Application Developer v7.5 and it will automatically synchronize the changes to the Map.v6mapxmi file and its data definition files upon saving the file.

Database Support

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.5 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
WebSphere Application Server v7.0

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.5 provides support for the following WebSphere Application Server runtime environments:
  • WebSphere Application Server v6.0
  • WebSphere Application Server v6.1
  • WebSphere Application Server v7.0
  • WebSphere Portal Server v6.0
  • WebSphere Portal Server v6.1
  • WebSphere Portal Server v6.1 on WAS v7

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.

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 any 1.2, 1.3 or 1.4 J2EE specification level to either the 1.3, 1.4, or the 5.0 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.

Important information on the Java EE migration wizard to the 5.0 specification level:
  • The Java EE Migration wizard added support for the 5.0 specification level in Rational Application Developer Version 7.5.3.
  • The Java EE Migration wizard does not modify any source code contained within any of the projects that are migrated. It does not convert any deployment descriptor values into Java EE anotations within source code.
  • The Java EE Migration wizard does not support migrating Entity beans in a EJB 1.x or 2.x module to an EJB 3.0 module. Manual migration will be required if there is a need to convert any existing 1.1 or 2.x Entity beans to use the Java Persistence API.
  • If there is no need to migrate EJB 1.x or 2.x modules to 3.0 then it is recommended to keep existing EJB modules as-is and perform new development using the EJB 3.0 and JPA functionality as necessary
  • EJB 3.0 overview
  • Differences between EJB 3.0 and EJB 2.1
  • Container-Managed Persistence (CMP) and Bean-Managed Persistence (BMP) 1.x or 2.x Entity beans are not supported in EJB 3.0 modules

APARs and Fixes

Fixed APAR list for IBM Rational Application Developer for WebSphere Software, version 7.5
A comprehensive list of recommended, generally available (GA) fixes for Rational Application Developer v7.5.
Change history
DateDescription
28 Jul 2009Original draft published.

[{"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Migration","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB15","label":"Integration"}}]

Document Information

Modified date:
04 February 2020

UID

swg27016268