WAS v8.5 > End-to-end paths > EJB applicationsImplement EJB 3.x applications
Based on the EJB specification, enterprise beans are Java components that typically implement the business logic of Java Platform, Enterprise Edition (JEE) applications as well as access data. IBM WebSphere Application Server provides broad support for enterprise beans, including the EJB 2.x and EJB 3.x specifications. The EJB 3.x specifications simplify the development of business logic and data handling for enterprise applications. We can assemble the beans into one or more EJB 3.x modules using one of the assembly tools.
Procedure
- Migrate enterprise bean code.
There are no migration issues associated with using EJB 3.x beans. Existing applications continue to run as-is and compile without error. The EJB 3.0 and 3.1 specifications have deprecated the use of EJB 1.1 style entity beans. You are encouraged to start migrating to Java™ Persistence API (JPA) or JDBC as a replacement for entity beans.
- Develop EJB 3.x applications.
Design a Java EE application and the enterprise beans that it needs. Before developing entity beans with CMP, read the topic, Concurrency control. Keep in mind that EJB 3.x modules do not support entity beans. You must continue to place entity beans in custom EJB 2.x-level modules.
- Assemble EJB 3.x applications.
Assemble an EJB 3.x module to contain enterprise beans and related code artifacts. Group web components, client code, and resource adapter code in separate modules. After the EJB module is assembled, install it as a stand-alone application or combine it with other modules into an enterprise application.
- Deploy the EJB 3.x applications.
When you deploy an EJB module, you install that module on a server that has been configured to support deployed modules. Assemble EJB modules assemble one or more web modules, and assemble them into a Java EE application.
- Administer EJB 3.x applications.
Manage EJB containers, administer session beans and entity beans.
- Secure EJB 3.x applications.
We can protect enterprise bean methods by assigning security roles to them. Before you assign security roles, you need to know which EJB methods need protecting and how to protect them.
- Tune EJB 3.x applications.
If we use applications that affect the size of the EJB container cache, it is possible the performance of the applications can be impacted by an incorrect size setting. It is important to know that entity beans are not supported in an EJB 3.x module. One of the steps in tuning custom EJB container to optimum performance levels is to fine-tune the EJB cache.
- Troubleshoot EJB 3.x applications.
Use these troubleshooting tips for problems related to accessing enterprise beans.
Related
Troubleshooting Enterprise JavaBeans applications
Change applications to WebSphere version specific setRollbackOnly behavior
Develop enterprise beans
Develop EJB 3.x enterprise beans
Assemble EJB 3.x enterprise beans
Deploy EJB 3.x enterprise beans
Deploy EJB modules
Assemble EJB modules
Develop entity beans
Administer entity beans
Develop applications using the embeddable EJB container
Configure EJB 3.1 session bean methods to be asynchronous
Migrating enterprise bean code to the supported specification
Manage EJB containers
Secure Enterprise JavaBeans applications
Tune Enterprise JavaBeans applications
Configure EJB 3.1 session bean methods to be asynchronous
Develop session beans