Custom finder SQL dynamic enhancement
To ensure data integrity for applications using custom finders defined on Enterprise JavaBeans (EJB) version 1.1 home interfaces, WebSphere Application Server version 5.x uses custom finder Structured Query Language (SQL) dynamic enhancement to maintain correct SQL locking semantics.
WebSphere Application Server uses SQL clauses applied to the custom finder SQL statements for those custom finders defined with the Update attribute and certain method-level isolation level settings. These dynamic enhancements are applied only if the backend data store supports these clauses.
This support takes affect at run time when the run time attempts to execute Container Managed Persistence (CMP) persistence operations associated with the custom finders. To ensure that the SQL dynamic enhancements occur correctly for custom finders defined on an EJB version 1.1 home interface accessing a backend data store that requires the special SQL locking clauses, WebSphere Application Server provides new Java Virtual Machine (JVM) and bean (module) properties. These properties enable you to indicate which custom finders should be enhanced, provided the backend store supports the SQL clauses. For more information about these properties, see Custom finder SQL dynamic enhancement properties.
There are several important items to consider when using this functionality:
- this support only applies to EJB version 1.1 CMP Custom Finder
methods
- Option A CMP beans and CMP beans involved in an inheritance relationship
are not supported
- applications using this capability in WebSphere Application Server for z/OS V4.x continue
to function, but address some compatibility issues:
- the default behavior of the WebSphere Application Server V5.x product is the opposite
of the V4.x product, that is, the default for 5.x is not to
enhance custom finder SQL statements unless directed to by specific settings.
If your WebSphere Application Server for z/OS installation relies on the automatic dynamic enhancement
of all custom finders in all applications installed, set the com.ibm.websphere.ejbcontainer.customfinder.honorAccessIntent
indicator to all.
- If an application contains a bean which has the com.ibm.websphere.persistence.bean.managed.custom.finder.access.intent indicator set into its env-var settings, that indicator continues to be used, provided the dynamic SQL enhancement features of the V5.x product are enabled. For more information, see Custom finder SQL dynamic enhancement properties
- the default behavior of the WebSphere Application Server V5.x product is the opposite
of the V4.x product, that is, the default for 5.x is not to
enhance custom finder SQL statements unless directed to by specific settings.
If your WebSphere Application Server for z/OS installation relies on the automatic dynamic enhancement
of all custom finders in all applications installed, set the com.ibm.websphere.ejbcontainer.customfinder.honorAccessIntent
indicator to all.
Establishing custom finder SQL dynamic enhancement server-wide
Establishing custom finder SQL dynamic enhancement on a set of beans
Establishing custom finder SQL dynamic enhancement for specific custom finders
Disabling custom finder SQL dynamic enhancement for custom finders on a specific bean
Custom finder SQL dynamic enhancement properties