WS Addressing elements in a SOAP request sent via SOAP sender adapter

Hi guys,
I have a requirement (Proxy->PI->SOAP) for sending a soap request using the WS addressing elements in the request header. As I went through a documentation to SOAP sender adpter there is no option for this. WS-A is supported in the WS adapter, but the target web service does not support WS-RM, so this is not an option.
Do you have any hint?
Thanks,
Peter

You can create your own SOAP header in mapping or use Axis framework for this.
Regards
Stefan

Similar Messages

I need to secure SOAP message sent into SOAP adapter, how to?

Hi guys,
My scenario uses SOAP and I need to secure this SOAP message sent into SOAP adapter. As I have read in the documentation, HTTPS is possible only on the SOAP receiver adapter. But my is SENDER.
COuld you help me please, how to solve it? Or post some link? Or, if you have your own approach, to let me know?
Thanx, Peter

Hi,
you can use SSL with the sender adapter. Please see the extract of the SOAP Adapter FAQ (Note #856597) below:
<b>Q:</b> Can I use SSL for my sender adapter?
<b>A:</b> Yes. Normally, the SOAP adapter servlet runs on the engines HTTP port. But you can activate the engine's HTTPS port so that this servlet can receive messages sent to the HTTPS port. See the documentation about the J2EE engine's security configuration.
I am afraid, I haven't yet tried this myself, so you will need to consult the J2EE documentation.
Regards,
HC

Async r3- xi- soap problem.. no soap msg sent from SOAP receiver adapter

Hi guys!
I have an issue with SOAP scenario. I have ABAP Proxy->XI->SOAP async scenario. When I send msgfrom r3, it arrives into XI, but no SOAP message is sent to the target url. In the SXMB monitor, the flag is delivered The status of adapter is not valid. error: target url is invalid. messages crash at timeout. But when I test it from other tools, the target web service worx fine. One more info: we use stand-alone adpater engine. I tried it also on the integrated one, but it didn't work.
Sync scenarios work fine: SOAP->XI->R3->XI->SOAP.
Any ideas, what could be wrong? Are there some special requirements, for message interfaces (do they need 2 b sync??) or something else?
Thanx, Olian.

Hi Michal!
First, I even didn't know about this monitoring tool it's gr8.
Well, I found error: MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction:
Any idea?
I'm going to study something about it, but if you know, let me pls info!
Thanx a lot!
Olian

Flex sending corrupt SOAP request

I've created a PHP5 SOAP webservice and am trying to call a
method from flex. I get a fault from the Flex app that says
faultString="HTTP request error"
faultCode="Server.Error.Request"
The SOAP request received by the server is as follows (which
I think explains why the server responded with an error):
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body/>
</SOAP-ENV:Envelope>
It is missing all the body parameters. What could cause an
empty request like this?
The relevant AS:
public var _webServiceLoaded:Boolean = false; // flag noting
when wsdl has been loaded
public var _myService:WebService = new WebService();
public function initWS():void {
_myService.wsdl = "
http://foreignserver.com/seminar_service.wsdl";
_myService.loadWSDL();
_myService.echoArgs.addEventListener("result",
echoResultHandler);
_myService.addEventListener("fault", faultHandler);
_myService.addEventListener('load',WSLoad);
public function send_attendee_email():void {
_myService.echoo("qwerty"); // should just return the same
string we send; echoo spelled with extra o
And my wsdl:
<?xml version="1.0"?>
<definitions
xmlns="
http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:tns="
http://foreignserver.com/seminar_service.php"
xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"
xmlns:soapenc="
http://schemas.xmlsoap.org/soap/encoding/"
targetNamespace="
http://foreignserver.com/seminar_service.php">
<message name="echooInput">
<part name="echo" type="xsd:string"/>
</message>
<message name="send_attendee_emailInput">
<part name="sem_date" type="xsd:string"/>
<part name="sem_first" type="xsd:string"/>
<part name="sem_last" type="xsd:string"/>
<part name="sem_title" type="xsd:string"/>
<part name="sem_company" type="xsd:string"/>
<part name="sem_phone" type="xsd:string"/>
<part name="sem_email" type="xsd:string"/>
<part name="pdf_filename" type="xsd:string"/>
</message>
<message name="echooOutput">
<part name="return" type="xsd:string"/>
</message>
<message name="send_attendee_emailOutput">
<part name="return" type="xsd:string"/>
</message>
<portType name="seminarPortType">
<operation name="echoo">
<input message="tns:echooInput"/>
<output message="tns:echooOutput"/>
</operation>
<operation name="send_attendee_email">
<input message="tns:send_attendee_emailInput"/>
<output message="tns:send_attendee_emailOutput"/>
</operation>
</portType>
<binding name="seminarBinding"
type="tns:seminarPortType">
<soap:binding xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
style="rpc" transport="
http://schemas.xmlsoap.org/soap/http"/>
<operation xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/"
name="echoo">
<input xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/">
<soap:body xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
use="encoded" encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/">
<soap:body xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
use="encoded" encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
<operation xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/"
name="send_attendee_email">
<input xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/">
<soap:body xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
use="encoded" encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/">
<soap:body xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
use="encoded" encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<service name="seminarService">
<port xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/"
name="seminarPort" binding="tns:seminarBinding">
<soap:address xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
location="
http://foreignserver.com/seminar_service.php"/>
</port>
</service>
</definitions>

This behavior (empty SOAP request sent to server) stemmed
somehow from my wsdl file. I'm uncertain what the specific problem
was, but when I rebuilt the wsdl from scratch using a different
model, the SOAP request from Flex was properly formed.

Setting timeout for SOAP requests in a webservice client

I am trying to set the timeout for a synchronous SOAP request sent to a Web Service deployed on weblogic 8.1 SP2. I tried setting timeout thru bindinginfo setTimeout() and also javax.xml.rpc.Stub _setProperty(). Both of them seem to be not working. I set the value to as low as 1 sec but i still donot get a timeout. Other properties/method from these two classes work fine though (like endpointaddress property in javax.xml.rpc.Stub and setVerbose flag to true in BindingInfo).
Can someone please help.
Thanks in Advance
srini

Our application calls the webservice provided by another company over the internet using the ssl. We use the wsdl url of the webservice on the destination while creating the port. If the destination is not available statement which creates the port blocks for around 4 minutes.
I think the first network call gets the wsdl from the remote server. Thus we encounter delays before getting the stub created. How can I timeout such a calls.
try {
port = (new ServiceName_Impl(remoteWsdlURL)).getServiceNameSoap();
} catch (IOException e) {

How to test SOAP request using XML SPY

Hi,
1. I am new to WebServices concept, I have downloaded the wsdl file and now I need to test the SOAP requests using XML Spy. However, when I try to test the SOAP request generated by XML Spy I receive an error "Internal Error: Session is not available. Aborting" , How do I go ahead to generate the session, Is there a way I can provide the Username and password in the XML Spy to generate something like session.
2. The second problem that I am facing is when I import the WSDL in XML Spy and generate the SOAP request, for all the fields xml tags gets populated with "aaaaaaaaaaaa" kind of data through out. Am i doing something wrong ? Is there some step while creating a SOAP request that I am missing becasue of which the gibbrish data is being populated as default ?
Please Help !
Thanks .

I got my SOAP Requests tested using SOAP UI .. However I am still looking for ways to test it using XML SPY.
In the SOAP UI Tool just do right click and select Add WS Security Token ..
Thanks :)

Sending a SOAP request with binary attachment

hi all,
I am sending a SOAP request from a SOAP client SOAP UI with a binary attachment ( image file as an attachment ) and creating a file on the receiver side with attachment.
But how do i see this attachment in XI and do i have to specify some additional configuration in my receiver or sender adapter modules.
Regards ,
Loveena.

creating a file on the receiver side with attachment.
Is this working? Receiver file adapter does not support attachment.
But how do i see this attachment in XI
In the pipeline steps, under payload, you will find two entries, one for payload and other for attachment.
Regards,
Prateek

SOAP Request to "XISOAPAdapter/MessageServlet" or"sap/xi/engine?type=entry"

Hi,
I created a webservice whichs creates an idoc from an orders05 xml file.
I created a wsdl file and try it out with xml spy. It works fine.
However I have a question.
If I send the SOAP Request to:
http://host:port/XISOAPAdapter/MessageServlet?channel=PARTY:PARTY_Application:CC_PARTY_Application_SOAP_SND
its working fine.
If I send the SOAP Request to:
http://host:port/sap/xi/engine?type=entry?channel=PARTY:PARTY_Application:CC_PARTY_Application_SOAP_SND
it is not working.
In the second case I can see my message in the monitor and I found my orders05 xml in the payload. However the message has no information about the sender, the application and the communication channel. So I got a lot of errors.
I thought that both are url are doing the same with soap requests, the first is the adapter engine j2ee port and the other the abap stack http port.
Could someone explain the differences to me and why the information is lost when using the abap port?
Many thanks,
Nils Kloth

Hi,
In the 2. case I think there shoudnt be two question marks.
"http://host:port/sap/xi/engine?type=entry?"
Shouldnt it be like this:
"http://host:port/sap/xi/engine?type=entry:"
Hope it helps (Please inform if it works)
Regards,
Arman

How to use SOAP sender adapter

Hi all
i have configured the SOAP sender adapter. Now my 3rd party needs to send me a soap message.
I have checked that the status at the following URL is OK:
http://host:port/XISOAPAdapter/MessageServlet?channel=:MXII_Web_Service:SOAP_MXII_Sender.
This is fine, however
I am unsure of the following:
1. Does XI make a wsdl available to the 3rd party?
2. Where does my 3rd party send the soap message to?
3. Is the SOAP message sent via a query string?
4. Do I need to create a web service?
Thanks for all your help in advance
Clinton

Hi Moorthy
Thanks for your answer.
The problem was solved, we used .Net to write a webservice to our wsdl.
I have now another problem.... When the message comes into XI it shows that no receiver found(RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC). If I just test the scenario with a file adpter as Sender, and Receiver it is fine, but when using the SOAP adapter as Sender, it gives me the no receiver found message.
Any help with this issue will be appreciated.
Thanks again
Clinton

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

SOAP request being sent only half sometimes

Hi All,
Sometimes, the SOAP request being sent (By Clicking a Button) has all the fields filled with data like say for example,
<doc:contact>
                 <gen:gender>Female</gen:gender>
                 <gen:firstName>FNAME</gen:firstName>
                 <gen:middleName>Middle</gen:middleName>
                 <gen:lastName>LNAME</gen:lastName>
                 <gen:dateOfBirth>1970-05-01T15:35:47.384-05:00</gen:dateOfBirth>
   </doc:contact> But sometimes, it just has
<doc:contact>
               <gen:gender>Female</gen:gender>
   </doc:contact> Missing the firstName, middleName, lastName, and dateOfBirth which should not be happening. Any idea as what might be causing this? The code I am using every time to send the SOAP request is same.
Thanks.
Edited by: RaviUTA on Jun 17, 2009 9:12 PM
Edited by: RaviUTA on Jun 17, 2009 9:17 PM

RaviUTA wrote:
Missing the firstName, middleName, lastName, and dateOfBirth which should not be happening. Any idea as what might be causing this? The code I am using every time to send the SOAP request is same.Whenever you send a SOAP Message on a connection it will be sent in serialized format. So each byte of the message will be sent one by one at the last. So if it is problem of sending the SOAP message on the connection then you might have got something like this as an
incomplete SOAP Message:*
<doc:contact>
<gen:gender>Female</gen:gender>
<gen:firstName>FNA
But this looks different:*
<doc:contact>
<gen:gender>Female</gen:gender>
</doc:contact>For above problem you should investigate at the code where you are building SOAP Message.
RaviUTA wrote:
the SOAP request being sent (By Clicking a Button) has all the fields filled with data like say for example,
<doc:contact>
<gen:gender>Female</gen:gender>
<gen:firstName>FNAME</gen:firstName>
<gen:middleName>Middle</gen:middleName>
<gen:lastName>LNAME</gen:lastName>
<gen:dateOfBirth>1970-05-01T15:35:47.384-05:00</gen:dateOfBirth>
</doc:contact>
Sorry if you are aware of this but one silly suggestion at last *:)*, The document you have given above is not look like SOAP Message.
Thanks,
Tejas

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.

How to control the location of the SOAP:address element in the WSDL

I have an EJB exposed as webservice in WebLogic 10.3. Further, the EJB has been annotated with the WebService annotation as in:
@WebService(name = "S_CALCULATORname", serviceName = "S_CALCULATORserviceName",
targetNamespace = "http://tempuri.org/SCalculator/")
@Stateless(name = "S_CALCULATOR")
public class S_CALCULATOR_Beanxxxxxx
The location attribute of the SOAP:address element in the WSDL document generated by the Test Client facility is of the form
http://host:port/ejb-java-class-name/service-name-attribute-value as in:
<soap:address location="http://123.4.5.678:1234/S_CALCULATOR_Beanxxxxxx/S_CALCULATORserviceName" />
Is there a way to control the value of the context root portion of the URL, ejb-java-class-name in this case, either using annotations or deployment descriptor files?
thanks in advance for any replies,
octavio

Hi,
While building the WebService Application you can use the following ANT task...
<target name="build-service4">
<jwsc
srcdir="src"
destdir="output/TestEar">
<jws file="examples/webservices/jwsc/TestServiceImpl.java">
<WLHttpTransport contextPath ="TestContext" serviceUri="TestServiceUri" portName="TestServicePortHTTP"/>
</jws>
</jwsc>
</target>
Or if you are developing JAXRPC EJB based WebService in that case you can even define the Context root using *@weblogic.jws.WLHttpTransport* annotation....
@WLHttpTransport(contextPath="simple", serviceUri="SimpleService", portName="SimpleServicePort")
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Feb 4, 2010 10:22 PM

Calling SOAP Request from XML Spy

I have published PLSQL web service at Oracle 10g AS.
The web service runs at http://localhost:7201/reqProcess with processRequest as method being exposed.
This web service takes the string as input and return XMLTYPE as out parameter.
Now When I am trying to pass SOAP XML from XMLSPY to above url I am getting folloing errors.
1) I get http error: couldnot post the file /reqProcess/ on server 'localhost' (500)
2) I get SOAP Error as
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <SOAP-ENV:Fault>
               <faultcode>SOAP-ENV:Client</faultcode>
               <faultstring>No Deserializer found to deserialize a 'http://wsi.nat.zz.com/2005/06/StandardHeader/:m0:standardHeader' using encoding style 'null'. [java.lang.IllegalArgumentException]</faultstring>
               <faultactor>/reqProcess</faultactor>
          </SOAP-ENV:Fault>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Please help..

