Sca component wsa:Address different to SOAP Action

Hi,
i have developed an SCA component with SOA Suite 11.1.1.2 and JDeveloper 11.1.1.2. I have an outgoing service call behind a mediator. the soa suite sends a request to this service containing WS-Addressing information. These WS-Addressing information seem to be generated automatically by the SOA Suite. Did i get that right? The problem is, that the wsa:Action Element is generated and i have no idea how to influence the content of that element. I have to change the content of the wsa:Address, because it is different to the SOAP Address committed via the HTTP Header. This difference leads to an exception in my Axis2 Web Service. The SOAP Address in the HTTP Header is being determined from the wsdl soapAction Attribute in soap:operation element. But how is the wsa:Address being determined and how can i influence it?
I hope someone can help me with that ... didn't find any solution after a lot of googling.
thx
Edited by: user12575721 on 08.02.2010 04:41

Hi,
I think i might have the same sort of issue with a very simple SCA: i have got an outgoing webservice with WS Security behind a mediator.
I have exposed my mediator interface.
I have defined a WSS username policy to my outgoing webservice and created appropriate key in the Credential Provider.
I desperately try to call from the SOA Infra Test console this interface but I got the following error in my composite: "WS Addressing property is set in SOAP Header, the service cannot be proceeded".
It seems related to some WS-Addressing header that the SOA 11g is adding automatically.
I have googled this issue, but anyone except you seems to encounter this problem.
Any idea ?

Similar Messages

Can we use same SOAP ACTION in different environments?

Hi All,
I have a doubt.
Can we use same SOAP Action URL in different environments i.e suppose say Quality, Production and Pre production.And the Target URL is different in both environments.
If yest what is the impact in different environment.

Hi ,
SOAP action is nothing but operation/method in webservice .
Usually at end system end as a good practice/std they will maintain the same soap action name in all their environments,but it's always better to cross check url and soap action with end system folks before configuring in PI .
We have faced an issue in production some time back ,at target system end they upgraded their server and used new wsdl which is almost similar to existing but one of the operation they duplicated by adding few addition fields but forgot to inform PI system.Though we are using new wsdl but pointed to old soap action .Interface got failed in PROD after investigation we come to know that we are using wrong soap action
Regards
Venkat

Preview Error: "no endpoint listening at net.pipe ... incorrect address or SOAP action ... could not be found on your local machine"

Hi
I am developing SSRS reports, suddenly now I am getting this error when I try to preview a report in the VS 2010 shell:
"This is a designer preview error, "There was no endpoint listening at net.pipe://localhost/PreviewProcessngServcie11108/ReportProcessng that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerExcelption,
if present, for more details. The pipe endpoint 'net.pipe://localhost/PreviewProcessing11108/ReportProcessing' could not be found on your local machine"
The error has come out of the blue, reports which I used to be able to preview, I can't preview anymore.
Anybody knows what to do to make it work again?

I tried to apply Mike Yin' answer on this thread
http://social.msdn.microsoft.com/Forums/en-US/38ff8d54-06aa-40c3-8916-378d5185320e/report-designer-preview-in-ssdt-throws-up-a-end-point-not-found-error?forum=sqlreportingservices
Suggestion 1:
Press WinKey+R , input “services.msc” in the Run box, and press enter.
In the local services list, find the “Net.Pipe Listener Adapter”.
If it is stopped, start it. If it is started, restart it.
I found that “Net.Pipe Listener Adapter” was not enabled, so I enabled it and started/restarted it. Now it works again :)

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?

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..

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.

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">XI / PI FAQ - Frequently Asked Questions</a>

Soap action: in Proxy to soap scenario

Hi experts,
I have a senario of Proxy to webservices.
I have imported the wsdl file as external defination, and have to use two message inside 1) to Insert 2) To Update.
Now proxy will run twice a month with same data structure,
I have to do insert action first and 2nd time Update.
I have only one receiver. So How to achive this in communication channel >> Soap Action.
1> Is is possible to provide two Soap action in a single communication channel.?
2> do i need to create 2 mapping and two interface ? My Source coming from Proxy is with one structure.
Regards,
Sumit Gupta

>
sumit gupta wrote:
> Hi experts,
>
> I have a senario of Proxy to webservices.
>
> I have imported the wsdl file as external defination, and have to use two message inside 1) to Insert 2) To Update.
>
> Now proxy will run twice a month with same data structure,
>
> I have to do insert action first and 2nd time Update.
>
> I have only one receiver. So How to achive this in communication channel >> Soap Action.
> 1> Is is possible to provide two Soap action in a single communication channel.?
> 2> do i need to create 2 mapping and two interface ? My Source coming from Proxy is with one structure.
>
> Regards,
>
> Sumit Gupta
You can either go for dynamic configuration and configure the action or you can go for two different Communication channels with separate actions.
In the proxy use a field as an indicator for the required action i.e INSERT or UPDATE and based on XPATH in your interface determination call the required channel or in case you are using a single channel create the dynamic action in your mapping based on that field.
Ref:
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/suraj.sr/blog/2006/01/05/multiple-inbound-interfaces-within-a-service
/people/shabarish.vijayakumar/blog/2009/03/26/dynamic-configuration-vs-variable-substitution--the-ultimate-battle-for-the-file-name

