Specifying SOAP action

Hello
I am accessing a webservice using SAAJ API
I have to specify the soapaction parameter
how can i specify the soap action parameter using the SAAJ API
Please help
Thanks
Shiva

Try
message.getMimeHeaders().addHeader("SOAPAction","\"http://tempuri.org/......\"");
message.saveChanges();If it works, send a thought to billsutton.

Similar Messages

The SOAP action specified on the message, '', does not match the HTTP SOAP

Error Message: " The SOAP action specified on the message, '', does not match the HTTP SOAP Action"
we need establish webservice link with our vendors, they are on windows platform and we are on java.
they gave us this URL:
http://mesadstage.webhop.net/MesadSCService/EBOrderService.svc?wsdl
I create a project in Netbeans, then add Web Service Client, put the URL in, after the some configuration and source code generation, i put these codes in the public void main(String[]), it always returned the error msg:
Error Message: "The SOAP action specified on the message, '', does not match the HTTP SOAP Action, 'http://tempuri.org/IEBOrderService/GetData'. "
what was wrong? any thing that I din configured? or it caused by different platforms???
h2. error message (stack trace)
javax.xml.ws.soap.SOAPFaultException: The SOAP action specified on the message, '', does not match the HTTP SOAP Action, http://tempuri.org/IEBOrderService/GetData'.
at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1326)
at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1052)
at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMarshaller.demarshalFaultResponse(DocLitWrappedMethodMarshaller.java:659)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:577)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:520)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:386)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:171)
at $Proxy11.getData(Unknown Source)
at javaapplication7.Main.a(Main.java:28)
at javaapplication7.Main.main(Main.java:43)
h2. source code:
try {
org.tempuri.EBOrderService service = new org.tempuri.EBOrderService();
org.tempuri.IEBOrderService port = service.getWSHttpBindingIEBOrderService();
java.lang.Integer value = Integer.valueOf(0);
java.lang.String result = port.getData(value);
System.out.println("Result = " + result);
} catch (Exception ex) {
System.out.println("Error = " + ex.getMessage());
ex.printStackTrace();
}

Try to rebuild the index file of the troubled folder.
Right-click the folder - Properties - Repair Folder

WSDL without SOAP Action (BTS.Operation?)

Hi
I got a WSDL without SOAP Action specified. I'm able to generate XSDs, set up a send port and call an operation. Since I was calling a single web operation then I set up my Action at send port WCF config to be
http://localhost/CarService/updateLocation, i.e. [service URL]/[operation name].
My problem now is that I need to call two separate operations from that web service by using BTS.Operation property; one is still
updateLocation and the other one is removeLocation. How can I specify Action in send port WCF config when SOAP Action is missing in WSDL? I tried specifying different values but none of them were successful.
Ex.
<BtsActionMapping>
<Operation Name="updateLocation" Action=""/>
<Operation Name="removeLocation" Action=""/>
</BtsActionMapping>
Kind regards
A.H.

Hi,
How are going to call these web-methods. Are your going to call these two methods from the same Orchestration. Or are you going to call these methods from two different send ports by content-based routing (send port filter).
In BizTalk, this instruction (SOAP Action) is set by assigning a value to WCF.Action context property. You can specify WCF.Action property in two ways:
Single Action Format
Action Mapping Format
The way you have been calling before "http://localhost/CarService/updateLocation" is called Single Action Format. Now you have use the Action mapping format.
In Action mapping format, you map the WCF.Action context is “mapped”/resolved from another context property BTS.Operation. So if you call from the Orchestration, set the BTS.Operation approirately to resolve the URL in the config. i.e if you have config
like this:
<BtsActionMapping>
<Operation Name="updateLocation" Action="http://localhost/CarService/updateLocation"/>
<Operation Name="removeLocation" Action="http://localhost/CarService/removeLocation"/>
</BtsActionMapping>
In your orchestration, if you set the WCF.Action to "removeLocation", WCF.Action would be resolved to "http://localhost/CarService/removeLocation". In orchestration, you set the
WCF.Action context, by setting the logical send port's operation name. Refer to this article for more info:http://www.fortuvis.com/blog/biztalk-and-wcf-soap-action/
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

PI 7.1 SOAP Action parameters in SOAP request?

Hi all,
I have to implement an IDOC->PI->XML interface to transfer some master data. After performing the mapping, the mapped data needs to be sent to the target system using a SOAP request via a webservice.
On PI, I specified the URL for the WS in a SOAP-oriented Communication Channel. In the parameter "SOAP Action" of this CC, I entered the relevant method name to be used to transfer the mapped data. However, this method requires 2 parameters:
- applicationName: this is the name of the target structure used in the Message Mapping
- xmlMessage: this is the actual mapped message string
So my question is: how can I bind these 2 parameters in my PI design and configuration?
Thanks for your help,
Eric

