cancel
Showing results for 
Search instead for 
Did you mean: 

Proxy to SOAP Scenario, payload with the SOAP envelops

Former Member
0 Kudos

Hi ,

We have Scenario like Proxy to SOAP,As per Business requirement they are asking payload with ENVELOP . Like below message

================================================================

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding">

<SOAP-ENV:Header>

<nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true">

<nseps:to>

<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>

</nseps:to>

<nseps:from>

<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>

</nseps:from>

</nseps:endpoints>

<nsprop:properties xmlns:nsprop="urn:schemas-IBX:/docs/property.nsproperty" SOAP-ENV:mustUnderstand="true">

<nsprop:identity>3198841w-fa4d-dafa-2797-89029c15255b</nsprop:identity>

<nsprop:sentAt>2010-01-18T02:42:08Z</nsprop:sentAt>

<nsprop:topic>CostObjectInformation</nsprop:topic>

</nsprop:properties>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

//Payload of the message to be added here.

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

I am trying out this in XSLT, but I am not sure how to add the SOAP Envelops and these Envelops are Static.

Can someone help me out in this.

Joe

Accepted Solutions (0)

Answers (2)

Answers (2)

Shabarish_Nair
Active Contributor
0 Kudos

as mentioned by Mike, note that the SOAP envelop is created by the SOAP adapter itself. So there is no need for you to create the envelop as part of the mapping.

ref: https://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.webservices.d...

that will help you understand a soap message

Former Member
0 Kudos

But if you look at the SOAP Envelop Structure below it is not XI generated SOAP Envelop. IBX (3rd party) has its own standards, so XI has to Produce the SOAP Envelop according to their standards.

I have created the XSD with SOAP Envelop stucture with what ever structure 3rd party wants, but the problem is when Creating the SOPA Envelp tag, where it has a ":" where its not allowing me to create the valid XSD. And at the same time 3rd party is not in position to give us even WSDL file and we are not using Webservice call and they are not able to provide the XSD with SOAP envelop structure.

I thought of going for XSLT and started doing as well with what ever XSD 3rd party has provided, which does not have the SOAP Envelop structure and has only payload XSD structure.

80% of the SOAP Envelop structure is Static, it does not change. Only 2 fields keeps changing. IS there any solution that we can create XSD with the SOAP structure with Special Character ": "or is there any way in doing in XSLT.

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding">

<SOAP-ENV:Header>

<nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true">

<nseps:to>

<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>

</nseps:to>

<nseps:from>

<nseps:address>b2b2ce96-7a92-1000-910f-c0a8b4340001</nseps:address>

</nseps:from>

</nseps:endpoints>

<nsprop:properties xmlns:nsprop="urn:schemas-IBX:/docs/property.nsproperty" SOAP-ENV:mustUnderstand="true">

<nsprop:identity>3198841w-fa4d-dafa-2797-89029c15255b</nsprop:identity>

<nsprop:sentAt>2010-01-18T02:42:08Z</nsprop:sentAt>

<nsprop:topic>CostObjectInformation</nsprop:topic>

</nsprop:properties>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

its a high priority issue.

Thanks in Advance.

Joe.

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

>>>>We have Scenario like Proxy to SOAP,As per Business requirement they are asking payload with ENVELOP

but why do you need to add the envelope with XSLT ? envelope gets added by the SOAP adapter by itself

(if you don't remove it by checking the "do not use envelope" in soap adapter)

just use the standard functionality

Regards,

Michal Krawczyk