Assemble application modules (known as EAR files) from new or existing J2EE 1.3 modules, including these archives: Web application archives (WAR), resource adapter archives (RAR), enterprise beans (EJB JAR), and application client archives (JAR). This packaging and configuration of code artifacts into application modules or standalone Web modules is necessary for deploying the applications onto the application server.
Before you begin
Gather the code artifacts that you want to package into one or more assembled modules. Code artifacts include these items that you have created and unit tested in your favorite integrated development environment:Steps for this task
The Application Assembly Tool (AAT) has an option for migrating J2EE 1.2 application modules to J2EE 1.3. The J2EE 1.2 module is kept intact, with a new 1.3 module created. See also the earconvert tool documentation.
You must migrate J2EE 1.2 application modules to which you want to add J2EE 1.3 level WAR, RAR, EJB and client modules. This tool migrates only the application modules. J2EE 1.2-level modules inside a J2EE 1.2 application module must be migrated by other means.
Assemble an EJB module to contain enterprise beans and related code artifacts. (Group Web components, client code, and resource adapter code in separate modules.)
You can install an EJB module as a standalone application or you can combine it with other modules into an enterprise application.
Assemble a Web module to contain servlets, JSP files, and related code artifacts. (Group enterprise beans, client code, and resource adapter code in separate modules.)
You can install a Web module as a standalone application or combine it with other modules into an enterprise application.
You are ready to combine your new or migrated modules into an application module (EAR file).
For applications containing only Web modules, this step is optional. It is feasible to deploy Web modules without assembling them into application modules.
What to do next
After assembling your applications, use a systems management tool to deploy the EAR or WAR files onto the application server.The systems management tool follows the security and deployment instructions defined in the deployment descriptor, and enables you to modify bindings specified within the AAT. The tool locates the required external resources that the application uses, such as enterprise beans and databases.
Select a tool to use:
If you are uncertain of which systems management tool to use, try using the administrative console.