Applying access intent policies to beans

 

You can apply an access intent policy to an application's entity beans through the assembly tool.

 

Overview

Container-managed persistence (CMP) developers can use access intent to provide hints on how the appserver run time should manage the details of persistence without having to explicitly manage any of the persistence logic from within their application.

Use the access intent service is also an option for programmers who develop bean-managed persistence (BMP) entity beans. Because the only meaningful difference between BMP and CMP components is the mechanism that provides the persistence logic, BMP beans leverage access intent hints in the same manner as the EJB container manages accent intent for CMP beans. This ability becomes especially important when BMP entities and CMP entities want to share connections. BMP beans configured with the same concurrency as the CMP beans and implemented to the same isolation level mapping as the CMP can share connections.

Developers can apply access intent policies to BMP entity beans as well as to CMP entity beans. It is expected that BMP developers use only those access intent attributes that are important to a particular BMP bean. The access intent service interface is bound into the java:comp namespace for each particular BMP bean. The access intent policy retrieved from the access intent service is current from the time that the ejbLoad process is called until the time that the ejbStore process completes its invocation.

This is the preferred technique to define access intent policies. Method-level access intent is deprecated in V6.0.

 

Procedure

1. Start the Application Server Toolkit.

    

2. Optional: Open the J2EE perspective to work with J2EE projects. Click Window > Open Perspective > Other > J2EE.

    

3. Optional: Open the Project Explorer view. Click Window > Show View > Project Explorer. Another helpful view is the Navigator view (Window > Show View > Navigator).

4. Create a new application EAR file or edit an existing one. For example, to change attributes of an existing application, use the import wizard to import an EAR file. To start the import wizard:

   1. Select File > Import > EAR file > Next

   2. Select the EAR file.

   3. Create a WAS v6.0 type of Server Runtime. Select New to open the New Server Runtime Wizard and follow the instructions.

   4. In the Target server field, select WAS v6.0 type of Server Runtime.

   5. Select Finish

5. In the Project Explorer view of the J2EE perspective, right-click Deployment Descriptor: EJB Module Name under the EJB module for the bean instance, then select Open With > Deployment Descriptor Editor. A property dialog notebook for the EJB project is displayed in the property pane.

6. Select the Access tab.

7. In the Access Intent for Entities 2.x (Bean Level) panel, select the name of the bean.

8. On the right side of the Access Intent for Entities 2.x (Method Level) panel, select Add. The Add Access Intent panel displays.

9. In the Access intent name field, select wsPessimisticUpdate from the drop-down list.

    

10. Optional: Enter a Description to help you remember what this policy does.

     

11. Optional: Change the Persistence Option setting

12. Click Finish. The access intent policy for the entity bean is shown in the Access Intent for Entities 2.x (Bean Level) panel

---

Access intent policies

 

Related tasks

Use access intent policies
Assembling applications

 

Related Reference

Access intent assembly settings
Access intent -- isolation levels and update locks