Multiref elements in SOAP

Hi,
When I call a webservice from SAP XI with the SOAP adapter then I get a response message in SAP XI without multiref elements from the webservice.
When I do the same thing with XMLspy I get a correct
message with multiref elements.
What do I wrong in SAP XI?
kind regards,
H. Hendriks

Hi Stefan,
Yes I had set the keep attachment parameter.
kind regards,
H. Hendriks

Similar Messages

The multiRef elements are missing.

hello friends
I'm using the receiver soap adapters for consuming the axis 1.0 web services, in order to do this, i'm using the message types referenced in the wsdl imported.
But, the multiref elements are missing in the response message.
what I must do?
Regards.
Sergio Gómiz

hello Deviprasad !
I already imported the wsdl file like as external definition as WSDL Category Then I reused his message types for making the interface message.
The problem is that not recognizes following response payload (<altaInspeccionReturn href="#id0"/>)...
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <ns1:altaInspeccionResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://mansub.webservice.mansub.gom.com/">
 <altaInspeccionReturn href="#id0"/>
 </ns1:altaInspeccionResponse>
 <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:RespuestaOperacion" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ServicioIntegracionMansub">
 <codigoError xsi:type="xsd:int">0</codigoError>
 <dato xsi:type="xsd:string" xsi:nil="true"/>
 <mensaje xsi:type="xsd:string">inspeccion dada de alta</mensaje>
 </multiRef>
 </soapenv:Body>
</soapenv:Envelope>
In the monitoring adapter (runtime workbench) it appear this payload ...
- <ns1:altaInspeccionResponse xmlns:ns1="http://mansub.webservice.mansub.gom.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<altaInspeccionReturn href="#id0" />
</ns1:altaInspeccionResponse>

Problem SOAP Receiver in PI 7.1 (multiRef elements)

Hello, I need help on this problem.
My need to consume a webservice interface, which has a reference XML response. SAP PI returns me only the reference. I need all the data content.
*Original message consumed SOAP UI.*
I need this data.
from already thank you very much
Edited by: Claudio Enrique León Hernández on Oct 8, 2009 3:39 AM

Hello, I need help on this problem.
My need to consume a webservice interface, which has a reference XML response. SAP PI returns me only the reference. I need all the data content.
*Original message consumed SOAP UI.*
I need this data.
from already thank you very much
Edited by: Claudio Enrique León Hernández on Oct 8, 2009 3:39 AM

Parsing multiref elements

hi!
I am trying to parse xml documents with elements like the following.
 <ns1:fullRequestResponse xmlns:ns1="http://some.name.space">
 <token href="#ID1"/>
 <result href="#ID2"/>
 <charged href="#ID3"/>
 </ns1:fullRequestResponse>...
 <ns1:response id="ID2" xsi:type="ns1:response">
 <result xsi:type="xsd:string">accepted</result>
 <text xsi:type="xsd:string">accepted</text>
 </ns1:response>Using DOM I only get an element with the attribute href="#ID2", the child element ( response ) is not accessible. Do I have to resolve the multiref by myself or can I use DOM (or JDOM, SAX., ...) to do that for me?
cheers,,
Philipp

I am currently faced with a similar issue. The following are the details. Any insights?
*** XML Document ***
<ns1:Body xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/">
<ns1:echoObjectResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://localhost:8080/axis/EchoHeaders.jws" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<ns1:echoObjectReturn href="#id0"/>
</ns1:echoObjectResponse>
<multiRef id="id0" soapenc:root="0" ns1:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<description xsi:type="ns2:string" xsi:nil="true" xmlns:ns2="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<id href="#id1"/>
<name xsi:type="soapenc:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Internet Widget</name>
</multiRef>
<multiRef id="id1" soapenc:root="0" ns1:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:long" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">1</multiRef>
</ns1:Body>
*** Code for parsing ***
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse("c:\\sample.xml");
System.out.println("Printing multi-ref info: " + document.getElementsByTagNameNS("http://localhost:8080/axis/EchoHeaders.jws", "echoObjectResponse").getLength());
//// above prints the value 0
Thanks,
-ac

Name Space deplaration in root element in soap message

