Task overview: Using enterprise beans in applications
This article provides an overview of the tasks perform to use enterprise beans in a J2EE application.
Procedure
- 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 one of the assembly tools. 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 appserver, 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 appserver.
- Test the modules.
- As needed, debug problems with the container.
- Debug access problems.
- Assemble the production application using one of 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 one of the assembly tools.
- Tune the performance of the application. See Best practices for developing enterprise beans.
Enterprise beans
Developing enterprise beans
Use access intent policies
EJB modules
Assembling EJB modules
EJB containers
Manage EJB containers
Deploying EJB modules
Enterprise beans: Resources for learning
EJB method Invocation Queuing
Securing enterprise bean applications
Enterprise bean and EJB container troubleshooting tips
Enterprise bean cannot be accessed from a servlet, a JSP file, a stand-alone program, or another client