Application assembly consists of creating Java 2 Platform, Enterprise Edition (J2EE) modules that can be deployed onto application servers. The modules are created from code artifacts such as Web application archives (WAR files), resource adapter archives (RAR files), enterprise bean (EJB) JAR files, and application client archives (JAR files). This packaging and configuring of code artifacts into enterprise application modules (EAR files) or standalone Web modules is necessary for deploying the modules onto an application server.
Before you begin
This article assumes that you have developed code artifacts that you want to deploy onto an application server and have unit tested the code artifacts in your favorite integrated development environment. Code artifacts that you might assemble into deployable J2EE modules include the following:Why and when to perform this task
You assemble code artifacts into J2EE modules in order to deploy the code artifacts onto an application server. When you assemble code artifacts, you package and configure the code artifacts into deployable J2EE applications and modules, edit deployment descriptors, and map databases as needed. Unless you assemble your code artifacts into J2EE modules, you cannot run them successfully on an application server.This article describes how to assemble J2EE code artifacts into deployable modules using an assembly tool. Alternatively, you can use a WebSphere rapid deployment tool to quickly assemble and deploy J2EE code artifacts. Refer to articles on Rapid deployment of J2EE applications in this information center for details.
Steps for this task
What to do next
After assembling your applications, use a systems management tool to deploy the EAR or WAR files onto the application server. Ways to install applications or modules lists systems management tools available for deploying J2EE modules on an 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 an assembly tool. The tool locates the required external resources that the application uses, such as enterprise beans and databases.To deploy EJB projects to a target server, right-click the EJB project in the Project Explorer view and click Deploy.
Package your application so that the .ear file contains necessary modules only. Modules can include metadata for the modules such as information on deployment descriptors, bindings, and IBM extensions.
Use the administrative console at installation to complete the security instructions defined in the deployment descriptor and to locate required external resources, such as enterprise beans and databases. You can add configuration properties and redefine binding properties defined in an assembly tool.
Related concepts
EJB modules
Enterprise (J2EE) applications
Web applications
Web modules
Application Client for WebSphere Application Server
Resource adapter archive file
Related tasks
Assembling EJB modules
Assembling application clients
Assembling resource adapter (connector) modules
Assembling Web applications
Developing Web applications
Securing enterprise bean applications
Securing Web applications using an assembly tool
Related information
Deploying J2EE application clients on workstation platforms
Developing and testing a complete J2EE "Hello World"
application with WebSphere Studio V5
Developing and Deploying an End-to-end
J2EE Application to JBoss Application Server using WebSphere Studio V5
Setting Up a Remote WebSphere Application
Server in WebSphere Studio V5