Introduction: EJB applications

Use this topic to explore the key concepts pertaining to Enterprise JavaBeans (EJB) applications. Based on the EJB specification, enterprise beans are managed Java components that typically implement the business logic of Java 2 Platform, Enterprise Edition (J2EE) applications, as well as access data.

New or updated for this feature pack The WebSphere Application Server Version 6.1 Feature Pack for EJB 3.0 implements the EJB Version 3.0 and Java Persistence API (JPA) 1.0 specifications, which simplifies business logic and data handling for enterprise applications. For more information review the topic What is new in the Version 6.1 Feature Pack for EJB 3.0

Enterprise beans
An enterprise bean is a managed Java component that can be combined with other resources to create Java applications. There are three types of enterprise beans: entity beans, session beans, and message-driven beans. Enterprise beans focus on managing business logic, providing ways to compose business logic and declaring the transaction and security needs of business logic.

New or updated for this feature pack Persistence logic in enterprise beans is being phased out and replaced by the JPA.

EJB modules
An EJB module is used to assemble one or more enterprise beans into a single deployable unit. An EJB module is stored in a standard Java archive (JAR) file.
EJB containers
An EJB container provides a run-time environment for enterprise beans within the application server. The container handles all aspects of an enterprise bean's operation within the application server and acts as an intermediary between the user-written business logic within the bean and the rest of the application server environment. Container-managed persistence (CMP) transfers data between the variables of an entity bean and a resource manager administered by the entity bean container.
Partial column updates for container managed persistence
Previously, the WebSphere Application Server implementation of the CMP bean method, ejbStore, always stored all of the persistent attributes of the CMP bean to the database, even if only a subset of persistent attribute fields were changed. This performance degradation is eliminated in this release of the product.
Sequence grouping for container-managed persistence
After assembling an EJB module that contains CMP beans, you can prevent certain types of database-related exceptions from occurring during application run time. Using sequence grouping, you can specify the order in which entity beans update relational database tables.
Message-driven beans - automatic message retrieval
WebSphere Application Server supports the use of message-driven beans as asynchronous message consumers.
Message-driven beans - listener port components
The WebSphere Application Server support for message-driven beans deployed against listener ports is based on Java Message Service (JMS) message listeners and the message listener service, and builds on the base support for JMS.
Task overview: Storing and retrieving persistent data with the Java Persistence API (JPA) New or updated for this feature pack
The JPA supports the Java EE and EJB 3.0 specifications requirements. JPA manages persistence and object and relational mapping, and represents a simplification of the persistence programming model. The JPA model is based on the Java objects programming model that applies to both the Java EE and Java Platform Standard Edition (SE) environments. In addition, the JPA defines the object and relational mapping within its specifications instead of relying on vendor-specific mapping implementations. These features make JPA easier to implement and manage than previous persistence models.
Lightweight local operational mode for entity beans
WebSphere Application Server provides a special operational mode called lightweight local mode, which can improve the performance of entity bean methods. You can decide which entity beans in your application to run in this mode.
(CMP 2.x persistence only) Access intent policies
An access intent policy is a named set of properties (access intents) that governs data access for EJB persistence. You can assign policies to an entity bean and to individual methods on an entity bean's home, remote, or local interfaces during assembly. You can set access intents only within EJB Version 2.x-compliant modules for entity beans with CMP Version 2.x.
(CMP 2.x persistence only) Access intent service
Access intent is a WebSphere Application Server runtime service that enables you to more precisely manage an application's persistence.
Stateful session bean failover for the EJB container
WebSphere Application Server Version 6.0 enables you to construct applications with the assumption that your applications using stateful session beans are not limited by unexpected server failures. This version of the product utilizes the functions of the Data Replication Service (DRS) and Workload Management (WLM) so you can enable stateful session bean failover.



Related concepts
New or updated for this feature pack Feature Pack for EJB 3.0
Related reference
New or updated for this feature pack What is new in the Version 6.1 Feature Pack for EJB 3.0
Related information
Learn about EJB applications
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=welc6tech_ejb_intro
File name: welc6tech_ejb_intro.html