Hi Quwang ur help needed
My requirement ...
1) PLSQL as web service : I succesffuly deployed PLSQL Procedure as Web service at 10 10g. The PLSQL takes string (CLOB) as input convert that into XML and store in table and return XMLTYPE as output.
When I am accesing PLSQL WS using browser I am able to send string (basically XML format) as a input and able to receive the result back (SOAP envelop)
2)WS Invocation : After PLSQL WS published I need to pass the SOAP XML which is generated from XYX wsdl file to the PLSQL WS published above. For this req I was using XML Spy to test this. (In actual the clinet will be Sieble that will send SOAP XML to PLSQL WS).
Initially I was generating the SOAP XML from XYZ.wsdl and was directly sending that to PLSQL URL. I was getting error as I described initially.
Next I tried to generate the SOAP request from the PLSQL WS wsdl file and inside the parameter I am sending the SOAP XML as string to the IN paramater of PLSQL WS. This time I am getting some different errors. The first error is same as http error: couldnot post the file /balprocess/balprocess/operation?processRequest on server 'localhost' (500)
and second error is SOAP fault as follows
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <SOAP-ENV:Fault>
               <faultcode>SOAP-ENV:Server</faultcode>
               <faultstring>java.sql.SQLException: ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00210: expected '<' instead of '"'
