Eai Integration Object To Xml Hierarchy Converter In Siebel

0 views

Skip to first unread message

Message has been deleted

Annice Hemmerling

unread,

Jul 16, 2024, 9:29:48 AM7/16/24

to yhopnymen

the xml does not conform to the xsd fed to siebel to create integration object.
Check the integration object defination and check if the xml tag is defined for any field/object which matches to your xml file tags.
To cross check, work in reverse direction and generate xml hierarchy from integration object and try to compare these two files.

eai integration object to xml hierarchy converter in siebel

Download --->>> https://lomogd.com/2yMIGk

It's time to get stuff done with Yahoo Mail. Just add your Gmail, Outlook, AOL or Yahoo Mail to get going. We automatically organize all the things life throws at you, like receipts and attachments, so you can find what you need fast. Plus, we've got...

IP2016 introduced the REST framework for the webservices. Enterprises modernize its infrastructure and webservices and XML slowly belongs to the museums. We will show you how effectivelly reimplement the SOAP XML webservice into the REST services for more complex service.

In this blog we want to discuss some more complex services. Lets say we had SOAP Webservice to create Activity in the Siebel. This webservice is implemented in quite a complex Siebel workflow and the data were received via XML.

The implementation contains both external and internal integration objects, datamaps, xslt transformations etc. The goal is to expose this webservice to the other systems via REST protocol and not to reimplement all complex business logic. The XML contained external XML reflected in the external Integration Object, during the processing in the workflow was mapped to internal integration object and upserted to the Siebel database.

The Oracle Siebel CRM IP2019 introduced REST capabilities, but they do not yet map the known patterns such as convert json inputs into integration object hierarchy. Until Siebel IP19.5 we couldn't make it work. We decided to make generic approach and expose REST service and internally convert the json input into external integration object hierarchy, which is passed to the existing workflow. So for every existing inbound SOAP Webservice we just implment business service and wrapper workflow, which converts the json into input needed of existing implementation.

2. Define any needed flat mandatory attributes under this method. The structure with the attributes for the activity, which is converted into integration object , put under parent such as parameters in the bellow example.