What is the use of soap action?

Hi experts,
what is the functionality of soap action in receiver soap adapter?
Thanks & Regards
E.Ravi Chandra Reddy

Hi Ravi,
This “SOAP action” tells the web service to perform a particular action. It will call the related method in the WSDL and perform that action and that WSDL may contain different functionalities/Methods and the action we will give in the channel will call the particular method
I have attched the screen of a WSDl containing different methods (WSMethods)
Channel for more reference

Is SOAP Adapter Action field can contain 2 or more "SOAP Actions"

Hi All,
I have following scenario:-
Step 1. Webmethod(sent price querry with material no)->R/3(search price from tables)
step 2. R/3(sent price)->Webmethod
step 3. Webmethod(sent quantity)->R/3(document created in sap)
step 4. R/3(sent confirmation doc no/error)->Webmethod
Q1 How can i implement above scenario in with one URL Webmethod????
(URL:http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel)
Q2 Is it possible with one (Receiver SOAP adapter->Conversion Parameters->SOAP Action) field can contain more than 1 SOAP Action......??????
With more than one message interfaces (inbound synchronous) in one scenario
Q3 Or I have to design two scenarios with two URL's????with different message interfaces (inbound synchronous) 
Q4 Or I use Sender(SOAP) Reciver(Rfc Adapter) in abave case??? With more than one message interfaces (inbound synchronous) in one scenario
Thanks & Regards
Message was edited by: Umesh R

When your scenario consists of sync calls, you have only to define SOAP sender channels. The best approach is to create two channels to keep the reference from interface to channel unique.
For the sync response message you do not need and communication channel (and no SOAP action).
Regards
Stefan

Receiver Adapter - Target URL/SOAP Action

Hi,
Can I just confirm the following 2 values required on a SOAP Receiver adapter:
Target URL : Location within SOAP:Address tag of WSDL
SOAP Action: SoapAction within SOAP:Operation for relevant Web Service method within WSDL
Cheers,
PaulC.

> Target URL : Value of SOAP:Address tag from web service WSDL
right, it is attribute "soapAction"
> SOAP Action: Value of SOAP:Operation for relevant Web Service method within web service WSDL
right. attribute "location"
check this guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4

Calling a business service based on operation-soap action in Proxy service