Error at line 1
ORA-06512: at "SYS.XMLTYPE", line 0
ORA-06512: at "SCOTT.BAL_A_PROCESS", line 16
ORA-06512: at line 1
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)</faultstring>
               <faultactor>/balprocess/balprocess</faultactor>
          </SOAP-ENV:Fault>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
For ur reference I am pasting the PLSQL WSDL file and the SOAP request xml that I am sending to PLSQL WS URL.
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="bal_a_process"
targetNamespace="http://bal.request.process/bal_a_process.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://bal.request.process/bal_a_process.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd1="http://bal.request.process/bal_a_process.xsd" >
<documentation>
WSDL for Service: bal_a_process, generated by Oracle WSDL toolkit (version: 1.1)
</documentation>
<types>
<schema targetNamespace="http://bal.request.process/bal_a_process.xsd" xmlns:tns="http://bal.request.process/bal_a_process.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:dom="http://xmlns.oracle.com/2001/XMLSchema/DOM">
<complexType name="bal_request_process_bal_a_processUser_processRequest_Out">
<all>
<element name="outresponsexmlOut" type="dom:org.w3c.dom.DocumentFragment"/>
</all>
</complexType>
</schema>
</types>
<message name="processRequestOutput">
<part name="return" type="xsd1:bal_request_process_bal_a_processUser_processRequest_Out"/>
</message>
<message name="processRequestInput">
<part name="param0" type="xsd:string"/>
</message>
<portType name="bal_a_processPortType">
<operation name="processRequest">
<input message="tns:processRequestInput"/>
<output message="tns:processRequestOutput"/>
</operation>
</portType>
<binding name="bal_a_processBinding" type="tns:bal_a_processPortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="processRequest">
<soap:operation soapAction="urn:bal-request-process-bal_a_process/processRequest"/>
<input>
<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:bal-request-process-bal_a_process"/>
</input>
<output>
<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:bal-request-process-bal_a_process"/>
</output>
</operation>
</binding>
<service name="bal_a_process">
<port name="bal_a_processPort" binding="tns:bal_a_processBinding">
<soap:address location="http://localhost:7200/balprocess/balprocess"/>
</port>
</service>
</definitions>
Request I am sending to PLSLQ WS URL
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <SOAP-ENV:Body>
          <processRequest xmlns:m="urn:bal-request-process-bal_a_process" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <param0 xsi:type="xsd:string">     "<a>"aaa"</a>"     </param0>
          </processRequest>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I above SOAP request XML i m testing "<a>"aaa"</a>" as XML string. but this is also getting failed. In actual this will be SOAP XML request from some other XYZ wsdl file.
