Before you begin
Assemble application modules (known as EAR files) from new or existing J2EE 1.3 or 1.4 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 stand-alone Web modules is necessary for deploying the applications onto the application server.For
the Windows and Linux Intel operating systems, the Assembly Toolkit replaces
the Application Assembly Tool (AAT). Visit the Web site http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q=&uid=swg24005125&loc=en_US&cs=utf-8&lang=en+en to download the Application Server Toolkit product, which offers the Assembly
Toolkit and other products. The Assembly Toolkit consists of the J2EE Perspective
of the WebSphere Studio Application Developer product without the code generation
capabilities.
Why and when to perform this task
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
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.
You can install an EJB module as a stand-alone application or you can combine it with other modules into an enterprise application.
You can install a Web module as a stand-alone application or combine it with other modules into an enterprise application.
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.