[techman]

Hi All

We are integrating EBusiness with OTM using BPEL . the problem here that the concurrent program "SyncRefDataToOtm.runProgram" in EBusiness does not generate the correct root for the message which should be sent to the service published in BPEL . the generated message missing the root element "<WshSendRefDataStlToOtmProcessRequest>" . Do we have any configurations or any way in Ebusiness to add the root element"<WshSendRefDataStlToOtmProcessRequest>" to the generated message. Here is the proper messages which we need for the service (including "<WshSendRefDataStlToOtmProcessRequest>" root element)

Thanks

<WshSendRefDataStlToOtmProcessRequest>
<input>
<entityType>CARRIER</entityType>
<entityIdList>
<entityId>1634781</entityId>
<entityId>1634767</entityId>
</entityIdList>
<parentIdList>
<entityId>220822</entityId>
<entityId>220858</entityId>
</parentIdList>
<securityContext>
<ticket>D4E897132ECF7675348428139179C3F3</ticket>
<proxyServer/>
<proxyPort/>
<dbConn/>
<opCode>refOpCode</opCode>
<argKey>refArgKey</argKey>
</securityContext>
<appsContext>
<userId/>
<respId/>
<respAppId/>
</appsContext>
</input>
</WshSendRefDataStlToOtmProcessRequest>

[techman]

We are using EBS CU2. I have tried webservices and got it to start the BPEL process, but the data mapping fails. (I think this is because of an extra tag in the XML when using webservices) . we are missing the root element when we synch the carriers . can you please let me know how can I fix it

thanks

[chrisplough]

Could you provide some more details, such as the OTM version (should be OTM v5.5 CU02 or higher -- preferably OTM v5.5 CU03 RU02) and the version of BPEL.

Also - many times carrier sync issues are linked to configuration issues within the OTM Profile options configured within EBS, or the configuration of the BPEL server -- including the GLogXML.xml and GLogXML.wsdl files necessary to get the base mapping working.

Thanks,
Chris

[techman]

Chris

Here are the versions which we are using

OTM 5.5 CU3
EBS 11.5.0 CU2
BPEL 10.1.2.0,2

Our main problem that EBS does not generate the root element as the service expect . when we add the root element and push the element from BPEL consol then it succeed .
Please guide me to the EBS OTM consfigutation to let EBS aware that OTM using a specific schema

Thanks

[jeff.depaul]

Assuming you've applied all necessary OTM related patches to your EBS instance and configured all EBS Profile Options correctly.

Not clear if you are submitting from the BPEL consol or from concurrent program in EBS directly (which calls BPELSoapInvoker from .class file) or both?

FYI, the concurrent processes in EBS call .class files which do invocation of the BPEL webservices - there is little to no control over their submission once you launch the process in EBS.

To note, we were using 10.1.2 Fusion and found several bugs - eventually had to upgrade to 10.1.3.3 where we are currently.

Try clearing the WSDL cache on the BPEL console before submitting and see if it works first time. Also, bounce the container and see if works first time after bounce?

One other note was that we found several challenges with the ticket authentication for the main BPEL process and ultimately commented it out completely (since both systems are secured behind firewall). Ours kept returning authentication: False. I noticed in your xml ticket authentication being sent is why I mention.

Hopefuly something above helps.

[techman]

this issue has been resolved by applying an EBS patch to let the concurrent program send
the correct XML structure to BPEL

Thanks for all of you for helping me

[chrisplough]

Could you please post the EBS patch number, so that others can reference?

Thanks,
Chris