I am a not new to webMethods, have spent many years architecting interesting application deployments. But this is my first time diving into flow and web services via webMethods.
I am not sure if I am missing something, due to my lack of experience or if there is an issue or missing step(s).
The goal here is to have webMethods ‘in the middle’ of two systems exchanging web services. As I understand it, this should not be too big a deal.
I have imported a wsdl into the IS. I have created a stub flow to validate the imported wsdl connector can be referenced and generated the web service descriptor to get the ‘webMethods wsdl’… I copied the expected inputs to the original wsdl into the inputs of my stub flow.
All seems to be fine.
I provided the webMethods wsdl to the original developer (who provided me the original application wsdl) just to confirm things were acceptable. They were not.
Here is the original wsdl:
<soap:Envelope xmlns:soap=“http://www.w3.org/2003/05/soap-envelope” xmlns:com=“http://apphost.domain/pub/common” xmlns:inc=“http://apphost.domain/pub/incident”>
Here is the webMethods wsdl:
<soapenv:Envelope xmlns:soapenv=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:get=“http://webMethodshost.domain/flow_test/incident/GetIncidentDetail_WSD” xmlns:inc=“http://apphost.domain/pub/incident” xmlns:com=“http://apphost.domain/pub/common”>
Now, I thought all looked well and via webMethods mapping will be able to get things working just fine.
The app developer has highlighted that the other application host is expecting things is a specific format and the webMethods wsdl will cause issues.
The app developer has asked me to move the “GetIncidentDetail” to be part of the “inc” namespace. Also, Authentication needs to be in the soap header.
Can you more experienced folks point me in the direction how to implement these changes? Again, am I missing something due to my inexperience? or is there a larger issue here?
Thanks for your help.
Additional info: IS 8.2 and Developer 8.2