WebLogic Server XML file review rules
The XML file review provides a number of rules to detect migration issues with deployment descriptors, web services, and other XML files.
| Rule Name | Rule Description | Automated Fix |
|---|---|---|
| Do not use Kodo PersistenceServerServlet in web.xml |
This rule detects the presence of servlet,
The quick fix removes the servlet along with its servlet mapping elements. |
No |
| Do not use local JNDI names |
This rule detects <local-jndi-name> tags in weblogic-ejb-jar.xml files. The quick fix scans all the projects associated with the application where the local JNDI name is found. If Java code is found that references the local JNDI name, a <ejb-local-ref> is added to that project. The Web or EJB bindings are also updated. |
No |
| Do not use WebLogic servlet filter for XML parsing |
This rule detects the use of an internal WebLogic Server servlet filter in web.xml files. The quick fix removes the servlet filter entry along with its filter mapping entry. |
No |
| Migrate WebLogic login modules |
This rule detects <login-config> elements in the WEB-INF/web.xml file that might indicate that login modules require migration. |
No |
| Use WebSphere bindings to define EJB JNDI names |
This rule detects the <jndi-name> tag in weblogic-ejb-jar.xml files for EJB definitions. The quick fix migrates the value found to the EJB bindings file. |
No |
| Use WebSphere bindings to define EJB local reference JNDI names |
This rule detects <ejb-local-ref> tags in weblogic-ejb-jar.xml files for EJB definitions. The quick fix migrates the value found to the EJB bindings file. |
No |
| Use WebSphere bindings to define EJB reference names |
This rule detects <ejb-ref-name> in weblogic.xml or weblogic-ejb-jar.xml files. The quick fix adds the EJB reference JNDI name to the EJB bindings file. |
No |
| Use WebSphere bindings to define message-driven bean JNDI names |
This rule detects <destination-jndi-name> for message-driven beans. The quick fix sets the destination JNDI name in the EJB bindings file. |
No |
| Use WebSphere bindings to define resource environment reference JNDI names |
This rule detects <resource-env-description> elements in weblogic.xml or weblogic-ejb-jar.xml files. The quick fix adds the resource reference JNDI name to the EJB bindings file. |
No |
| Use WebSphere bindings to define resource reference names |
This rule detects <res-ref-name> elements in weblogic.xml or weblogic-ejb-jar.xml files. The quick fix adds the resource reference JNDI name to the EJB bindings file. |
No |
| Use WebSphere extensions to define transaction timeout seconds |
This rule detect the <trans-timeout-seconds> in weblogic-ejb-jar.xml files. The quick fix defines the timeout value to the EJB extensions file. |
No |
| Use WebSphere extensions to define virtual directory mappings |
This rule detects WebLogic Server virtual directory mapping configuration and migrates entries to use WebSphere file serving. |
No |
| Use WebSphere extensions to define web module context root |
This rule detects the <context-root> element in weblogic.xml files. The quick fix defines the context root value to the Web extensions file. |
No |
| Detect Oracle auto-generated keys |
This WebSphere Application Server traditional rule detects Oracle auto-generated keys defined in the weblogic-cmp-rdbms-jar.xml file. These keys are used for container managed persistence entity beans. The application must be modified to support keys generation. |
No |
| Do not use WebLogic-specific EJB Query Language constructs |
This WebSphere Application Server traditional rule detects query
language elements, |
No |
| Do not use WebLogic-specific JNDI name values or the t3 protocol |
This WebSphere Application Server traditional rule detects non-portable WebLogic Server JNDI lookup values or URLs with the t3 or t3s protocol. |
No |
| Do not use WebLogic web services deployment descriptor |
This WebSphere Application Server traditional rule flags webservices.xml J2EE deployment descriptor files. The quick fix generates an Ant script that uses IBM WebSphere Ant tasks, which generate the appropriate artifacts for the list of web services, based on the information collected from the deployment descriptors. Depending on the deployment descriptor, the fix might also generate the Service Endpoint Interface (SEI) for the service, and add it to the project class path. You can then run the Ant script, copy the generated artifacts to the project, and possibly add additional targets such as the endpoint enabler, for example. |
No |
| Use WebSphere extensions to define CMP mappings |
This WebSphere Application Server traditional rule detects <weblogic-rdbms-jar> elements in weblogic-cmp-rdbms-jar.xml files. The quick fix uses the weblogic-cmp-rdbms-jar.xml file to generate the EJB to RDB mapping files used by WebSphere Application Server for CMP. |
No |
| Use WebSphere extensions to define concurrency strategy |
This rule detects the <concurrency-strategy> element in weblogic-ejb-jar.xml files. The quick fix moves the Exclusive, ReadOnly, Database, and Optimistic options to the EJB extensions file. |
No |
WebLogic used Kodo for its JPA 1.0 provider implementation. Similarly, OpenJPA was the WebSphere default JPA provider for JPA 1.0 and 2.0. The following rules handle WebLogic Server Persistence XML migration to JPA 2.0 or earlier:
| Rule Name | Rule Description | Automated Fix |
|---|---|---|
| Do not use Kodo properties that have no openJPA equivalent |
This rule detects the use of
The quick fix deletes the kodo property from persistence.xml files. |
No |
| Use OpenJPA equivalent property names instead of Kodo-specific property names |
This rule detects the presence of known JPA properties with a name starting with kodo.* in persistence.xml files. The quick fix renames these properties to openjpa.*. |
No |
| Use OpenJPA property values instead of Kodo-specific property values |
This rule detects the JPA properties with kodo-specific values in persistence.xml files. The quick fix changes these values to valid OpenJPA values. |
No |
Starting with JPA 2.1, WebSphere switched to EclipseLink as its default JPA provider. The following rules handle WebLogic Server Persistence XML migration to JPA 2.1 or later:
| Rule Name | Rule Description | Automated Fix |
|---|---|---|
| Do not use Kodo properties |
This rule detects Kodo properties that need to be migrated to EclipseLink. |
No |
The following rules flag any WebLogic Server unhandled or partially handled XML file:
| Rule Name | Rule Description | Automated Fix |
|---|---|---|
| Do not use weblogic.xml file |
This rule flags the weblogic.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use weblogic-application.xml file |
This rule flags the weblogic-application.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use weblogic-cmp-jar.xml file |
This rule flags the weblogic-cmp-jar.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use weblogic-cmp-rdbms-jar.xml file |
This rule flags the weblogic-cmp-rdbms-jar.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use weblogic-diagnostics.xml file |
This rule flags the weblogic-diagnostics.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use weblogic-ejb-jar.xml file |
This rule flags the weblogic-ejb-jar.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use weblogic-ra.xml file |
This rule flags the weblogic-ra.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |