It's All About the Platform.

  • October 14, 2013

Tip to Quickly Test JDeveloper based Customizations Locally

Vik Kumar
Group Manager
We have been exploring design time customizations on various Fusion Applications and compiled  a list of dependencies that cause deployment failures in the integrated WLS. Below list contains  servlets, filters and EJB reference entries that can be commented in web.xml for testing the customizations locally.

For HCM comment out below in your Customization workspace's web.xml:

Servlet Entries

  • IntegrateTaskFlowWithTask
  • RESTfulAPI
  • PortletProducerResourceServlet

EJB References

  • ess/runtime
  • ess/metadata

For Financials comment out below in your Customization workspace's web.xml:

Filter Entries

  • CardIssuerMDSFilter
  • BankRelationshipsMDSFilter

Servlet Entries

  • IntegrateTaskFlowWithTask
  • PersonImage
  • PersonVCard
  • PortletProducerResourceServlet
  • IntegrateTaskFlowWithTask
  • RESTfulAPI

Please do make sure to comment the entry as well as the mapping in the web.xml. Another very common dependency causing deployment failures in integrated WLS is the missing oracle.apps.common.resource library. The error stack may look like below:

[J2EE:160149]Error while processing library references. Unresolved application library
references, defined in weblogic-application.xml: [Extension-Name:
oracle.apps.common.resource, exact-match: false].'  weblogic.management.DeploymentException:
[J2EE:160149]Error while processing library references
Please read here about deploying it as a shared library to the integrated WLS

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.