openliberty.websphere.liberty-websphere-unavailable-technologies.windup.xml Maven / Gradle / Ivy
The newest version!
This ruleset identifies usage of WebSphere APIs and technologies which are not provided by Open Liberty.
<div class="Text">
<p> The Activity Session service is unavailable on Liberty. This rule flags the following items: </p>
<ul>
<li>References to APIs in the <code>com.ibm.websphere.ActivitySession</code> package</li>
<li>The activity session JNDI name <code>java:comp/websphere/UserActivitySession</code></li>
<li>Elements that are related to activity sessions in Java Platform, Enterprise Edition (Java EE) extension deployment descriptors</li>
</ul>
</div>
<div class="Text">
<p> The following WebSphere Application Profiling APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.appprofile</code></li>
<li><code>com.ibm.websphere.appprofile.accessintent</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<span class="SubHeader">WebSphere Asynchronous Beans API</span>
<div class="Text">
<p> This rule flags APIs from the <code>com.ibm.websphere.asynchbeans</code> package. These APIs are not provided on Liberty and are marked as deprecated in WebSphere Application Server traditional V9.0. The WebSphere Asynchronous Beans API are replaced by JSR 236, Concurrency Utilities for Java EE. </p>
<p> <b>Note:</b> Concurrency Utilities for Java EE provides no replacement for the <code>com.ibm.websphere.asynchbeans.pool</code> APIs. </p>
<p> For information and examples about how to use Concurrency Utilities for Java EE instead of Asynchronous beans in WebSphere traditional, see <a href="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rasb_migrate_to_eeconcurrency" title="Opens a new window" onclick="javascript:helpWindow('http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rasb_migrate_to_eeconcurrency'); return false;"> Examples to migrate to EE Concurrency from Asynchronous beans and CommonJ</a>. </p>
<p> For information about the Concurrency Utilities for Java EE feature <code>concurrent-1.0</code> in Liberty, see the link below
</div>
<div class="Text">
<p>WebSphere Batch API and SPI are unavailable on Liberty. This rule flags the following packages:</p>
<ul>
<li><code>com.ibm.websphere.batch*</code></li>
<li><code>com.ibm.websphere.ci</code></li>
<li><code>com.ibm.websphere.grid.spi</code></li>
<li><code>com.ibm.websphere.longrun</code></li>
<li><code>com.ibm.wsspi.batch*</code></li>
</ul>
<p> For information on Liberty Batch, see <a href="http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102544" title="Opens a new window" onclick="javascript:helpWindow('http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102544'); return false;"> IBM WebSphere Liberty Java Batch</a>. </p>
<p> For information on transitioning to WebSphere Liberty Batch, see the <a href="http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102638" title="Opens a new window" onclick="javascript:helpWindow('http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102638'); return false;"> WebSphere Liberty Batch Migration</a> documentation. </p>
</div>
<div class="Text"> <span class="SubHeader">Web Services Policy Sets are unavailable in Liberty.</span>
<p> This rule detects the following generated files when using web services Policy Sets in WebSphere traditional: </p>
<ul>
<li>policySet.xml</li>
<li>policyAttachments.xml</li>
<li>clientPolicyAttachments.xml</li>
<li>policy.xml</li>
<li>bindings.xml</li>
<li>bindingDefinition.xml</li>
</ul>
<p> In Liberty, web services Policy Sets are no longer used. Changes are needed to migrate an application to the Web Services Policy implementation on Liberty. For more information on using WS-Policy in Liberty see <a href="https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/twlp_dep_policyattach.html" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/twlp_dep_policyattach.html'); return false;"> Defining web service policy via policy attachment</a>. </p>
<p> The web services security implementation for Liberty is different than WebSphere traditional. If an application is using the WebSphere traditional web services security adhering to the OASIS specification changes may not be necessary. Review the <a href="https://www.ibm.com/support/knowledgecenter/SS7K4U_liberty/com.ibm.websphere.wlp.zseries.doc/ae/cwlp_wssec_cxf_diff.html" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/support/knowledgecenter/SS7K4U_liberty/com.ibm.websphere.wlp.zseries.doc/ae/cwlp_wssec_cxf_diff.html'); return false;"> WS-Security behavior differences between traditional and Liberty</a> for more information about behavior differences that may require changes in your application. </p>
<p> For more information on the OASIS specification see <a href="https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/cwlp_wssec_specs.html" title="Opens a new window" onclick="https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/cwlp_wssec_specs.html'); return false;"> Web Services Security specifications and standards</a>. </p>
</div>
<div class="Text">
<p> Web Services Atomic Transaction (WS-AT) Version 1.2 is now available on Liberty. This rule flags the following unsupported WS-AT attributes in IBM deployment descriptor extensions: </p>
<ul>
<li><code>execute-using-wsat="true"</code></li>
<li><code>sendWSAT="true"</code></li>
<li><code>send-wsat-context="true"</code></li>
<li><code>supportsWSAT="true"</code></li>
</ul>
<p> Liberty does not provide support for WS-AT with EJB global transactions, but Liberty applications can use the WS-AT Version 1.2 specification. </p>
<p> For more information, see the knowledge center topics starting at <a href="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=twlp_dep_wsat_lib" title="Opens a new window" onclick="javascript:helpWindow('http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=twlp_dep_wsat_lib'); return false;"> Web Services Atomic Transaction in Liberty</a>. </p>
</div>
<div class="Text">
<p> Web Services Business Activity (WS-BA) is unavailable on Liberty. This rule flags references to APIs in the com.ibm.websphere.wsba package and the business activity JNDI name <code>java:comp/websphere/UserBusinessActivity</code>. </p>
</div>
<div class="Text">
<p> On Liberty, the dynamic cache service is provided by the Distributed Map Interface for Dynamic Caching feature, <code>distributedMap-1.0</code>, and the Web Response Cache feature, <code>webCache-1.0</code>. The implementation has the following restrictions: </p>
<ul>
<li>No cache replication</li>
<li>Only the high-performance disk caching mode is supported with random and size eviction techniques</li>
<li>There is no support for Web Services client and server side caching as well as portlet caching in the cachespec.xml file</li>
<li>Servlet caching of SingleThreadModel servlets is not supported</li>
<li>Defining cache configuration by using properties files is not supported for JAR files that contain only Enterprise JavaBeans</li>
<li>Limiting the memory cache sizes in megabytes works only for 32-bit Java Virtual Machines</li>
</ul>
<p> This rule flags Java code that has references to the following packages: </p>
<ul>
<li><code>com.ibm.websphere.cache</code></li>
<li><code>com.ibm.ws.cache</code></li>
<li><code>com.ibm.wsspi.cache</code></li>
<li><code>com.ibm.websphere.servlet.cache</code></li>
</ul>
<p> The following APIs and SPIs are not available in Liberty: </p>
<ul>
<li><code>com.ibm.websphere.cache.ServletCache</code></li>
<li><code>com.ibm.wsspi.cache.CacheInstanceResourceBinder</code></li>
<li><code>com.ibm.wsspi.cache.CacheMonitor</code></li>
<li><code>com.ibm.wsspi.cache.ESIStats</code></li>
<li><code>com.ibm.wsspi.cache.ESIStats$ESIServerStats</code></li>
<li><code>com.ibm.wsspi.cache.ESIStats$ESIServerStats$ESIProcessorStats</code></li>
<li><code>com.ibm.wsspi.cache.ESIStats$ESIServerStats$ESIProcessorStats$ESICacheEntryStats</code></li>
</ul>
<p> For detailed information about dynamic cache on Liberty, see the following resources: </p>
<ul>
<li> <a href="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=rwlp_restrict#rwlp_restrict__dynacache-restrict" title="Opens a new window" onclick="javascript:helpWindow('http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=rwlp_restrict#rwlp_restrict__dynacache-restrict'); return false;"> Liberty:Runtime environment known issues and restrictions</a> </li>
<li> <a href="https://mediacenter.ibm.com/media/Dynamic+cache+in+Liberty/0_bnh3uidz" title="Opens a new window" onclick="javascript:helpWindow('https://mediacenter.ibm.com/media/Dynamic+cache+in+Liberty/0_bnh3uidz'); return false;"> Dynamic cache in Liberty</a> document </li>
</div>
<div class="Text">
<p> The WebSphere Enterprise JavaBeans (EJB) query service is not available on Liberty. </p>
<p> This rule flags Java code that has references to the <code>com.ibm.websphere.ejbquery</code> package. </p>
<p> WebSphere EJB query service is used to query entity beans, which are not available on Liberty. </p>
</div>
<div class="Text">
<p> The following WebSphere i18n APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.i18n.context</code></li>
<li><code>com.ibm.wsspi.i18n.context.util</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
METHOD_CALL
<div class="Text">
<p> On Liberty, each DataHandler object can be written to an output stream only once. Writing a DataHandler object to an OutputStream object more than once results in an empty file. After you call the <code>javax.activation.DataHandler.writeTo(OutputStream)</code> method, you cannot pass the DataHandler object to another method, return it, or store it for later use. </p>
<p> As a workaround, you can create a new DataHandler object and initialize the DataHandler object with the content that was already retrieved from the existing DataHandler object using the <code>writeTo</code> method. For example: </p>
<table class="code">
<tbody>
<tr>
<td> <span class="Code"> <span class="JavaType">File</span> f = <span class="JavaKeyword">new</span> File("received_image");<br> <span class="JavaKeyword">if</span> (f.exists()) {<br> <span class="indent"></span>f.delete();<br> }<br> <br> <span class="JavaType">FileOutputStream</span> fos = <span class="JavaKeyword">new</span> FileOutputStream(f);<br> <br> // Write the DataHandler object to the output stream.<br> img_in.writeTo(fos);<br> <br> // Create a new DataHandler object and initialize it with<br> // the content that was retrieved using the writeTo method above.<br> <br> <span class="JavaType">FileDataSource</span> fos_out = <span class="JavaKeyword">new</span> FileDataSource(f);<br> <br> <span class="JavaType">DataHandler</span> img_out = <span class="JavaKeyword">new</span> DataHandler(fos_out);<br> <br> <br> <span class="JavaKeyword">return</span> img_out; </span> </td>
</tr>
</tbody>
</table>
</div>
METHOD_CALL
METHOD_CALL
METHOD_CALL
<div class="Text">
<p> This rule flags references to the following methods: </p>
<ul>
<li><code>com.ibm.websphere.management.AdminService.getProcessName()</code></li>
<li><code>com.ibm.ejs.ras.RasHelper.getServerName()</code></li>
<li><code>com.ibm.websphere.runtime.ServerName.getDisplayName()</code></li>
<li><code>com.ibm.websphere.runtime.ServerName.getFullName()</code></li>
</ul>
<p> These methods are not available on Liberty. </p>
<p> The source scanner has a quick fix to change any reference to the methods mentioned earlier to <code>java.lang.System.getProperty("wlp.server.name")</code> which retrieves the name of your Liberty server. This solution does not work on WebSphere Application Server traditional. </p>
<p> For alternative solutions, see the <a href="https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/rwlp_dirs.html#d132906e961" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/rwlp_dirs.html#d132906e961'); return false;"> Programmatic access to location properties</a> section in the Knowledge Center. </p>
</div>
ANNOTATION
<div class="Text">
<p> Liberty does not support Simple Object Access Protocol (SOAP) over Java Message Service (JMS). References to the following namespaces indicate usage of SOAP over JMS: </p>
<ul>
<li>http://www.w3.org/2010/soapjms/</li>
<li>http://www.w3.org/2010/soapjms/soap1.1</li>
<li>http://www.w3.org/2010/soapjms/soap1.2</li>
</ul> This rule flags the following items:
<p></p>
<ul>
<li><code>javax.xml.ws.BindingType</code> annotations with a <code>value</code> attribute that references one of the described namespaces</li>
<li>WSDL files with a <code>transport</code> attribute on the <span class="XmlDefinition"><binding></span> element that references one of the described namespaces</li>
</ul>
</div>
<div class="Text">
<p> The WebSphere startup bean service was superseded by the startup beans in Enterprise JavaBeans (EJB) 3.1. The service is deprecated in WebSphere Application Server traditional V8.0 and is not available on Liberty. </p>
<p> This rule flags Java code that has references to the <code>com.ibm.websphere.startupservice</code> package. </p>
<p> For information about EJB 3.1 startup beans, see the following resources: </p>
<ul>
<li> <a href="https://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/asyncbns/tasks/tasb_confstb.html" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/asyncbns/tasks/tasb_confstb.html'); return false;"> Using startup beans</a> IBM knowledge center documentation </li>
<li> <a href="http://docs.oracle.com/javaee/6/api/javax/ejb/Startup.html" title="Opens a new window" onclick="javascript:helpWindow('http://docs.oracle.com/javaee/6/api/javax/ejb/Startup.html'); return false;"> javax.ejb.Startup</a> annotation Java documentation </li>
<li> <a href="http://www.redbooks.ibm.com/abstracts/redp4885.html" title="Opens a new window" onclick="javascript:helpWindow('http://www.redbooks.ibm.com/abstracts/redp4885.html'); return false;"> Developing Enterprise JavaBeans Applications</a> Redpaper </li>
</ul>
</div>
<div class="Text">
<p> The following WebSphere Service Data Objects (SDO) APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.sdo</code></li>
<li><code>com.ibm.websphere.sdox</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The WebSphere Scheduler API was superseded by Enterprise JavaBeans Persistent Timers 3.2, which is enabled by the ejbPersistentTimer-3.2 Liberty feature. </p>
<p> This rule flags references to the <code>com.ibm.websphere.scheduler</code> package because it is not available on Liberty. </p>
<p> For information about the Enterprise JavaBeans Persistent Timers feature, see the link below
</div>
<div class="Text">
<p> The WebSphere Servlet API was superseded by standard Servlet 3.0 functionality. </p>
<p> This rule flags Java code that has references to the following classes and packages because they are not available on Liberty. </p>
<ul>
<li><code>com.ibm.servlet.ClientList</code></li>
<li><code>com.ibm.servlet.ClientListElement</code></li>
<li><code>com.ibm.servlet.MLNotFoundException</code></li>
<li><code>com.ibm.servlet.PageListServlet</code></li>
<li><code>com.ibm.servlet.PageNotFoundException</code></li>
<li><code>com.ibm.websphere.servlet.filter.ChainedRequest</code></li>
<li><code>com.ibm.websphere.servlet.filter.ChainedResponse</code></li>
<li><code>com.ibm.websphere.servlet.filter.ChainerServlet</code></li>
<li><code>com.ibm.websphere.servlet.filter.ServletChain</code></li>
<li><code>com.ibm.websphere.servlet.response.IResponse</code></li>
<li><code>com.ibm.websphere.servlet.response.StoredResponseCompat</code></li>
<li><code>com.ibm.websphere.servlet.response.HttpServletResponseProxy</code></li>
<li><code>com.ibm.websphere.servlet.response.ResponseUtils</code></li>
<li><code>com.ibm.websphere.servlet.response.ServletOutputStreamAdapter</code></li>
<li><code>com.ibm.websphere.servlet.response.ResponseErrorReport</code></li>
<li><code>com.ibm.websphere.servlet.request</code></li>
<li><code>com.ibm.websphere.webcontainer.async</code></li>
</ul>
<p> For information about the Java EE Servlet APIs, see the <a href="http://docs.oracle.com/javaee/6/api/?javax/servlet/package-summary.html" title="Opens a new window" onclick="javascript:helpWindow('http://docs.oracle.com/javaee/6/api/?javax/servlet/package-summary.html'); return false;"> javax.servlet</a> package Java documentation. </p>
<p> For information about the WebSphere Servlet APIs, see the <a href="http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.javadoc.doc/web/apidocs/overview-summary.html" title="Opens a new window" onclick="javascript:helpWindow('http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.javadoc.doc/web/apidocs/overview-summary.html'); return false;"> IBM WebSphere Application Server, Release 8.5 API Specification</a>. </p>
</div>
<div class="Text">
<p> The following WebSphere Application Client APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.client.applicationclient</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Connector Architecture APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.j2c</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Enterprise JavaBeans APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.ejbcontainer</code></li>
<li><code>com.ibm.websphere.ejbpersistence</code></li>
<li><code>com.ibm.websphere.csi</code></li>
<li><code>com.ibm.wsspi.ejbpersistence</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Exception APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.exception.DistributedEJBCreateException</code></li>
<li><code>com.ibm.websphere.exception.DistributedEJBRemoveException</code></li>
<li><code>com.ibm.ws.exception</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following Extension Registry APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.workplace.extension</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following Integrated Solutions Console (ISC) APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.isc.api.platform</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere logging and RAS APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.logging.RawTraceList</code></li>
<li><code>com.ibm.websphere.logging.RawTraceList$PatternLevel</code></li>
<li><code>com.ibm.websphere.logging.MessageConverter</code></li>
<li><code>com.ibm.websphere.logging.WsLevel</code></li>
<li><code>com.ibm.ejs.ras</code></li>
<li><code>com.ibm.ffdc</code></li>
<li><code>com.ibm.ras</code></li>
<li><code>com.ibm.websphere.als</code></li>
<li><code>com.ibm.websphere.logging.cbe</code></li>
<li><code>com.ibm.websphere.ras</code></li>
<li><code>com.ibm.wsspi.rasdiag</code></li>
<li><code>com.ibm.wsspi.xct</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Management APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.ant.tasks</code></li>
<li><code>com.ibm.websphere.hamanager.jmx</code></li>
<li><code>com.ibm.websphere.interrupt</code></li>
<li><code>com.ibm.websphere.management</code></li>
<li><code>com.ibm.websphere.naming</code></li>
<li><code>com.ibm.websphere.product</code></li>
<li><code>com.ibm.wsspi.management.metadata</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere ORB Extensions APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.orbext</code></li>
<li><code>com.ibm.ejs.oa.EJSORB</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Performance Monitoring Infrastructure (PMI) APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.pmi</code></li>
<li><code>com.ibm.wsspi.pmi</code></li>
<li><code>com.ibm.ws.performance.tuning.rule</code></li>
<li><code>com.ibm.ws.pmi.server</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Portal APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.portal</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Resource Adapter APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.rsadapter</code></li>
<li><code>com.ibm.wsspi.rsadapter</code></li>
<li><code>com.ibm.wsspi.rawrapper</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Security APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.crypto.KeyGenerator</code></li>
<li><code>com.ibm.websphere.crypto.KeyPair</code></li>
<li><code>com.ibm.websphere.crypto.KeyPairGenerator</code></li>
<li><code>com.ibm.websphere.crypto.KeySetHelper</code></li>
<li><code>com.ibm.websphere.security.auth.WSPrincipal</code></li>
<li><code>com.ibm.websphere.security.auth.IdentityPrincipal</code></li>
<li><code>com.ibm.websphere.security.auth.MappingAuthData</code></li>
<li><code>com.ibm.websphere.security.auth.AuthenticationFailedException</code></li>
<li><code>com.ibm.websphere.security.auth.AuthenticationNotSupportedException</code></li>
<li><code>com.ibm.websphere.security.auth.MapCredentialFailedException</code></li>
<li><code>com.ibm.websphere.security.auth.MapCredentialNotSupportedException</code></li>
<li><code>com.ibm.websphere.security.auth.UnsupportedRealmException</code></li>
<li><code>com.ibm.websphere.security.auth.ValidationFailedException</code></li>
<li><code>com.ibm.websphere.security.auth.ValidationNotSupportedException</code></li>
<li><code>com.ibm.websphere.security.auth.callback.NonPromptCallbackHandler</code></li>
<li><code>com.ibm.websphere.security.auth.callback.WSCcacheCallBackHandlerImpl</code></li>
<li><code>com.ibm.websphere.security.auth.callback.WSGUICallbackHandlerImpl</code></li>
<li><code>com.ibm.websphere.security.auth.callback.WSStdinCallbackHandlerImpl</code></li>
<li><code>com.ibm.websphere.security.DistributedUserMappingFailedException</code></li>
<li><code>com.ibm.websphere.security.oidc.util</code></li>
<li><code>com.ibm.websphere.security.ProviderFailureException</code></li>
<li><code>com.ibm.websphere.security.SAFRoleMapper</code></li>
<li><code>com.ibm.websphere.security.TrustAssociationInterceptor</code></li>
<li><code>com.ibm.websphere.security.UserMapping</code></li>
<li><code>com.ibm.websphere.security.UserMappingException</code></li>
<li><code>com.ibm.websphere.security.WebSphereBaseTrustAssociationInterceptor</code></li>
<li><code>com.ibm.websphere.ssl.protocol</code></li>
<li><code>com.ibm.ws.security.core.SecurityContext</code></li>
<li><code>com.ibm.ws.security.util.LoginHelper</code></li>
<li><code>com.ibm.ws.security.util.ByteArray</code></li>
<li><code>com.ibm.wsspi.security.audit</code></li>
<li><code>com.ibm.wsspi.security.auth.callback.WSIdentityCallback</code></li>
<li><code>com.ibm.wsspi.security.auth.callback.WSMappingCallbackHandlerFactory</code></li>
<li><code>com.ibm.wsspi.security.auth.callback.WSProtocolPolicyCallback</code></li>
<li><code>com.ibm.wsspi.security.auth.callback.WSTokenHolderCallback</code></li>
<li><code>com.ibm.wsspi.security.auth.WSSubjectWrapper</code></li>
<li><code>com.ibm.wsspi.security.authorization</code></li>
<li><code>com.ibm.wsspi.security.context</code></li>
<li><code>com.ibm.wsspi.security.crypto.aes</code></li>
<li><code>com.ibm.wsspi.security.csiv2</code></li>
<li><code>com.ibm.wsspi.security.ltpa</code></li>
<li><code>com.ibm.wsspi.security.policy</code></li>
<li><code>com.ibm.wsspi.security.securitydomain</code></li>
<li><code>com.ibm.wsspi.security.spnego</code></li>
<li><code>com.ibm.wsspi.security.tai.NegotiateTrustAssociationInterceptor</code></li>
<li><code>com.ibm.wsspi.security.tai.NegotiateTrustAssociationInterceptorImpl</code></li>
<li><code>com.ibm.wsspi.security.tai.TrustAssociationInterceptorExt</code></li>
<li><code>com.ibm.wsspi.security.token.AuthenticationToken</code></li>
<li><code>com.ibm.wsspi.security.token.AuthorizationToken</code></li>
<li><code>com.ibm.wsspi.security.token.KerberosToken</code></li>
<li><code>com.ibm.wsspi.security.token.PropagationToken</code></li>
<li><code>com.ibm.wsspi.security.token.TokenHolder</code></li>
<li><code>com.ibm.wsspi.security.token.WSOpaqueTokenHelper</code></li>
<li><code>com.ibm.wsspi.security.web.saml</code></li>
<li><code>com.ibm.wsspi.ssl.RetrieveSignersHelper</code></li>
<li><code>com.ibm.wsspi.ssl.WSPKIClient</code></li>
<li><code>com.ibm.IExtendedSecurity</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Service Integration Bus (SIB) APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.sib</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere SMF recording APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.smf</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following Tivoli Performance Viewer SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.ws.tpv</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Extension Helper SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.ws.extensionhelper</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following Universal Description, Discovery and Integration (UDDI) APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.uddi</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Workload Manager APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.wlm</code></li>
<li><code>com.ibm.websphere.wlm.exception</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Studio Application Developer Integration Edition APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.webtools.runtime.AbstractStudioServlet</code></li>
<li><code>com.ibm.webtools.runtime.BuildNumber</code></li>
<li><code>com.ibm.webtools.runtime.NoDataException</code></li>
<li><code>com.ibm.webtools.runtime.StudioPervasiveServlet</code></li>
<li><code>com.ibm.webtools.runtime.TransactionFailureException</code></li>
<li><code>com.ibm.webtools.runtime.WSUtilities</code></li>
<li><code>com.ibm.etools.ctc.physicalrep</code></li>
<li><code>com.ibm.etools.ctc.plugin.binding.connector</code></li>
<li><code>com.ibm.etools.ctc.wsdl.extensions.physicalrep</code></li>
<li><code>com.ibm.etools.logging</code></li>
<li><code>com.ibm.etools.xsltypeconverter</code></li>
<li><code>com.ibm.jca.importservice</code></li>
<li><code>com.ibm.wsdl.extensions.physicalrep</code></li>
<li><code>com.ibm.wsdl.extensions.transformer</code></li>
<li><code>com.ibm.wsif.format.jca</code></li>
<li><code>com.ibm.wsif.format.literal</code></li>
<li><code>com.ibm.wsif.format.transformer</code></li>
<li><code>com.ibm.wsif.jca</code></li>
<li><code>com.ibm.wsif.providers.ejb.proxy</code></li>
<li><code>com.ibm.wsif.providers.transformer</code></li>
<li><code>com.ibm.wsif.providers.transformerrt</code></li>
<li><code>org.xmlsoap.schemas.wsdl.wsadie.messages</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
METHOD_CALL
<div class="Text">
<p> The following WSSecurityHelper methods are not available on Liberty: </p>
<ul>
<li><code>getCallerList</code></li>
<li><code>getFirstCaller</code></li>
<li><code>getFirstServer</code></li>
<li><code>getServerList</code></li>
<li><code>addPropagationAttribute</code></li>
<li><code>getPropagationAttributes</code></li>
<li><code>convertCookieStringToBytes</code></li>
<li><code>revokeSSOCookies</code></li>
<li><code>revokeSSOCookiesForPortlets</code></li>
<li><code>getLTPACookieFromSSOToken</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> The following WebSphere Remote Request Dispatcher (RRD) SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.wsspi.rrd</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
METHOD_CALL
<div class="Text"> <span class="SubHeader">Avoid using the deprecated WSSecurityHelper revokeSSOCookies method</span>
<p> This rule flags the following deprecated method from the <span class="Code">com.ibm.websphere.security.WSSecurityHelper</span> class: </p>
<ul>
<li><span class="Code">revokeSSOCookies(HttpServletRequest req, HttpServletResponse res)</span></li>
</ul>
<p>This method is deprecated in traditional WebSphere Application Server Version 8.5 and might be removed in a future release. It is not available on Liberty. </p>
<p> The functionality provided by <span class="Code">WSSecurityHelper.revokeSSOCookies(HttpServletRequest req, HttpServletResponse res)</span> is replaced by the Java Servlet-3.0 specification's <span class="Code">logout()</span> method. The Java Servlet-3.0 <span class="Code">logout()</span> method will perform all of the work that <span class="Code">WSSecurityHelper.revokeSSOCookies(HttpServletRequest req, HttpServletResponse res)</span> performs as well as doing additional state clean up, such as invalidating the session and clearing the security <span class="Code">Subject</span> from the thread. </p>
<p> Use the new method to be compatible on both WebSphere Application Server traditional and Liberty. Also note that with the <span class="Code">logout()</span> method in use, the application requires WebSphere Application Server V8.0 or later. </p>
<p> In the source scanner, the quick fix replaces calls to <span class="Code">revokeSSOCookies(HttpServletRequest req, HttpServletResponse res)</span> with calls to the <span class="Code">logout()</span> method. For example, the following code </p>
<table bgcolor="#F7F8F9" border="1" cellpadding="2px">
<tbody>
<tr>
<td> import javax.servlet.http.HttpServletRequest; <br> <span class="indent2"></span>... <br> <span class="indent2"></span>WSSecurityHelper.revokeSSOCookies(req, res); </td>
</tr>
</tbody>
</table>
<p>is replaced by </p>
<table bgcolor="#F7F8F9" border="1" cellpadding="2px">
<tbody>
<tr>
<td> import javax.servlet.http.HttpServletRequest; <br> <span class="indent2"></span>...<br> <span class="indent2"></span>req.logout(); </td>
</tr>
</tbody>
</table>
<p> For additional information, see </p>
<ul>
<li><a href="https://www.ibm.com/docs/en/was-nd/8.5.5?topic=providers-java-servlet-30-support-security" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/docs/en/was-nd/8.5.5?topic=providers-java-servlet-30-support-security'); return false;"> Java Servlet 3.0 support for security</a> Knowledge Center documentation. </li>
<li><a href="https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.javadoc.doc/web/apidocs/com/ibm/websphere/security/WSSecurityHelper.html" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.javadoc.doc/web/apidocs/com/ibm/websphere/security/WSSecurityHelper.html'); return false;"> Class WSSecurityHelper</a> Java documentation. </li>
<li><a href="https://www.ibm.com/docs/en/was-nd/8.5.5?topic=applications-servlet-security-methods" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/docs/en/was-nd/8.5.5?topic=applications-servlet-security-methods'); return false;"> Servlet security methods</a> Knowledge Center documentation. </li>
</ul>
</div>
METHOD_CALL
<div class="Text">
<p> This rule flags the following method from the <span class="Code">com.ibm.websphere.security.WSSecurityHelper</span> class: </p>
<ul>
<li><span class="Code">getLTPACookieFromSSOToken()</span></li>
</ul>
<p>This method is deprecated in traditional WebSphere Application Server Version 8.5 and might be removed in a future release. It is not available on Liberty. </p>
<p> The functionality provided by <span class="Code">WSSecurityHelper.getLTPACookieFromSSOToken()</span> is replaced by the new method <span class="Code">com.ibm.websphere.security.web.WebSecurityHelper.getSSOCookieFromSSOToken().</span> Note that this new method is in the class <span class="Code">com.ibm.websphere.security.web.WebSecurityHelper,</span> not <span class="Code">com.ibm.websphere.security.WSSecurityHelper.</span> This method will extract the SSO token from the subject of current thread and builds an SSO cookie out of it for use on downstream web invocations. </p>
<p> Use the new method to be compatible on both WebSphere Application Server traditional and Liberty. Also note that with the <span class="Code">getSSOCookieFromSSOToken()</span> method in use, the application requires WebSphere Application Server V8.0 or later. </p>
<p> In the source scanner, the quick fix replaces calls to <span class="Code">WSSecurityHelper.getLTPACookieFromSSOToken()</span> with calls to the <span class="Code">WebSecurityHelper.getSSOCookieFromSSOToken()</span> method. An import statement for <span class="Code">com.ibm.websphere.security.web.WebSecurityHelper</span> is added if needed. For example, the following code </p>
<table bgcolor="#F7F8F9" border="1" cellpadding="2px">
<tbody>
<tr>
<td> import javax.servlet.http.Cookie;<br> import com.ibm.websphere.security.WSSecurityHelper; <br> <span class="indent2"></span>... <br> <span class="indent2"></span>Cookie ltpaCookie = WSSecurityHelper.getLTPACookieFromSSOToken(); </td>
</tr>
</tbody>
</table>
<p>is replaced by </p>
<table bgcolor="#F7F8F9" border="1" cellpadding="2px">
<tbody>
<tr>
<td> import javax.servlet.http.Cookie;<br> import com.ibm.websphere.security.WSSecurityHelper;<br> import com.ibm.websphere.security.web.WebSecurityHelper; <br> <span class="indent2"></span>...<br> <span class="indent2"></span>Cookie ltpaCookie = WebSecurityHelper.getSSOCookieFromSSOToken(); </td>
</tr>
</tbody>
</table>
<p> For additional information, see </p>
<ul>
<li><a href="https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.javadoc.doc/web/apidocs/com/ibm/websphere/security/web/WebSecurityHelper.html" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.javadoc.doc/web/apidocs/com/ibm/websphere/security/web/WebSecurityHelper.html'); return false;"> Class WebSecurityHelper</a> Java documentation. </li>
<li><a href="https://www.ibm.com/docs/en/SSAW57_8.5.5/com.ibm.websphere.javadoc.doc/web/apidocs/com/ibm/websphere/security/WSSecurityHelper.html" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/docs/en/SSAW57_8.5.5/com.ibm.websphere.javadoc.doc/web/apidocs/com/ibm/websphere/security/WSSecurityHelper.html'); return false;"> Class WSSecurityHelper</a> Java documentation. </li>
<li><a href="https://www.ibm.com/docs/en/was-nd/8.5.5?topic=ssa-using-websphere-application-server-api-achieve-downstream-web-single-sign-ltpatoken2-cookie" title="Opens a new window" onclick="javascript:helpWindow('https://www.ibm.com/docs/en/was-nd/8.5.5?topic=ssa-using-websphere-application-server-api-achieve-downstream-web-single-sign-ltpatoken2-cookie'); return false;"> Using a WebSphere Application Server API to achieve downstream web single sign-on with an LtpaToken2 cookie</a> Knowledge Center documentation. </li>
</ul>
</div>
ANNOTATION
<div class="Text">
<p> Liberty supports a subset of the WebSphere Optimized Local Adapters (WOLA) APIs. This rule flags the use of APIs that are unsupported on Liberty. </p>
<p> The Java™ rule flags the following classes related to MBean functions that are unavailable on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.ola.OLAConnectionHandle</code></li>
<li><code>com.ibm.websphere.ola.OLAHeader</code></li>
<li><code>com.ibm.websphere.ola.OLARGE</code></li>
<li><code>com.ibm.websphere.ola.OLARGEInformation</code></li>
<li><code>com.ibm.websphere.ola.OLARGEList</code></li>
<li><code>com.ibm.websphere.ola.OLASearchObject</code></li>
<li><code>com.ibm.websphere.ola.OLAStatusInformation</code></li>
</ul>
<p> The Java rule also flags <code>RemoteHome</code> annotations with <code>com.ibm.websphere.ola.ExecuteHome.class</code> as the remote interface. Liberty ignores the <code>@RemoteHome</code> 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. </p>
<ul>
<li><code>@RemoteHome(com.ibm.websphere.ola.ExecuteHome.class)</code></li>
</ul>
<p> The XML rule flags <code><remote></code> and <code><home></code> elements that contain references to <code>com.ibm.websphere.ola</code> classes. To use WOLA with EJB beans on Liberty, you need to migrate your EJB beans to use EJB 3.0 <code><business-local></code> interfaces, and your EJB class must implement <code>com.ibm.websphere.ola.ExecuteLocalBusiness</code>. </p>
<p> For example, the tool flags the use of WOLA on the remote and home interfaces: </p>
<table class="code">
<tbody>
<tr>
<td> <span class="Code"> <span class="indent"></span><session id="wola_sample"><br> <span class="indent3"></span><ejb-name>WOLA</ejb-name><br> <span class="indent3"></span><span style="font-weight:bolder;"><home>com.ibm.websphere.ola.ExecuteHome</home></span><br> <span class="indent3"></span><span style="font-weight:bolder;"><remote>com.ibm.websphere.ola.Execute</remote></span><br> <span class="indent3"></span><ejb-class>com.ibm.Hello</ejb-class><br> <span class="indent3"></span><session-type>Stateless</session-type><br> <span class="indent3"></span><transaction-type>Container</transaction-type><br> <span class="indent"></span></session><br> </span> </td>
</tr>
</tbody>
</table>
<p> To use WOLA in this application on Liberty, migrate the EJB classes to use the local business interface and update the <span class="FilePath">ejb-jar.xml</span> file as follows: </p>
<table class="code">
<tbody>
<tr>
<td> <span class="Code"> <span class="indent"></span><session id="wola_sample"><br> <span class="indent3"></span><ejb-name>WOLA</ejb-name><br> <span class="indent3"></span><span style="font-weight:bolder;"><business-local>com.ibm.websphere.ola.ExecuteLocalBusiness</business-local></span><br> <span class="indent3"></span><ejb-class>com.ibm.Hello</ejb-class><br> <span class="indent3"></span><session-type>Stateless</session-type><br> <span class="indent3"></span><transaction-type>Container</transaction-type><br> <span class="indent"></span></session><br> </span> </td>
</tr>
</tbody>
</table>
<p> Also note that Java Naming and Directory Interface (JNDI) names of target EJB beans on Liberty use <code>java:</code> naming. Start the Liberty server and check the server log for messages that display the JNDI of the target EJB beans. </p>
<p> For detailed information about WOLA on Liberty, see the <a href="http://www.ibm.com/support/knowledgecenter/SS7K4U_liberty/com.ibm.websphere.wlp.zseries.doc/ae/container_wlp_ola_developing.html" title="Opens a new window" onclick="javascript:helpWindow('http://www.ibm.com/support/knowledgecenter/SS7K4U_liberty/com.ibm.websphere.wlp.zseries.doc/ae/container_wlp_ola_developing.html'); return false;"> Developing applications that use optimized local adapters on Liberty</a> documentation. </p>
</div>
<div class="Text">
<p> Liberty supports some com.ibm.websphere.ola APIs, but there are differences from the support provided on WebSphere Application Server traditional. Review your use of the WOLA APIs to see if the differences affect your application. </p>
<p> Differences include the WOLA support for global transactions, Enterprise JavaBeans (EJB) support, and Java Naming and Directory Interface (JNDI). For detailed information about WOLA on Liberty, see the <a href="http://www.ibm.com/support/knowledgecenter/SS7K4U_liberty/com.ibm.websphere.wlp.zseries.doc/ae/container_wlp_ola_developing.html" title="Opens a new window" onclick="javascript:helpWindow('http://www.ibm.com/support/knowledgecenter/SS7K4U_liberty/com.ibm.websphere.wlp.zseries.doc/ae/container_wlp_ola_developing.html'); return false;"> Developing applications that use optimized local adapters on Liberty</a> documentation. </p>
<p> WOLA support for IBM Information Management Systems (IMS) is introduced in Liberty 16.0.0.3. </p>
</div>
<div class="Text">
<p> The following WebSphere Work Area APIs and SPIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.workarea</code></li>
<li><code>com.ibm.wsspi.workarea</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<span class="SubHeader">The WebSphere Web Services Notification (WS-Notification) APIs are unavailable</span>
<div class="Text">
<p> The following WebSphere Web Services Notification (WS-Notification) APIs are not available on Liberty: </p>
<ul>
<li><code>com.ibm.websphere.sib.wsn</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p> To use the WebSphere XPath, XQuery, and XSLT API, applications must be configured to use the XML thin client JAR file provided by the WebSphere Application Server Feature Pack for XML. <!-- How do they get this feature pack? How do they configure their applications to use it? --> </p>
</div>
<div class="Text">
<p>
The following WebSphere web services APIs and SPIs are not available on Liberty:
</p>
<ul>
<li><code>com.ibm.websphere.webservices</code></li>
<li><code>com.ibm.websphere.websvcs.rm</code></li>
<li><code>com.ibm.websphere.wssecurity</code></li>
<li><code>com.ibm.websphere.cache.webservices</code></li>
<li><code>com.ibm.ws.webservices</code></li>
<li><code>com.ibm.ws.websvcs</code></li>
<li><code>com.ibm.ws.wssecurity</code></li>
<li><code>com.ibm.websphere.wsaddressing</code></li>
<li><code>com.ibm.websphere.wsrf</code></li>
<li><code>com.ibm.wsspi.soapcontainer</code></li>
<li><code>com.ibm.wsspi.webservices</code></li>
<li><code>com.ibm.wsspi.wssecurity</code></li>
<li><code>com.ibm.wsspi.wsaddressing</code></li>
<li><code>com.ibm.wsspi.wsrm</code></li>
</ul>
<p>You must modify the application so that it can run on Liberty.</p>
</div>
<div class="Text">
<p>
The WSDL2Java emitter generates Java classes from JAX-RPC WSDL files. These generated classes are used with JAX-RPC web
services that is not supported on Liberty. These classes can be removed when converting from JAX-RPC to JAX-WS.
</p>
<p>
This rule flags the following WSDL2Java emitter generated classes:
</p>
<ul>
<li><code>*_Deser.class</code></li>
<li><code>*_Helper.class</code></li>
<li><code>*_Ser.class</code></li>
<li><code>*Stub.class</code></li>
<li><code>*Locator.class</code></li>
<li><code>*Information.class</code></li>
</ul>
<p>
For example, if your WSDL file contains an element named Book the WSDL2Java emitter may generate any of the following classes
to be flagged by this rule:
</p>
<ul>
<li><code>Book_Deser.class</code></li>
<li><code>Book_Helper.class</code></li>
<li><code>Book_Ser.class</code></li>
<li><code>BookStub.class</code></li>
<li><code>BookBindingStub.class</code></li>
<li><code>BookLocator.class</code></li>
<li><code>BookServiceLocator.class</code></li>
<li><code>Book_ServiceLocator.class</code></li>
<li><code>BookInformation.class</code></li>
<li><code>BookServiceInformation.class</code></li>
<li><code>Book_ServiceInformation.class</code></li>
</ul>
</div>
© 2015 - 2025 Weber Informatics LLC | Privacy Policy