My soap client is having problems interpreting the response received from my Java service. When implemented using Endpoint.publish it works, whoever once packaged up inside an WAR file it break my client. After some investigation I found that the response message differs slightly. It seems that the namespace is declared on the root element using JAX-WS 2.0, and within the content body using JAX-WS 2.1. As I am not able to change the soap framework on my client, I am wondering if there is an option I could get either JAX-WS or JAX-B to produce the response message in the working format.
This is the fault generated by Endpoint.publish (Java5 with JAX-WS 2.0):
HTTP/1.1 500 Internal Server Error
Content-length: 507
Content-type: text/xml; charset=utf-8
<?xml version="1.0" ?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns1="http://addressbookserver.j2anywhere.com/">
<soapenv:Body>
<soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>soapenv:Server</faultcode>
<faultstring>Unable to verify license</faultstring>
<detail><ns1:LicenseException>
Unable to verify license
</ns1:LicenseException></detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>This is the fault received from Tomcat (Java5 with JAX-WS 2.1):
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=utf-8
Date: Thu, 19 Jun 2008 22:26:17 GMT
Connection: close
<?xml version="1.0" ?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Server</faultcode>
<faultstring>Unable to verify license</faultstring>
<detail>
<ns2:LicenseException xmlns:ns2="http://addressbookserver.j2anywhere.com/">
Unable to verify license
</ns2:LicenseException>
</detail>
</S:Fault>
</S:Body>
</S:Envelope>Thanks in advance

Those two documents look functionally the same to me. It shouldn't matter whether the namespaces are declared at a higher level than necessary. If you have a client that treats those two documents differently then I would say it's not working correctly.

Presence of multiref tag in soap response message

We are having a problem when we try to call a web service in PI. The web services called is provided by an Axis server.
We tried to use the plain HTTP protocol in the definition of the communication channel as shown here:
Adapter type: SOAP
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Central Adapter Engine
We got the followong error response in SXMB_MONI:
The payload shown in SXNB_MONI is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<ns1:cedstr_obt_cle_elem_v2_Response xmlns:ns1='urn:CEDSTR' soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<tab_cle soapenc:arrayType='ns1:cedstr_cle_elem_v1[3]' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/' xsi:type='soapenc:Array'>
<item href='#id0'/>
<item href='#id1'/>
<item href='#id2'/>
</tab_cle><nb_cle xsi:type='xsd:int'>3</nb_cle><stat_elem href='#id3'/>
<cdr href='#id4'/>
</ns1:cedstr_obt_cle_elem_v2_Response>
The expected payload is:
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Body>
- <ns1:cedstr_obt_cle_elem_v2_Response soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:CEDSTR">
- <tab_cle xsi:type="soapenc:Array" soapenc:arrayType="ns1:cedstr_cle_elem_v1[3]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item href="#id0" />
<item href="#id1" />
<item href="#id2" />
</tab_cle>
<nb_cle xsi:type="xsd:int">3</nb_cle>
<stat_elem href="#id3" />
<cdr href="#id4" />
</ns1:cedstr_obt_cle_elem_v2_Response>
- <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">118406</id_structure_det>
<ordinal xsi:type="xsd:int">2648545</ordinal>
<appareil xsi:type="xsd:string">C3D1E</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">984806</id_structure_det>
<ordinal xsi:type="xsd:int">2723425</ordinal>
<appareil xsi:type="xsd:string">O5C3X</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">1163686</id_structure_det>
<ordinal xsi:type="xsd:int">3144641</ordinal>
<appareil xsi:type="xsd:string">Y0A6B</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:cedstr_stat_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="urn:CEDSTR">
<tension xsi:type="xsd:string">MT</tension>
<nb_concess xsi:type="xsd:int">0</nb_concess>
<nb_restr xsi:type="xsd:int">0</nb_restr>
<localisation xsi:type="xsd:string">DEVILLERS EST DE BEAUREGARD</localisation>
<remarque xsi:type="xsd:string" />
</multiRef>
- <multiRef id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:utlgen_cdr" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns6="urn:CEDSTR">
<succes xsi:type="xsd:int">1</succes>
<code xsi:type="xsd:int">0</code>
<message xsi:type="xsd:string" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
</ns1:cedptr_obt_cle_di_v1_HResponse>
What I can see is that PI seems to ignore the multiref tag in the SOAP response message. Does anybody knows if there is an issue with the mutiref tag in PI ?
Thanks for your help.