there can be one WS having many actions....which means one WS can be used in multiple interfaces.
However, this method requires 2 parameters:
- applicationName: this is the name of the target structure used in the Message Mapping
- xmlMessage: this is the actual mapped message string
If I get it correctly, you have to actually set the SOAP action before you send the message to the WS....and you want to do it in SAP PI?
so your action is something like http://something.abcd/applicationName/xmlMessage and you have to set the things here?
If yes, then you can use the Dynamic Configuration (adapter specific message attributes...ASMA) in SOAP channel (UDF in mapping) and set this ASMA THeaderSOAPACTION
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
String a = http://something.abcd/applicationName/xmlMessage //set the value of actual action here
conf.put(key, a);
return "";
Regards,
Abhishek.

Can Soap Action be dynamically substituted in receiver side soap Action ?

Hi all
I am trying to place Action in Soap Receiver adapter.
I could see the THeaderSoapAction and the action I have specified in Dynamic Configuration and that action is not getting triggered
I was going through previous posts and Raj was mentioning that there was some problem with Soap Receiver adapter while dynamically placing Soap Action.
Is it so? Has anyone dynamically passed Soap Action using Adapter specific parameters?
If its cannot be achieved with ASP, What is the best alternate to this ?
Thanks and Regards,
Nikhil.

Have not tried this option, but theoretically it should work using the Adapter Specific message attributes
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
Regards,
Prateek

What does SOAP action do?

Hi All,
From hep.sap, i have got a very few knoweldge abt SOAP Action. i.e.,"Specify the SOAP action. The action species the value for the SOAPAction in Web service messages.".
Can any one elaborate SOAP Action purpose, since we are calling Webservice through SOAP URL.
Thanks

Hi ,
it is like a function that web service can perform.
you find the SOAP action from WSDL file at tag soap:operation:
If more than one message type is described in the WSDL, several SOAP actions might also be defined. Check for the correct operation name. If no SOAP action is defined in the WSDL, you can leave the parameter in the receiver channel empty.
Regards,
Rohit
pls reward points if found useful...

Calling a web service from a portal application / SOAP Action

Hallo,
Ich möchte aus einer Portal Applikation auf einen Web Service zugreifen.
Dafür habe ich mit dem Wizard "Portal Service from Wsdl file - Client side"
eine Portal Service erzeugt, auf den ich dann zugreife.
Leider wird dabei ein Fehler ausgegeben (Stacktrace-Ausschnitt s.u.).
Ich habe ein Posting zu dem Fehler hier im SDN gefunden, leider hatte dort niemand eine Antwort. Vielleicht hat inzwischen jemand eine Idee?
Das Feld soapaction ist in der soapconfig.xml leer angegeben (soapaction="").
Es ändert aber nichts an der Fehlermeldung, wenn ich dort etwas eintrage.
Ein weiterer Gedanke ist, dass die soapaction, die wenn ich es richtig verstehe eine URL auf die web service methode enthalten soll, im Grunde dynamisch sein sollte, da der Web Service lokal in dem Portal läuft, auf dem die Applikation gerade deployed ist. Auf den Web Service wird mit WebDynPro erfolgreich zugegriffen (dynamisch). Meine Vermutung ist, dass hier das Problem liegt und es entweder mit diesem Wizard nicht möglich ist oder ein Bug vorliegt.
Also ist die Frage: Wie erzeuge ich dasselbe für eine Portal-Applikation?
Ich hoffe, dass mir jemand mit einer Antwort oder Hinweisen wo man weiterforschen kann, weiterhelfen kann.
Freundliche Grüße,
Daniel Dehnhard
Stacktrace:
Component finished with error: (com.sapportals.portal.prt.service.soap.exception.PRTFaultEnvelopeVersion)
java.lang.IllegalArgumentException: The SOAP Action "" include in the soap request not corresponding to the Portal service method.
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.processParams(PRTSOAPBodyElement.java:253)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.init(PRTSOAPBodyElement.java:190)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.(PRTSOAPBodyElement.java:56)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBody.init(PRTSOAPBody.java:94)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBody.(PRTSOAPBody.java:36)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPEnvelope.init(PRTSOAPEnvelope.java:113)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPEnvelope.(PRTSOAPEnvelope.java:54)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPMessage.processSOAPMessage(PRTSOAPMessage.java:58)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPMessage.(PRTSOAPMessage.java:40)
at com.sapportals.portal.prt.service.soap.SOAPService.call(SOAPService.java:180)
at com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:209)
at de.enviam.ep.egk.km.webservicewrapper.Z_EP_EM_EGK_CustomerGroupToCRMData.getCustomerGroup2CrmDataByGPNr(Z_EP_EM_EGK_CustomerGroupToCRMData.java:218)
at de.enviam.ep.egk.km.imp.EPImpSchedulerTask.resolveGroupId(EPImpSchedulerTask.java:764)

