Forum Stats

  • 3,826,878 Users
  • 2,260,719 Discussions


Oracle EDQ web services consuming EBS Customer Business objects(complex XML)


Our customer has a requirement to integrate the EDQ web services in their customer interface.The interface is being maintained using Oracle SOA and it works on the concept of Business events which get triggered when a customer record is created or changed in Oracle EBS. This data is captured by the business object which is in the form of a complex XML. The role of EDQ webservice is now to consume this business object in its entirety and cleanse the some part of data in it (Address data, customer info etc. ) and hand it back in the exact XML format in SOA. The business object has to be passed back to Oracle EBS and Legacy systems (to update both systems with the cleansed information) as a JMS message.

We have been using EDQ for conversion purposes(EDQ reads from and to staging tables and it is a one to one attribute mapping and is very straightforward. But is there a way to handle such complex XMLs using EDQ web services? Following is the reply from Oracle for a service ticket raised earlier.

"If you have no control over the XML format provided by the calling system then you can use the EDQ wsdlizer.jar to build a custom web service. This is located in the dnDirector\tools directory and allows you to build a custom web service jar file using an XML schema. You copy the resulting file into the config\webservices directory and it appears as a new realtime source/destination. Depending on the complexity of the schema file you may need to run the wsdlizer with the ‘–nobuckets’ option which allows you to control how the XML is flattened using some custom JavaScript. This will almost certainly be necessary if the XML has many levels of nested elements."

We have not worked with this wsdlizer.jar file earlier and would really appreciate for any detailed guidance in this regard if someone has encountered such a case earlier.

Will be glad to provide with further information if needed.

Thanks in advance.


This discussion has been closed.