Oracle Application 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 custom Oracle Application Shared Libraries |
This rule detects the tag <imported-shared-libraries> in the orion-application.xml file. |
No |
| Do not use Oracle global load-on-startup servlet |
This rule detects servlets that are marked with the <load-on-startup> tag in the global-web-application.xml file. |
No |
| Do not use Oracle servlet invoker |
This rule detects an Oracle Application Server servlet invoker using the <servlet-webdir> tag in the orion-web.xml or global-web-application.xml file. |
No |
| Do not use Oracle-specific web filters |
This rule detects the use of web filters that start with "oracle." defined in the web.xml. The quick fix deletes the filter element. |
No |
| Do not use Oracle-specific web listeners |
This rule detects the use of web listeners that start with "oracle." defined in the web.xml. The quick fix deletes the listener element. |
No |
| Migrate Oracle login modules |
This rule detects login modules that are marked with the <login-modules> tag in the orion-application.xml file. |
No |
| Use WebSphere bindings to define EJB reference names |
This rule detects EJB references in the orion-web.xml or orion-ejb-jar.xml files. The quick fix adds the JNDI name of the EJB reference 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 reference names |
This rule detects resource references in the orion-web.xml or orion-ejb-jar.xm files. The quick fix adds the JNDI name of the resource reference to the EJB bindings file. |
No |
| Use WebSphere configuration to control class loader order |
This rule detects the presence of the search-local-classes-first setting used to control class loading order. |
No |
| Do not use MDB 2.0 listener ports |
This WebSphere Application Server traditional rule detects the message-driven bean (MDB) 2.0 listener ports in the ejb-jar.xml file. |
No |
| Do not use Oracle web services deployment descriptor |
This WebSphere Application Server traditional rule flags oracle-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 enterprise bean to relational database mappings that are used for container-managed persistence (CMP). |
No |
| Use WebSphere extensions to define concurrency strategy |
This WebSphere Application Server traditional rule detects and migrates the concurrency strategy used for EJB persistence. The quick fix locates the concurrency strategy settings in the orion-ejb-jar.xml file and sets equivalent properties in the WebSphere extension file. |
No |
The following rules flag any Oracle Application Server unhandled or partially handled XML file:
| Rule Name | Rule Description | Automated Fix |
|---|---|---|
| Do not use data-sources.xml file |
This rule flags the data-sources.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use global-web-application.xml file |
This rule flags the global-web-application.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use jazn-data.xml file |
This rule flags the jazn-data.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use oc4j-connectors.xml file |
This rule flags the oc4j-connectors.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use oc4j-ra.xml file |
This rule flags the oc4j-ra.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use oracle-webservices.xml file |
This rule flags the oracle-webservices.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use orion-application.xml file |
This rule flags the orion-application.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use orion-application-client.xml file |
This rule flags the orion-application-client.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use orion-ejb-jar.xml file |
This rule flags the orion-ejb-jar.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |
| Do not use orion-web.xml file |
This rule flags the orion-web.xml file so that you can look for any unmigrated elements at the end of the application migration. |
No |