Hi,
I have a requirement in which I have to call a business service based on operation-soap action defined in Proxy service wsdl.
Like in below mentioned wsdl GetPartCostDelta and GetCurrencyList operations are there.But which ever operation I select,It just goes to one business service.
Is there any way,I can route to some another business service based on the soap action
proxy service WSDL
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ewopcd="urn:com:gm:gpd:schema:ewopartcostdelta" xmlns:gen="urn:com:gm:gpd:schema:genericfault" xmlns:tns="urn:com:gm:gpd:services:ewopartcostdeltaservice" targetNamespace="urn:com:gm:gpd:services:ewopartcostdeltaservice">
 <wsdl:types>
 <xs:schema>
 <xs:import namespace="urn:com:gm:gpd:schema:ewopartcostdelta" schemaLocation="ewocostdelta.xsd"/>
 <xs:import namespace="urn:com:gm:gpd:schema:genericfault" schemaLocation="servicefault.xsd"/>
 </xs:schema>
 </wsdl:types>
 <wsdl:message name="EWOCurrencyListRequest">
 <wsdl:part name="CurrencyListRequest" element="ewopcd:EWOCostDeltaInput"/>
 </wsdl:message>
 <wsdl:message name="EWOCurrencyListResponse">
 <wsdl:part name="CurrencyListResponse" element="ewopcd:EWOCurrencyList"/>
 </wsdl:message>
 <wsdl:message name="EWOPartCostDeltaRequest">
 <wsdl:part name="PartCostDeltaRequest" element="ewopcd:EWOCostDeltaInput"/>
 </wsdl:message>
 <wsdl:message name="EWOPartCostDeltaResponse">
 <wsdl:part name="PartCostDeltaResponse" element="ewopcd:EWOCostDeltaResult"/>
 </wsdl:message>
 <wsdl:message name="EWOPartCostDeltaServiceFault">
 <wsdl:part name="PartCostDeltaServiceFault" element="gen:ServiceFault"/>
 </wsdl:message>
 <wsdl:portType name="EWOPartCostDeltaPortType">
 <wsdl:operation name="GetCurrencyList">
 <wsdl:input name="EWOCurrencyListRequest" message="tns:EWOCurrencyListRequest"/>
 <wsdl:output name="EWOCurrencyListResponse" message="tns:EWOCurrencyListResponse"/>
 <wsdl:fault name="EWOPartCostDeltaServiceFault" message="tns:EWOPartCostDeltaServiceFault"/>
 </wsdl:operation>
 <wsdl:operation name="GetPartCostDelta">
 <wsdl:input name="EWOPartCostDeltaRequest" message="tns:EWOPartCostDeltaRequest"/>
 <wsdl:output name="EWOPartCostDeltaResponse" message="tns:EWOPartCostDeltaResponse"/>
 <wsdl:fault name="EWOPartCostDeltaServiceFault" message="tns:EWOPartCostDeltaServiceFault"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="EWOPartCostDeltaBinding" type="tns:EWOPartCostDeltaPortType">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="GetCurrencyList">
 <soap:operation soapAction="GetCurrencyList" style="document"/>
 <wsdl:input>
 <soap:body use="literal"/>
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal"/>
 </wsdl:output>
 <wsdl:fault name="EWOPartCostDeltaServiceFault">
 <soap:fault name="EWOCostDeltaServiceFault" use="literal"/>
 </wsdl:fault>
 </wsdl:operation>
 <wsdl:operation name="GetPartCostDelta">
 <soap:operation soapAction="GetPartCostDelta" style="document"/>
 <wsdl:input>
 <soap:body use="literal"/>
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal"/>
 </wsdl:output>
 <wsdl:fault name="EWOPartCostDeltaServiceFault">
 <soap:fault name="EWOCostDeltaServiceFault" use="literal"/>
 </wsdl:fault>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="EWOPartCostDeltaService">
 <wsdl:port name="EWOPartCostDeltaPort" binding="tns:EWOPartCostDeltaBinding">
 <soap:address location="https://localhost/EWOPartCostDelta"/>
 </wsdl:port>
 </wsdl:service>
</wsdl:definitions>

Did you try using the Operational branching node of OSB?
You have copy the operation name from the inbound variable and populate the SOAP Header with that value into the SOAPAction tag.I think this will work.
Thanks,
Prabu

Blank SOAP Action in Soap Request- Portal Service calling Web Service

Hi
I'm trying to access an Web Service through a client portal service which was generated by NWDS. I called this service from a basic component and tried to execute the WS function after populating all the needed fields. When I started the component I encountered the following error.
java.lang.IllegalArgumentException: The SOAP Action "" include in the soap request not corresponding to the Portal service method..
I initially thought it was because I was downloading the WSDL to my local and using that in the portal service generation. Maybe not all the information about the web service was being obtained. I tried it again after generating the portal service from the WSDL online but still obtained the same error.
Any insight on what's causing the error would be appreciated. Thanks!

Dear expert.
i got the same problem with Reyes. anyone can solve this issue?
thank in advance.

C# interviews and soap actions...

For the interview web service wsdls, the soap actions have the project name in them... I am not really sure why that is... Is there any background someone can provide on that?
For instance, an OPA project called "test" has the following action defined for opening a session:
http://oracle.com/determinations/server/interview/10.4/test/types/OpenSession
A project called "WebServiceDemo" has the following action defined for opening a session:
http://oracle.com/determinations/server/interview/10.4/WebServiceDemo/types/OpenSession
Other than that, these are identical, and the same client C# code could be used to run interviews for either ruleset...
Anybody know how in C# to replace the action so that one client can call both interview rulesets (or any other ruleset at a dynamic endpoint)?
I know how to change the endpoint. The endpoint can be changed easily as in this example:
OPAInterview.odsInterviewService_test_typeClient iclient = new OPAInterview.odsInterviewService_test_typeClient();
iclient.Endpoint.Address = new System.ServiceModel.EndpointAddress("http://mynewurl/...");
Changing the actions are giving me a problem... Without that, I can't run interviews generically.

Rehi,
forgot to say: when using jsp:include, the whole calling JSP is replaced w/ the called document. However, jsp:include is not an option die to c:import tech advantages.
But, important may be this two-liner that Jasper throws to STDOUT:
Nov 5, 2003 10:26:22 PM org.apache.jasper.runtime.PageContextImpl release
WARNING: Internal error flushing the buffer in release()
? Bug due to Tomcat beta... or?
THX, Timo

Sca component wsa:Address different to SOAP Action

Similar Messages

Maybe you are looking for