Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I need to call a web-service (looks like a special web service, of some compaque_nsk_oss, I have no control over upgrading/changing that WS).
The wsdl of that webservice looks like this:
wsdl of DummyPinService
I could call the “DummyPinService” using soapUI
SoapUI call works great
Expt1: tESBConsumer using tXmlMap for payload fails. Looks like the tXmlMap is not providing Headers to ESBConsumer . Repository metadata was used for soapRequest.
Error: Error Unmarshalling Request.
tESBConsumer - payload - ErrorUnmarshallingRequest
Also tried ..
Expt2: Create tXmlMap-payload + tXmlMap-header = tMap_request -> tESBConsumer
Observation: <Header> section seems correct . I do not see <Envelop>, <Body> in the logged request.
Error : Error Unmarshalling Request.
ErrorUnmarshallingRequest">Header+Payload -> ErrorUnmarshallingRequest
What should I do to get the same effect as payload supplied to soapUI?
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:compaq_nsk_oss_SoapHeader" xmlns:urn1="urn:cpq_tns_ODINITS-RETRIEVE-DUMMYPIN">
<soapenv:Header>
<dummyTag>1</dummyTag>
</soapenv:Header>
<soapenv:Body>
<urn1:ODINITS-RETRIEVE-DUMMYPIN>
<urn1:header_data>
<urn1:table_type>07</urn1:table_type>
<urn1:sql_error>0</urn1:sql_error>
<urn1:guardian_error>0</urn1:guardian_error>
<urn1:eda_error>0</urn1:eda_error>
<urn1:occurs_count>0</urn1:occurs_count>
<urn1:total_rec_count>0</urn1:total_rec_count>
<urn1:more_to_come>Y</urn1:more_to_come>
</urn1:header_data>
<urn1:rec_create_timestamp>1900-01-01:00:00:00.000000</urn1:rec_create_timestamp>
<urn1:key_data_dummypin>
<urn1:dummypin>0</urn1:dummypin>
</urn1:key_data_dummypin>
</urn1:ODINITS-RETRIEVE-DUMMYPIN>
</soapenv:Body>
</soapenv:Envelope>
Thanks
Espresso
Hello,
The structure of payload is not correct for you when import it in tXmlMap?
Did you create Service -> Import Existing WSDL with 'Import WSDL schemas on finish' checkbox?
Best regards
Sabrina