Quwang ur help needed urgently.
Regards

Web Service operation not in SOAP request

Hi There,
I have a problem with the SOAP receiver adapter.
I have created an external definition and uploaded a wsdl file. Several messages have been created out of the file.
In my mapping I fill the message structure from the wsdl file. When I send the message to the Web Service I get an error back.
The reason for this error seam to be a missing tag under the SOAP:Body element. Because when I create a SOAP request with the XMLSPY, it looks like this:
<SOAP:Body>
<m:setVendor xmlns:m="http://..." ...>
<ns8:v xmlns:ns8="http://...">
But in the message from the XI adapter the <m:setVendor..> tag is missing:
<SOAP:Body>
<ns8:v xmlns:ns8="http://...">
This m: tag seems to be the operation of the web service.
Has anybody an Idea how to solve this?
Is the error in the SOAP adapter or in the message definition?
By the way, can I display the complete SOAP message that has been sent out from the adapter with any XI tool (including SOAP header)?
BR,
Jürgen

Jurgen
I have exactly the same problem in a RFC -> RFC Adapter -> XI -> SOAP Adapter -> Web Service scenario.
What we see is that the external vendor wants the SOAP to be in "documet-literal wrapped" whereas XI is returning is as "document literal".
**I don't want to change the original wsdl file because it was provided by our business partner and a modification could cause problems when release update.
But I have build a workaround with an XSL stylesheet as a second mapping step in my Interface Mapping. The stylesheet adds the missing operation tag into the XML message.**
Even in our case we dont want to change wsdl, the operation & soap body are going as two parts we want the soap body in operation,i think this can be achieved by xsl stylesheet,Can u please brief us about xsl stylesheet as a second mapping step in interface maping.I dint work on xsl before......
Advance thanx for ur help
Sriram

WS Addressing elements in a SOAP request sent via SOAP sender adapter

Similar Messages

Maybe you are looking for