Monday Oct 14, 2013

Tip to Quickly Test JDeveloper based Customizations Locally

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
About

Follow us on twitter Fusion Applications Extensibility, Customizations and Integration forum Fusion Applications Dev Relations YouTube Channel
This blog offers news, tips and information for developers building extensions, customizations and integrations for Oracle Fusion Applications.

Search

Categories
Archives
« October 2013 »
SunMonTueWedThuFriSat
  
1
2
4
6
7
9
11
12
13
15
16
17
18
19
20
22
24
25
26
27
29
30
31
  
       
Today