Migrating code artifacts to an assembly tool

You can migrate enterprise archive (EAR), Web archive (WAR), enterprise bean (EJB) JAR, application client JAR, resource adapter archive (RAR) files created with the Application Assembly Tool (AAT), Assembly Toolkit or a different tool to the Application Server Toolkit or Rational Web Developer.

This article assumes you have previously assembled code artifacts that you want to work with in an assembly tool such as the Application Server Toolkit (AST) or Rational Web Developer.

This article also assumes that you have started the assembly tool and have configured the assembly tool for work on Java 2 Platform, Enterprise Edition (J2EE) modules.

You can migrate EAR, WAR, enterprise bean JAR, application client JAR, or RAR projects or files to an assembly tool using the J2EE Migration wizard or by importing the files.

1. Optional: Migrate a project from J2EE 1.2 to 1.3 or 1.4, or from J2EE 1.3 to 1.4, using the J2EE Migration wizard. As part of the migration, you can migrate CMP 1.x beans to CMP 2.x beans. The J2EE Migration wizard is similar to the earconvert batch utility or the File > ConvertEar option of the AAT.

   1. In the Project Explorer view, right-click the enterprise application project (EAR file) you want to migrate.

   2. Click Migrate > J2EE Migration Wizard .

   3. Follow the instructions in the wizard.

2. Import an enterprise application.

3. Import a WAR file.

4. Import an application client file.

5. Import an enterprise bean JAR file.

6. Import a resource adapter RAR file. RAR files are also known as connectors.

What to do next

1. Verify the archive files.

2. Deploy the imported and assembled module or application.

Related concepts
Application assembly and J2EE applications
Enterprise (J2EE) applications
EJB modules

Related reference
Archive support in Version 6.0