The SOAP adapter does not support more than one body child.
If a SOAP message with several body childs arrive, then only the first body child is considered, all other body childs are ignored.
Regards
Stefan

Change element in soap header

hello,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>79630070-BC27-11DC-BD4F-0017A4106568</SAP:MessageId>
<SAP:TimeSent>2008-01-06T07:17:46Z</SAP:TimeSent>
i sent the message in HTTPS,
the problem is the target system can't get SOAP:mustUnderstand="1", the target system can get only SOAP:mustUnderstand="0"
how can i change SOAP:mustUnderstand="1" to SOAP:mustUnderstand="0"
thanks,
Shelly

Hello,
My propousal is as follows:
Go to the involved comunication channel on the integration Builder and Select the option:
"Do not use SOAP Envelope"
Then create your own XSLT mapping program as bellow:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 
 <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
 <SOAP:Header>
 <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:MUSTUNDERSTAND="0" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
 <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
 <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
 <SAP:MessageId>79630070-BC27-11DC-BD4F-0017A4106568</SAP:MessageId>
 <SAP:TimeSent>2008-01-06T07:17:46Z</SAP:TimeSent>
 <SPECIFICMAPPINGPROGRAM/>
 </SAP:Main>
 </SOAP:Header>
 </SOAP:Envelope>
</xsl:stylesheet>
Import the archive and select it in the Interface Mapping.
Good luck!!

SOAP request has multiref/soapenc:Array elements

Hi there - I am receiving a request that is structured using multiref elements. When I examine the SOAP request in the diagnostic log, I see all of the data, but when it gets to the mediator, only the elements in id0 are populated and the rest of the elements are empty. I have seen a few posts that OSB does not handle multirefs, but wanted to see if anyone has solved the problem in another way.
I am currently using jDev 11.1.1.2 but moving soon to 11.1.1.5. Here is the associated wsdl, an example of the raw SOAP request (which has all of the data) and then the input to my mediator (with the empty elements):
The problem is occurring with the "Keys" type which is a soapenc:Array. In this case I get the id0 Keys element but the rest of the Keys elements (id1, id2, id3 and id4) are empty when it gets to my mediator.
WSDL_
 <s:complexType name="Document">
 <s:sequence>
 <s:element name="Keys" type="tns:Keys" />
 <s:element name="IdentifierDisplay" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="contextType" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="autodownload" type="s:boolean" minOccurs="0" maxOccurs="1" />
 <s:element name="ObjectId" type="tns:ObjectId" />
 <s:element name="Type" type="tns:Type" minOccurs="0" maxOccurs="1" />
 <s:element name="EditURL" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="Description" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="Date" type="s:date" minOccurs="0" maxOccurs="1" />
 <s:element name="Time" type="s:time" minOccurs="0" maxOccurs="1" />
 <s:element name="Status" type="tns:Status" minOccurs="0" maxOccurs="1" />
 <s:element name="DocumentLocators" type="tns:DocumentLocators" minOccurs="0" maxOccurs="1" />
<s:element name="content" type="s:base64Binary" minOccurs="0" maxOccurs="1" />
 </s:sequence>
 </s:complexType>
 <s:complexType name="Type">
 <s:sequence>
 <s:element name="Keys" type="tns:Keys" />
 <s:element name="IdentifierDisplay" type="s:string" minOccurs="0" maxOccurs="1" />
 </s:sequence>
 </s:complexType>
 <s:complexType name="Status">
 <s:sequence>
 <s:element name="Keys" type="tns:Keys" minOccurs="0" maxOccurs="1" />
 <s:element name="Name" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="Value" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="Date" type="s:date" minOccurs="0" maxOccurs="1" />
 <s:element name="Time" type="s:time" minOccurs="0" maxOccurs="1" />
 </s:sequence>
 </s:complexType>
 <s:complexType name="ElectronicFileLocator">
 <s:sequence>
 <s:element name="Keys" type="tns:Keys" minOccurs="0" maxOccurs="1" />
 <s:element name="IdentifierDisplay" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="contextType" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="filename" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="fileDateTime" type="s:string" minOccurs="1" maxOccurs="1" />
 <s:element name="fileLocation" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="fileSize" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="serverAddress" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="serverDescription" type="s:string" minOccurs="1" maxOccurs="1" />
 <s:element name="serverType" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="serverPlatform" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="serverVendor" type="s:string" minOccurs="0" maxOccurs="1" />
 </s:sequence>
 </s:complexType>
 <s:complexType name="PhysicalDocumentLocator">
 <s:sequence>
 <s:element name="Keys" type="tns:Keys" minOccurs="0" maxOccurs="1" />
 <s:element name="IdentifierDisplay" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="contextType" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="location" type="s:string" minOccurs="0" maxOccurs="1" />
 <s:element name="Date" type="s:date" minOccurs="1" maxOccurs="1" />
 </s:sequence>
 </s:complexType>
