You can import applications created in Rational® Application Developer V.6.x or
V.7.0.0.x into your current workspace.
Before you begin
Before you migrate your application, open a new workspace.
Procedure
- In a clean workspace, click .
- On the Import page, in the Select an import
source field, select , and click Next.
- On the Project Imports page, in the From archive
file field, click Browse, and navigate
to your project that you want to migrate. Select the projects that
you want to include in your migration. You do not need to select the
J2C Tool plugin Import Service:
- Click Finish, and the workshop migration
wizard launches automatically.
- On the Rational Desktop Migration page, click Next.
- On the Workspace projects which need migration page, select
the projects that you want to include in your migration, and click Next.
- On the Migration Project Resources page, review the summary
of tasks and click Next.
- On the Complete Migration Startup page, Click Finish.
- Once the migration is complete, you can review the process
in the Migration Results view. If you don't see the Migration Results
view, select , and click Okay.
- Post-Migration steps: If your migrated project was
created in a version of Rational Application Developer earlier than 6.0.1.5, you have to perform
some manual steps to the generated J2C Java™ bean interface and implementation code.
- Open the Problems view by selecting , and click Okay.
- If you see this Error in the Problems view Unhandled exception type ResourceException, then follow
these steps to resolve the problem:
- Open your J2C Java Bean
interface and implementation file, find the Error icon: Right-click the error icon, and select Quick Fix: Select Add throws declaration to add a throws javax.resource.ResourceException statement to all the business method declarations:
- Use Quick Fix to add the import statement import javax.resource.ResourceException;, if it is missing.
- If you see this Error in the Problems view CHKJ3013E: Duplicate 'resource-ref' element named <variable-name> in the ejb-jar.xml, then follow these steps to resolve the problem:
- Select .
- Close and restart the workspace.