Hi,
I am accessing a web service from a Portal Component through a Portal Web Service. First i created a web service, then a portal web service which is made to access the wsdl file of the web service. Now i access the Portal Web Service from a Portal Component. Now i am getting an error as,
Exceptionjava.lang.IllegalArgumentException: The SOAP Action "" include in the soap request not corresponding to the Portal service method.
The code which i wrote in component is below
String text = "word";
FuncHelloResponse res=new FuncHelloResponse();
FuncHello fn= new FuncHello() ;
fn.setName(text);
res= ( (INewPortal) PortalRuntime.getRuntimeResources().getService(INewPortal.KEY)).FuncHello(fn);
response.write(res.getResponse());
Can any one solve this problem?

PI 7.1 multiple operation interface and SOAP action doubt

Hi guys,
I'm trying to implement a scenario, where I have a single outbound (sender side) interface with multiple operations (as 7.1 allows). The problem is afetr the WSDL generation I have the same SOAP action for each operation. Standardly there should be unique SOAP action per operation, but how to achieve it?
And another question - is it ok to use SOAP sender adapter for this interface?
Thanks for your help,
Olian

Hi Olian,
>>The problem is afetr the WSDL generation I have the same SOAP action for each operation. Standardly there should be unique SOAP action per operation, but how to achieve it?
I dont think you need to have separate action, the Operation Name inside Service Interface differentiate the Request type. Also when you send SOAP message to PI, you are sending it to either
http://host:port /XISOAPAdapter/MessageServlet?channel=p:s:c
(where host is the host name, port is the port number, p is the optional party name, s the service name, and c is the channel name, respectively.The URL given above is valid for 3.0/7.0/7.1.)
or * http://host:port /XISOAPAdapter/MessageServlet?senderParty=FP& senderService=FS& interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace *
(7. 10 onwards a new URL syntax is also valid and is recommended to be used. )
>>And another question - is it ok to use SOAP sender adapter for this interface?
Yes
Regards
Suraj
Edited by: S.R.Suraj on Sep 8, 2009 6:23 AM

DynamicConfiguration - Comma is appended in start of Soap Action

HI All,
I am setting soapAction in receiver communication channel using DynamicConfiguration.
I performed following Configuration in receiver SOAP adapter.
Advanced Tab -> Check 'Use Adapter Specific Message Attributes' -> Check 'Variable Transport Binding' ->
Variable Header (XHeaderName1) = THeaderSOAPACTION
SOAP Action in General Tab is empty
I am using following code snippet in UDF under message mapping.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
String soapAction = "http://abc.com/acon/service/1.0/IServiceOut/AddNote";
conf.put(key, soapAction);
return "";
Now while executing scenario using SOAPUI tool, at runtime i get following soap error message -
soap fault: The message with Action ', http://abc.com/acon/service/1.0/IServiceOut/AddNote' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).
I observed that in soapAction "," (comma) is being appended in starting. I believe this additional comma is causing problem. How can we remove this automatically appended comma from Soap Action?
Thanks in anticipation.
- Gopi

