Task overview: Using enterprise beans in applications
This article provides an overview of the tasks perform to use enterprise beans in a J2EE application.
- Design a J2EE application and the enterprise beans that it needs. For links to design information that is specific to enterprise beans, see Data access: Resources for learning.
- Develop any enterprise beans that your application will use.
- Prepare for assembly. For your EJB 2.x-compliant entity beans, decide on an appropriate access intent policy.
- Assemble the beans into one or more EJB modules using the assembly tool. This process includes setting security. For your EJB 2.x-compliant entity beans, you might also want to designate container-managed persistence (CMP) sequence groups.
- Assemble the modules into a J2EE application using the assembly tool.
- For a given application server,
update the EJB container configuration if needed for the application to be deployed, and determine if you want to batch commands or defer commands for container-managed persistence.
- Deploy the application in an application server.
- Test the modules.
- Assemble the production application using the assembly tools.
- Deploy the application to a production environment.
- Manage the application:
- Manage installed EJB modules. After an application has been installed, you can manage its EJB modules individually through the Assembly Service Toolkit.
- Manage other aspects of the J2EE application.
- Update the module and redeploy it using the assembly tools.
- Tune the performance of the application. See Best practices for developing enterprise beans.
Sub-topics
Enterprise beans
Developing enterprise beans
Using access intent policies
EJB
modules
Assembling EJB
modules
EJB containers
Managing EJB containers
Deploying EJB modules
Enterprise beans: Resources for learning
EJB method Invocation Queuing