<s:complexType name="DocumentLocators">
 <s:sequence>
 <s:element name="ElectronicFileLocator" type="tns:ElectronicFileLocator" minOccurs="0" maxOccurs="1" />
 <s:element name="PhysicalDocumentLocator" type="tns:PhysicalDocumentLocator" minOccurs="0" maxOccurs="1" />
 </s:sequence>
</s:complexType>
 <s:complexType name="Keys">
 <s:complexContent mixed="false">
 <s:restriction base="soapenc:Array">
 <s:attribute wsdl:arrayType="s:string[]" ref="soapenc:arrayType" />
 </s:restriction>
 </s:complexContent>
 </s:complexType>
XML input from diagnostic.log Note: bold elements are missing once it gets to my mediator_
<?xml version = '1.0' encoding = 'UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:create xmlns:ns1="http://www.replaced.com/edms" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<Document href="#id0"/>
</ns1:create>
<multiRef xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="http://www.replaced.com/edms/types" id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:Document">
<Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array">
<Keys xsi:type="xsd:string">DENVER</Keys>
<Keys xsi:type="xsd:string">CAP</Keys>
<Keys xsi:type="xsd:string" xsi:nil="true"/>
</Keys>
<IdentifierDisplay xsi:type="xsd:string">2011-SITE-000011</IdentifierDisplay>
<contextType xsi:type="xsd:string">application/xml</contextType>
<autodownload xsi:type="xsd:boolean">false</autodownload>
<ObjectId href="#id1"/>
<Type href="#id2"/>
<Description xsi:type="xsd:string">skipper7</Description>
<EditURL xsi:type="xsd:string" xsi:nil="true"/>
<Date xsi:type="xsd:date">2011-11-03</Date>
<Time xsi:type="xsd:time" xsi:nil="true"/>
<Status xsi:type="ns2:Status" xsi:nil="true"/>
<DocumentLocators href="#id3"/>
</multiRef>
<multiRef xmlns:ns3="http://www.replaced.com/edms/types" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:DocumentLocators">
<ElectronicFileLocator href="#id4"/>
<PhysicalDocumentLocator xsi:type="ns3:PhysicalDocumentLocator" xsi:nil="true"/>
</multiRef>
*<multiRef xmlns:ns4="http://www.replaced.com/edms/types" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:Type">*
*<Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array">*
*<Keys xsi:type="xsd:string">DENVER</Keys>*
*<Keys xsi:type="xsd:string">CAP</Keys>*
*<Keys xsi:type="xsd:string" xsi:nil="true"/>*
*</Keys>*
*<IdentifierDisplay xsi:type="xsd:string">Inspection Notice</IdentifierDisplay>*
*</multiRef>*
*<multiRef xmlns:ns5="http://www.replaced.com/edms/types" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:ObjectId">*
*<Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array">*
*<Keys xsi:type="xsd:string">DENVER</Keys>*
*<Keys xsi:type="xsd:string">CAP</Keys>*
*<Keys xsi:type="xsd:string" xsi:nil="true"/>*
*</Keys>*
*<IdentifierDisplay xsi:type="xsd:string">2011-SITE-000011</IdentifierDisplay>*
*<Value xsi:type="xsd:string"/>*
*<contextType xsi:type="xsd:string">application/xml</contextType>*
*</multiRef>*
*<multiRef xmlns:ns6="http://www.replaced.com/edms/types" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:ElectronicFileLocator">*
*<Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array">*
*<Keys xsi:type="xsd:string">DENVER</Keys>*
*<Keys xsi:type="xsd:string">CAP</Keys>*
*<Keys xsi:type="xsd:string" xsi:nil="true"/>*
*</Keys>*
*<IdentifierDisplay xsi:type="xsd:string" xsi:nil="true"/>*
*<contextType xsi:type="xsd:string">application/xml</contextType>*
*<filename xsi:type="xsd:string">ExternalAPOService.wsdl</filename>*
*<fileDateTime xsi:type="xsd:string">2011-11-03T16:20:46</fileDateTime>*
*<fileLocation xsi:type="xsd:string">ExternalAPOService.wsdl</fileLocation>*
*<fileSize xsi:type="xsd:string">24084</fileSize>*
*<serverAddress xsi:type="xsd:string" xsi:nil="true"/>*
*<serverDescription xsi:type="xsd:string">skipper7</serverDescription>*
*<serverType xsi:type="xsd:string" xsi:nil="true"/>*
*<serverPlatform xsi:type="xsd:string" xsi:nil="true"/>*
*<serverVendor xsi:type="xsd:string" xsi:nil="true"/>*
*</multiRef>* </soapenv:Body>
</soapenv:Envelope>
XML input when looking at the input to my mediator in em_
<Document>
 <Keys soapenc:arrayType="xsd:string[3]" xsi:type="soapenc:Array" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
 <Keys xsi:type="xsd:string">DENVER</Keys>
 <Keys xsi:type="xsd:string">CAP</Keys>
 <Keys xsi:type="xsd:string" xsi:nil="true"/>
 </Keys>
 <IdentifierDisplay xsi:type="xsd:string" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">2011-SITE-000011</IdentifierDisplay>
 <contextType xsi:type="xsd:string" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">application/xml</contextType>
 <autodownload xsi:type="xsd:boolean" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">false</autodownload>
 <ObjectId href="#id1" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
 <Type href="#id2" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
 <Description xsi:type="xsd:string" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
 <EditURL xsi:type="xsd:string" xsi:nil="true" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
 <Date xsi:type="xsd:date" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">2011-11-03</Date>
 <Time xsi:type="xsd:time" xsi:nil="true" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
 <Status xsi:type="ns2:Status" xsi:nil="true" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
 <DocumentLocators href="#id3" xmlns:ns1="http://www.replaced.com/edms" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</Document>