Hi,
We are able to solve additional comma (,) problem in start of SOAPAction. Thanks for your inputs.
But now we are facing another problem which contains 2 SOAPActions in HTTP Headers as shown below.
POST /MyService/MyService.svc HTTP/1.0
Accept: */*
Host: training.com:8080
User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
content-id: <soap-001CC4FC74A51EE18DF87E8066A44800.sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 277
SOAPACTION:
SOAPACTION: http://abc.com/acon/service/1.0/IServiceOut/AddNote
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Header/>
<SOAP:Body>
some body message
</SOAP:Body>
</SOAP:Envelope>
Please provide inputs to remove empty SOAP Action from HTTP Headers.
Do i need to set any parameter in receiver channel to suppress it?
- Gopi

Missing soap action in the soap axis receiver adapter ?

Hi Guys,
I could not find the soap action field in the soap receiver adapter and i followed the OSS note
Note 1054986 - SOAP (Axis) receiver adapter's SOAPAction field missing
Please apply the following patch and use the handler parameter defaultSOAPAction for the XI30OutboundHandler handler in the request chain. This handler parameter can be configured as a module parameter for the HandlerBean module associated with this handler. It is noted that this module parameter takes precedence over the channel parameter for SOAPAction if this field is available.
For SP12
XI ADAPTER FRAMEWORK CORE 7.0
Support Package 12, Patch Level 1 (SAPXIAFC12P_1.SCA)
we are on SP15 so i think the option should be available ?
Do i need to add this parameter in the Module Configuration ?
Moduel Key : ?
Parameter Name: handler.type ---> is this right
Parameter Value ---> ?
we need to validate the user id and pw on IIS for NTLM authentication. Any help regarding developong the handlers would be great
any help would be appreciated.
Thanks,
Srini

Srinivas,
You are on the right path...........yes that is the right note for this issue.
The problem is this is not a general fix that comes with all service packs as the axis adapter is not used a lot, that being said.if you dont see it with sp15..i would safely go apply this fix and see if it works..else you might have to open an oss note for the same...
Hope that helps..
Regards
Ravi Raman
P.S: On my home system..i did apply the fix and i was on a much higher sp level ..i saw some errors..in the logs but nothing a restart couldent fix..

Dynamic Configuration of SOAP Action

Hello Everyone,
I am currently working on a project which requires us to set the SOAP action dynamically:
I did follow the guidelines mentioned in the following links
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
Dynamic webservice selection
The process which we are using is as follows
We are creating the following UDF and mapping the root nodes in message mapping using it
DynamicConfigurationKey keyURL = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
// access dynamic configuration
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
conf.put(keyURL,"RetrieveList");
return "";
In the Receiver Comm Channel we are setting the use adapter specific identifiers option and the use variable binding option. We are leaving the SOAP Action field blank.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Server</faultcode>
<faultstring>String index out of range: 0</faultstring>
<faultactor>Server</faultactor>
</SOAP:Fault>
Now we tested the scenario using TCP Mon and we identified that for the value of SOAP Action we are getting the following results
SOAPAction:
SOAPAction: actual value
It means that 2 SOAP Action are generated one being the empty SOAP Action from Receiver Comm Channel and the other being the one generated using UDF.
Can anyone please update us on if our steps are proper or is there a way to supress the SOAP Action which we left empty in the receiver comm channel.
Your help is truly appreciated.
Thanks.
Kiran

Did you follow all the three steps I have pointed in the thread,
1. In the Receiver SOAP adapter,Select options ,
a) Use Adapter Specific Message Attributes
b) variable Transport Binding.
c) Keep the SOAP action field empty.
In the receiver SOAP adapter, make sure that the soap action is empty and the above options are selected.
In this case, the SOAP action from the UDF will be choosen.
But, if you enter something in the receiver SOAP adapter's SOAP action this will be treated as the SOAP action rather than the UDF code.
Regards
Bhavesh

Invalid SOAP action when using java ws WebService

Hi all,
this is a slightly more detailed error for a problem i posted recently. I am connecting to a web service that was generated from WSDL. It has two methods "HelloWorld" and "HelloSayFirstName". As defined in the WSDL, the methods use the SOAP action document style. I want to add a cookie to the http header, so after the port is created, I use the following to add the header to the requestContext:
          BindingProvider bindingProvider = (BindingProvider) servicePort;
          Map<String, Object> requestContext = bindingProvider.getRequestContext();
          List<String> cookies = new ArrayList<String>();
          cookies.add("mycookie=mytoken");
          HashMap<String, List<String>> httpHeaders = new HashMap<String, List<String>>();
          httpHeaders.put(HTTPConstants.HEADER_COOKIE, cookies);
          requestContext.put(MessageContext.HTTP_REQUEST_HEADERS, httpHeaders);
This works when I call the first method (HelloWorld) - the first activity message sent to the server contains the following:
<HttpRequest>
<Method>POST</Method>
<QueryString></QueryString>
<WebHeaders>
<Cache-Control>no-cache</Cache-Control>
<Connection>keep-alive</Connection>
<Pragma>no-cache</Pragma>
<Transfer-Encoding>chunked</Transfer-Encoding>
<Content-Type>text/xml; charset=UTF-8</Content-Type>
<Accept>*</Accept>
<Cookie>mycookie=mytoken</Cookie>
<Host>exampleHost</Host>
<User-Agent>Java/1.5.0_14</User-Agent>
<SOAPAction>"http://tempuri.org/IMyService/HelloWorld"</SOAPAction>
</WebHeaders>
</HttpRequest>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<To s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://exampleHost/WebServices/WCFService/Service.svc</To>
<Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://tempuri.org/IMyService/HelloWorld</Action>
</s:Header>
<soap:Body>
<HelloWorld xmlns="http://tempuri.org/" xmlns:ns2="http://schemas.datacontract.org/2004/07/" xmlns:ns3="http://schemas.microsoft.com/2003/10/Serialization/">
<myValue1>world</myValue1>
</HelloWorld>
</soap:Body>
</soap:Envelope>
However, after this method, the httpHeaders in the requestContext object have been updated to include the "Accept" header and the "SOAPAction" header - which is the incorrect action! Now, when I call the method "HelloSayFirstName" I get the following:
<HttpRequest>
<Method>POST</Method>
<QueryString></QueryString>
<WebHeaders>
<Cache-Control>no-cache</Cache-Control>
<Connection>keep-alive</Connection>
<Pragma>no-cache</Pragma>
<Transfer-Encoding>chunked</Transfer-Encoding>
<Content-Type>text/xml; charset=UTF-8</Content-Type>
<Accept>*</Accept>
<Cookie>mycookie=mytoken</Cookie>
<Host>exampleHost</Host>
<User-Agent>Java/1.5.0_14</User-Agent>
<SOAPAction>"http://tempuri.org/IMyService/HelloWorld"</SOAPAction>
</WebHeaders>
</HttpRequest>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<To s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://exampleHost/WebServices/WCFService/Service.svc</To>
<Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://tempuri.org/IMyService/HelloWorld</Action>
</s:Header>
<soap:Body>
<HelloSayFirstName xmlns="http://tempuri.org/" xmlns:ns2="http://schemas.datacontract.org/2004/07/" xmlns:ns3="http://schemas.microsoft.com/2003/10/Serialization/">
<dataContractValue></dataContractValue>
</HelloSayFirstName>
</soap:Body>
</soap:Envelope>
It seems that the SOAPAction in the http header and the soap header is incorrect. Is there any reason why the requestContext would keep hold of the action that was previously called, and not use the new action? I'm stumped here - any help would be greatly appreciated.
Cheers.

Does not only happen when using JAX-WS.
the following servlet code is enough to reproduce the problem :
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
response.setContentType("text/xml;charset=\"utf-8\"");
It only occurs on 10.1.3.4.0 (works fine on 10.1.3.3.0 and 11.1.1.1.0 TP4)
Regards

SOAP Action

I have a scenario rfc to soap,In soap receiver configuration i have given name method name of wsdl,I Have an error
Unable to find a matching Operation for this remote invocation in moni
I feel my soap action is not trigerring,what would be the problem...
Thanks
sriram

hi,
did you use the imported wsdl ?
if the document that you imported
has a different type (RPC) if may not work
plase have a look at sap note: 856597
and two questions:
Q: Does the RPC or Document style in WSDL play a role in the SOAP adapter?
Q: Can I convert an RPC styled WSDL to a document styled WSDL?
the above will help you to create a correct wsdl
you can also have a look at this weblog:
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
to see how to get a correct structure (via XML Spy) of the wsdl message
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Soap Action missing in the WSDL generated for Service Interface

Hi All,
I have modelled an interface in the ESR and have created the proxy in the back-end ECC6 system. It is basically an outside-in approach. I have generated a WSDL using the Wizard in the SPROXY transaction. But the WSDL does not have any SOAP Action. I tried to create a web-service for an existing BAPI. That WSDL also did not have any SOAP Action. Can you please let me know why the SOAP Action is missing? Is there any other way of generating the WSDL?
Regards,
Geetha

Hi Geetha,
Please try configuring the entire scenario in PI.
If you are using PI 7.1, You can see the WSDL by right clicking on Sender agreement. Please use SENDER SOAP Channel. In PI 7.0 you will have to generate WSDL manually.
Regards,
Vikas

SOAP Action missing in Axis adapter

Hi,
I am not able to send data to a Web Service using Axis Adapter (SOAP 1.2) and getting an error of "SOAP Action is missing". Can see that SOAP action is missing in the SOAP message sent to Web Service. Communication channel is configured with SOAP Action.
Am on PI 7.10 SP6.
Any help is appreciated!!
Thanks
Kiran

Hello,
I tink you are using receiver SOAP Communication channel... Ask your client to provide the same... because.... your message will be processed at receiver side by using SOAP Action at receiver side...
SOAP action is mandatory for SOAP Receiver communication channels...
Thnx
Subbu

Specifying SOAP action

Similar Messages

Maybe you are looking for