Implementing EJB 2.x applications

Use this task when you are implementing Enterprise JavaBeans (EJB) 2.x applications.

About this task

Based on the Enterprise JavaBeans (EJB) specification, enterprise beans are Java™ components that typically implement the business logic of Java 2 Platform, Enterprise Edition (J2EE) applications as well as access data. IBM®WebSphere® Application Server provides broad support for enterprise beans, including the EJB 2.x and EJB 3.0 and EJB 3.1 specifications. The EJB 2.x specification includes a container-managed persistence (CMP) 2.0 component model, which provides a number of improvements to aid developer productivity and application performance. The EJB 3.0 and 3.1 specifications simplify the development of business logic and data handling for enterprise applications.

This task lists the steps needed to implement EJB 2.x application in WebSphere Application Server, including tuning and troubleshooting tips.

Procedure

  1. Migrate enterprise bean code.
    1. Enterprise JavaBeans (EJB) Version 2.1-compliant beans can be assembled only in an EJB 2.1-compliant module, although an EJB 2.1-compliant module can contain a mixture of Version 1.x and Version 2.1 beans.
  2. Develop EJB 2.x applications.
    1. You can develop an EJB application or prepare an existing application. For Enterprise JavaBeans™ (EJB) 2.x CMP entity beans, you can use the partial update feature to specify how you want to update the persistent attributes of the CMP bean to the database. This feature is provided as a bean-level persistence option, called PartialOperation, in the access intent policy configured for the bean.
  3. Assemble EJB 2.x applications.
    1. This topic assumes that you have created and unit tested an enterprise bean file that you want to assemble in an enterprise application and deploy onto an application server. Now you are assembling EJB modules based on the EJB 2.x and earlier specifications. You can apply an access intent policy to an application's entity beans through the assembly tool.
  4. Deploy EJB 2.x applications.
    1. When you deploy an EJB module, you install that module on a server that has been configured to support deployed modules.
  5. Administer EJB 2.x applications.
    1. Each application server can have a single EJB container; one is created automatically for you when the application server is created. You can back up entity beans, enable, and disable session beans.
  6. Secure EJB 2.x applications.
    1. You 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.
  7. Tune EJB 2.x applications.
    1. If you use applications that affect the size of the EJB container cache, it is possible that the performance of your applications can be impacted by an incorrect size setting. Container managed persistence (CMP) is discussed in this topic, although it is important to know that entity beans are not supported in an EJB 3.x module. One of the steps in tuning your EJB container to optimum performance levels is to fine-tune the EJB cache.
  8. Troubleshoot EJB 2.x applications.
    1. Use these troubleshooting tips for problems related to accessing enterprise beans and access intents for EJB 2.x entity beans.

Results

You have implemented EJB 2.x applications on WebSphere Application Server.

指出主題類型的圖示 作業主題



時間戳記圖示 前次更新: July 9, 2016 11:15
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=tejb_implement_ejb2x_apps
檔名:tejb_implement_ejb2x_apps.html