Assemble applications
Overview
This topic 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.
Application assembly consists of creating J2EE modules that can be deployed onto appservers. The modules are created from code artifacts such as...
- Web application archives (WAR files)
- resource adapter archives (RAR files)
- enterprise bean (EJB) JAR files
- 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 appserver.
This topic assumes that you have developed code artifacts to deploy onto an appserver and have unit tested the code artifacts in your favorite integrated development environment. Code artifacts that you might assemble into deployable J2EE modules include...
- Enterprise beans
- Servlets, JavaServer Pages files and other Web components
- Resource adapter (connector) implementations
- Application clients
- Session Initiation Protocol (SIP) modules (SAR files)
- Other supporting classes and files
Before you can assemble your code artifacts into deployable J2EE modules, install or get access to a supported assembly tool. WAS supports tools that you can use to develop, assemble, and deploy J2EE modules:
- Application Server Toolkit
- Rational Application Developer
You assemble code artifacts into J2EE modules in order to deploy the code artifacts onto an appserver. 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 appserver.
Procedure
- Start an assembly tool.
- Configure the assembly tool for work on J2EE modules.
- Migrate J2EE projects or code artifacts created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool.
To migrate files, use the J2EE Migration wizard or import the files to the assembly tool.
- Create an enterprise application project to which you can add archive files. You can create an enterprise application project separately or when you create archive files such as the following:
- Create a Web project.
- Create an EJB project.
- Create an application client.
- Create a resource adapter (connector) project.
- Edit the deployment descriptors as needed. You can edit deployment descriptors for enterprise application, Web, application client, and EJB modules.
Topics on deployment descriptor editors such as Application Deployment Descriptor editor in Application Server Toolkit documentation provide extensive information on editing deployment descriptors.
- Optional: Generate EJB to relational database (RDB) mappings for EJB modules.
- Verify the archive files.
- Generate code for deployment for Web services-enabled modules or for enterprise applications that use Web service modules.
What to do next
After assembling your applications, use a systems management tool to deploy the EAR or WAR files onto the appserver. Ways to install applications or modules lists systems management tools available for deploying J2EE modules on an appserver. 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.
After installation, you can view module deployment descriptors using the console.
Application assembly and J2EE applications
Assembly tools
Generating code for Web service deployment
Related concepts
EJB modules
Enterprise (J2EE) applications
Web applications
Web modules
Application Client for WAS
Related tasks
Develop Web applications
Related information
Overview of Application Server Toolkit
Start the Application Server Toolkit assembly tool
Configure the Application Server Toolkit assembly tool
Create an enterprise application project
Create a dynamic Web project
Create EJB projects
Create application clients
Create a connector project
Application Deployment Descriptor editor
Update maps with the Mapping editor
Validate code in enterprise applications
Deploy J2EE application clients on workstation platforms