Edited by: mi**** on Nov 4, 2011 7:24 AM

Hi PeterFL,
Well Done!
Thank you very much for sharing the solution to us.
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SOAP Response with WS-Addressing elements

Hi All,
I have an issue with the response message of SOAP - PI - RFC Sync scenario.
In the request of the SOAP message, we receive following header(WS-Addressing) Elements in the SOAP Header part of the envelope.
<wsa:Action wsu:Id="wssecurity_signature_id_281" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
http://partnername/interfacedetails
</wsa:Action>
<wsa:MessageID wsu:Id="wssecurity_signature_id_285" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
uuid:463BF10F-0126-4000-E000-604DAC152914
</wsa:MessageID>
<wsa:RelatesTo wsu:Id="wssecurity_signature_id_283" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
urn:uuid:02875597AE9A49ABAB1229340545618
</wsa:RelatesTo>
Now the issue is the, our interface partner(who actually sends the SOAP Request), wants SOAP response containing the above WS-Addressing elements.
Is it possible with SAP PI?. Can anybody help me with this.
By the way, our interface( SOAP-PI-RFC Sync ) working fine. We just need these elements inside SOAP Response.
Thanks in advance.
Kind Regards,
Prasad.

Hi Prasad,
I am not sure if the problem is solved.
I guess you are talking about a scenario in which a non-SAP consumer sends a request to SAP ABAP provider. The consumer requests the enabling of WS-Addressing. The answer nothing is required to configure the ABAP provider, which will send back a SOAP response either with WS-A or without depending if WS-A is sent by the consumer or not. That might be the case that you can see these headers with the SXMB_MONI.
Hope this helps.
Regards,
Wei

Set SOAP header element while invoking WS thru ADF webservice Data control

Experts,
I am trying to invoke/call a webservice (using ADF web service data control ) which is expecting custom element in SOAP-Header. I want to know the steps needed to set SOAP-Header custom element when using ADF web service data control. SOAP-Header custom element will be string type, something like
<soap:Header><element1>String</element1></soap:Header>
Thank you,
Ashish

