Use this task when you are implementing Enterprise JavaBeans (EJB) 3.x applications.
Based on the Enterprise JavaBeans (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 specification simplifies the development of business logic and data handling for enterprise applications. You can assemble the beans into one or more EJB 3.x modules using one of the assembly tools.
The EJB 3.0 specification has justifiably been called the most important upgrade to the Java™ Platform, Enterprise Edition 5 (Java EE 5) programming model. The EJB 3.0 specification represents simplification and streamlining of the business logic and persistence programming models used in Java EE. While the Java Persistence API (JPA) replacement is called an entity class, it should not be confused with entity enterprise beans. A JPA entity is not an enterprise bean and is not required to run in an EJB container.
EJB method invocations throw com.ibm.websphere.ejbcontainer.EJBStoppedException when the target EJB application has been stopped. If you have cached the EJB reference in an instance variable by using either @EJB injection or JNDI lookup, then you can catch this exception and refresh the EJB reference by performing a non-cached lookup.
Complete the following procedure if you want to implement EJB 3.x application in WebSphere Application Server, including tuning and troubleshooting tips.