Liberty supports a subset of the WebSphere Optimized Local Adapters (WOLA) APIs. This rule flags the use of APIs that are unsupported on Liberty.
The Java™ rule flags the following classes related to MBean functions that are unavailable on Liberty:
com.ibm.websphere.ola.OLAConnectionHandlecom.ibm.websphere.ola.OLAHeadercom.ibm.websphere.ola.OLARGEcom.ibm.websphere.ola.OLARGEInformationcom.ibm.websphere.ola.OLARGEListcom.ibm.websphere.ola.OLASearchObjectcom.ibm.websphere.ola.OLAStatusInformation
The Java rule also flags RemoteHome annotations with
com.ibm.websphere.ola.ExecuteHome.class as the remote interface.
Liberty ignores the @RemoteHome interface.
To host this EJB on Liberty, modify your application to also provide a business local EJB bean
that implements com.ibm.websphere.ola.ExecuteLocalBusiness.
@RemoteHome(com.ibm.websphere.ola.ExecuteHome.class)
The XML rule flags <remote> and <home> elements that
contain references to com.ibm.websphere.ola classes.
To use WOLA with EJB beans on Liberty, you need to migrate your EJB beans to use
EJB 3.0 <business-local> interfaces, and your EJB class must implement
com.ibm.websphere.ola.ExecuteLocalBusiness.
For example, the tool flags the use of WOLA on the remote and home interfaces:
To use WOLA in this application on Liberty, migrate the EJB classes to use the local business interface and update the ejb-jar.xml file as follows:
Also note that Java Naming and Directory Interface (JNDI) names of target EJB beans on Liberty use java: naming.
Start the Liberty server and check the server log for messages that display the JNDI of the target EJB beans.
For detailed information about WOLA on Liberty, see the Developing applications that use optimized local adapters on Liberty documentation.
For information about other APIs and SPIs that are not supported on Liberty, see Some APIs and SPIs are not available on Liberty.