Hi,
extend the SOAPProvider class
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPMessage;
import oracle.adf.model.adapter.AdapterException;
import oracle.adfinternal.model.adapter.webservice.provider.soap.SOAPProvider;
public class CustomSOAProvider extends SOAPProvider {
 public CustomSOAProvider() {
 super();
 //expose protected method to public
 public void handleRequest(SOAPMessage soapMessage) throws AdapterException {
 super.handleRequest(soapMessage);
 //Expose protetcted method to public
 public void handleResponse(SOAPMessage soapMessage) throws AdapterException {
 super.handleResponse(soapMessage);
 }And configure it in the DataControls.dcx file of your WS DC project
<AdapterDataControl id="..."
xmlns="http://xmlns.oracle.com/adfm/datacontrol">
<Source>
<definition xmlns="http://xmlns.oracle.com/adfm/adapter/webservice"
name="..." version="1.0"
provider="adf.sample.wsdc.CustomSOAProvider"
wsdl="http://...">
Frank

How to create SOAP Header elements using SAAJ??

I am facing a problem when adding header elements under SOAP Header
using SAAJ(api).
I want to create a structure as following:
I get a empty SOAP header obejct by writing code--> SOAPHeader header
= envelope.getHeader();
But not able to add SOAP header elements as specified in example
below. I tried but its giving me error as
"HeaderElements must be namespace qualified"
CAN ANYBODY TELL ME THAT HOW TO ADD HEADER ELEMENTS USING SAAJ??
<SOAP:Header>
<AccountNumber>123</AccountNumber>
<AuthorisationCode>test111</AuthorisationCode>
<Source>abc</Source>
<Market>01</Market>
</SOAP:Header>

I'm including this comment from some code I've just written after wrestling with this for hours (I've actually left it on another post as well). The upshot of it all is that you have to include a namespace URI when creating a header in SAAJ:
 NOTE: SOAP 1.1 requires that all header entries be namespace-qualified to
 namespace URI's. The SAAJ 1.2 implementation requires a Name object with
 the namespace URI to make this happen even if the prefix used is already
 visible by being declared higher in the document (e.g. in the Envelope).
 However, the namespace URI is not present in the serialized header element
 as long as it was declared higher in the document. In order to create a
 header element without a prefix (to conform to a web service definition
 that doesn't use a prefix in its headers, for example), leave the prefix
 null in the addHeaderElement() method.
 For example, with a SOAPHeader 'hdr':
 //first create the name
 Name name = env.createName("my-local-name", null, "my-URI");
 //then create the header element
 SOAPHeaderElement he = hdr.addHeaderElement(name);
 This would result in an XML element that looked like this:
 <my-local-name xmlns="my-URI"/>
 This would allow SAAJ developers to create a header for a service that
 only expected a local name in its header elements (as many do!). As long
 as the service doesn't choke on the attribute (validation! evil!), this
 should work.
 Rob Kemmer
 01/12/2005

Consume web service in ABAP proxy with SOAP header

Hi Thomas ,
I am trying to consume web service in ABAP . I have followed the procedure from one of your web blog <a href="/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap a Developer's Journal Part XIV - Consuming WebServices with ABAP</a> . (640 release).
I need to pass SOAP header along with SOAP body. As you mentioned I have used if_wsprotocol_ws_header interface to pass header but it is still failing.
Please see below code and please give some direction to fix the issue.
1.Create ABAP proxy for WSDL (http://ws.strikeiron.com/SwanandMokashi/StockQuotes?WSDL). It has created structures only for SOAP body.
2.Create Logical port
3.Create following program to call proxy
REPORT zproxy.
DATA: ref_stock TYPE REF TO zzco_stock_quotes_soap ,
 ws_header TYPE REF TO if_wsprotocol_ws_header,
 name TYPE string,
 namespace TYPE string.
TRY.
 CREATE OBJECT ref_stock
get WS_HEADER protocol
 ws_header ?= ref_stock->get_protocol('IF_WSPROTOCOL_WS_HEADER').
set somehow header as iXML-DOM tree
 DATA: ixml TYPE REF TO if_ixml,
 xml_document TYPE REF TO if_ixml_document,
 xml_root TYPE REF TO if_ixml_element,
 xml_element TYPE REF TO if_ixml_element,
 xml_node TYPE REF TO if_ixml_node.
 DATA l_xstring TYPE xstring.
 DATA l_string TYPE string.
 FIELD-SYMBOLS <fs_xstring> TYPE xstring.
Additional Header:
 CONCATENATE
'<soap:Header>'
'<s1:LicenseInfo xmlns:s1="http://ws.strikeiron.com">'
'<s1:RegisteredUser>'
'<s1:UserID>[email protected]</s1:UserID>'
'<s1:Password>aaaaaaaa</s1:Password>'
'</s1:RegisteredUser></s1:LicenseInfo>'
'</soap:Header>' INTO l_string.
convert to xstring
 l_xstring = cl_proxy_service=>cstring2xstring( l_string ).
 IF NOT l_string IS INITIAL.
 create iXML DOM document from XML xstring
 CALL FUNCTION 'SDIXML_XML_TO_DOM'
 EXPORTING
 xml = l_xstring
 IMPORTING
 document = xml_document
 EXCEPTIONS
 invalid_input = 1
 OTHERS = 2.
 IF sy-subrc = 0 AND NOT xml_document IS INITIAL.
 xml_root = xml_document->get_root_element( ).
 xml_element ?= xml_root->get_first_child( ).
 add header element by element to SOAP header
 WHILE NOT xml_element IS INITIAL.
 name = xml_element->get_name( ).
 namespace = 'http://swanandmokashi.com' . "xml_element->get_namespace_uri( ).
 IF NOT xml_element IS INITIAL.
 ENDIF.
 ws_header->set_request_header(
 name = name
 namespace = namespace
 dom = xml_element ).
 xml_element ?= xml_element->get_next( ).
 ENDWHILE.
 ENDIF.
 ENDIF.
CATCH cx_ai_system_fault .
ENDTRY.
*Call soap body using abap proxy class.
DATA: get_quotes TYPE zzget_quotes_soap_out .
DATA: get_quotes1 TYPE zzget_quotes_soap_in .
get_quotes1-quote_ticker = 'GE'.
TRY.
 CALL METHOD ref_stock->get_stock_quotes
 EXPORTING
 get_quotes1 = get_quotes1
 IMPORTING
 get_quotes = get_quotes.
CATCH cx_ai_system_fault .
CATCH cx_ai_application_fault .
ENDTRY.
4.It is throwing cx_ai_system_fault error.
SOAP details:
Input:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding" >
<soap:Header>
<s1:LicenseInfo xmlns:s1="http://ws.strikeiron.com">
<s1:RegisteredUser>
<s1:UserID>[email protected]</s1:UserID>
<s1:Password>aaaaaaaa</s1:Password>
</s1:RegisteredUser>
</s1:LicenseInfo>
</soap:Header>
<soap:Body>
<tns:GetQuotes xmlns:tns="http://swanandmokashi.com">
<tns:QuoteTicker>GE</tns:QuoteTicker>
</tns:GetQuotes>
</soap:Body>
</soap:Envelope>
Thanks,
Kavitha.

Hi ,
Thank you for the response. Did you passed user email and password ([email protected] /aaaaaaaa) part of licenseinfo->resisteredUser along with Quoteticker GE in analyzer?
<a href="http://www.strikeiron.com/Analyzer/OnlineAnalyzer.aspx?WSDL=http://ws.strikeiron.com/SwanandMokashi/StockQuotes?WSDL">ANALYZER</a>
Thanks,
Kavitha.

Split-Join, unable to set SOAP:HEADER in OSB at Invoke Service Component.

Hi Experts,
i created a Split-join for parallel processing and invoke third party services, but this service requires some mandatory elements in soap:header like WS-Addressing and, WSA-TO and some security infomation, but i don't know how to pass header in invoke service step. Please help me to setup Header for Invoke services in split join.
Please help me to resolve this issue.
Thanks
Ankit

see this :https://forums.oracle.com/thread/951618
not the most fancy way, but you can create some sort of wrapper proxyservice in front of your business service to make it work

SOAP Adapter: DO not use soap envelope

Hi Guys
I have a scenario, which calls a webservice from my ABAP Proxies, the twist in this is that SOAP request expects license info into the header of SOAP envelope, I could achive this by XSLT mapping in the receiver SOAP adapter I selected the option "Do not use SOAP envelope" and could do the call.
Due to this the response received from the webservice is treated as payload, as shown below...
response message payload:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Header xmlns="http://schemas.xmlsoap.org/soap/envelope/">
 <SubscriptionInfo xmlns="http://ws.strikeiron.com">
 <LicenseStatusCode>0</LicenseStatusCode>
 <LicenseStatus>Valid license key</LicenseStatus>
 <LicenseActionCode>0</LicenseActionCode>
 <LicenseAction>Decremented hit count</LicenseAction>
 <RemainingHits>18</RemainingHits>
 <Amount>0</Amount>
 </SubscriptionInfo>
</Header>
<soap:Body>
 <getRateResponse xmlns="CurrencyRates">
 <getRateResult>44.945</getRateResult>
 </getRateResponse>
</soap:Body>
</soap:Envelope>
and when i am trying to do the response mapping, it is not able to read the value.
Anyone having any idea, on how we could do this.
Thanks
Dheeraj

Hi
I am sorry for replying in so late, was busy with some projects.
I got few mails and this post is cathing up again, so thought of giving the solution I followed without any adapter module or anything, simple plain XSLT mapping.
Integration Repository
1. Created data type and message type for Outbound Interface
2. Imported the WSDL
3. Created an XSD out of the sample response I got by calling the WSDL (this you can do from any tool available, i used the strikeiron website), pls refer below to see the XSD below, and you will have to use the message type envelope from it.
4. Most Important step, created 2 XSLT mappings, one for request and the other for response., Pls refer below for both these mappings.
5. did the interface mapping
Integration Directory
1. pls configure your scenario as normaly you do, and while you configure the communication channel for your soap receiver, make sure you click on the do not use soap envelop option.
thats it done.
XSLT Request Mapping
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:template match="/">
 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Header>
 <LicenseInfo xmlns="http://ws.strikeiron.com">
 <RegisteredUser>
 <UserID>xyz</UserID>
 <Password>xyz</Password>
 </RegisteredUser>
 </LicenseInfo>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 <getConversion xmlns="CurrencyRates">
 <FromCurrencyCode>
 <xsl:value-of select="//fromCurrency"/>
 </FromCurrencyCode>
 <ToCurrencyCode>
 <xsl:value-of select="//ToCurrency"/>
 </ToCurrencyCode>
 <Amount>1</Amount>
 </getConversion>
 </SOAP-ENV:Body>
 </SOAP-ENV:Envelope>
 </xsl:template>
</xsl:stylesheet>
XSLT Response Mapping
<?xml version='1.0' ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:a="CurrencyRates" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <xsl:template match="/">
 <ns0:MT_Cur_res xmlns:ns0="http://www.april.in/WebService/SOAPHeader">
 <Rate>
 <xsl:value-of select="soap:Envelope/soap:Body/a:getConversionResponse/a:getConversionResult"/>
 </Rate>
 </ns0:MT_Cur_res>
 </xsl:template>
</xsl:stylesheet>
Webservice Response XSD
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://ws.strikeiron.com" xmlns:ns2="CurrencyRates">
<xs:import namespace="CurrencyRates" schemaLocation="ns2.xsd"/>
<xs:import namespace="http://ws.strikeiron.com" schemaLocation="ns1.xsd"/>
<xs:element name="Envelope">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="soap:Header"/>
 <xs:element ref="soap:Body"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="Header">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ns1:SubscriptionInfo"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="Body">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ns2:getConversionResponse"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
</xs:schema>
let me know in case somebody gets stuck somewhere for this scenario.
Take Care
Dheeraj

SOAP Sender System in SLD

Hi
Im doing a SOAP-XI-JDBC scenario
Im getting request from a 3rd part system to XI through Webservice provided by WSDL file
Now i have to create a sender SOAP adapter . For this do i need to make an entry of the sending system in my SLD..
Do i need to create a Business system or Business Service
If so what would be the details
Thanks
Keerthi

To add more points to Rajesh
<soap:address location="http://yhsapi01:50000/XISOAPAdapter/MessageServlet?channel=:BS_FILE_SENDER:CCT_WebService_2_WebService_Sender_H1309&version=3.0&Sender.Service=BS_FILE_SENDER&Interface=http%3A%2F%2Fyash.com%2Fh1309%2FWebService_2_WebService%5EMI_A_OUT_+SendSMSToIndia_H1309" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
In the above sample example soap:address element specify the address to access the XI. test tool like soapUI read the wsdl and try to connect to the WebService provider(here XI) using the address specified in the soap:address element and soap:action attribute in soap:operation because soap:action identifies the specific operation in the webservice.

Multiref elements in SOAP

Similar Messages

Maybe you are looking for