Any Soap Service / http header

http header "SOAPAction" is not routed from proxy service to business service and to the external web service
Please see follow steps that would describe the case
1. I developed a Proxy Service of type "Any Soap Service". This is because I dont want to generate a WSDL for the proxy service and give it to the clients. I just want to give them an URL and whatever the SOAP message they send, this proxy service will receive.
2. I developed a Business Service of type "Any Soap Service" The end point of this business service is an external web service. I dont want to use the external web service WSDL, but just the endpoint URL.
3. In the proxy service I developed in the step 1, I added a routing action and invoked the business service.
When a ws client now invokes the Proxy service with a soap payload (body), proxy service takes the payload and routes it to the business service and business service sends the payload (body) to the external web service. business service recieves the soap response back from external service and passes it back to the proxy service and thus client gets the response back from the proxy service.
What is missing is the http header "SOAPAction" passed to the proxy service by the ws client is not passed to the business service and hence not to the external web service. I want to pass the SOAPAction and all http headers sent by the ws client all the way to the external web service.
Do we have to programmatically extract SOAPAction and pass it to the external web service?
Your ideas please.. TIA
Edited by: GDD on Dec 3, 2009 6:32 PM

I used Message flow Communication/TransportHeader component to copy soapaction from Inbound request. This enabled transport headers to be passed.
would like to hear if there are other options.

Similar Messages

Messaging Service vs WSDL Based service vs Any SOAP service

Hi,
What is the basic difference between these three types of configuration for OSB Proxy? Why can't we use wsdl based or soap based service instead of messaging service? Is there any significance for messaging service?
Thanks

Each configuration defines how the Proxy will interface with the consumers. (In other words the input (request format) and output (response format) specifications for the proxy)
Refer http://docs.oracle.com/cd/E17904_01/doc.1111/e15867/configuringandusingservices.htm#i1146533 (The description column gives an understanding on this)
Let us know in case of further questions.
Thanks,
Patrick
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
https://forums.oracle.com/forums/ann.jspa?annID=893

SOAP Receiver - HTTP header problem

Hi,
Scenario: IDOC - - XI - - SOAP(webservice).
Third party is asking for missing "/" (path?) in header after "POST". Following is the message received by third party. How to override this header to put "/" after POST? Please help.
POST HTTP/1.0
Accept: /
Host: 100.10.2.5:9092
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Authorization: Basic Z2hydHNvYXA6bm92ZWxs
content-id: <soap-48E034BD9F5B3308E1000000876CF529@sapcom>
Content-Type: text/xml; charset=utf-8
Content-Length: 313
SOAPACTION: "#batchRequest"
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
 <SOAP:Header/>
 <SOAP:Body>
 <ns0:cvgtransaction xmlns:ns0='http://abc.com/xi/Novell' event='modify' workforceID='1' type='employee'>
 <attribute name='WWID' operation='replace'>1234567</attribute>
 </ns0:cvgtransaction>
 </SOAP:Body>
</SOAP:Envelope>

Hi!
with XI standard tools you have no chance to manipulate the soap envelope created by the XI. You have to configure your soap receiver communication channel to not create a soap envelope "Do not use SOAP envelope") and then you use e.g. a XSLT mapping to create a soap envelope by yourself.
Regards,
Volker

How to send concurrent xml request to Soap service.

Hi
I am working in a scenario. where i need to send more than 10 concurrent xml request to soap service hosted in IIS.
and that service directly pools to biztalk recieve location. Presently i am sending a single request through soap ui.
Is there any tool available to send more than 10 xml request to service. If not then how we send through C#.code

Hi Anagh,
Microsoft BizTalk LoadGen 2007 Tool would be the perfect fit for your requirement where you need to send "Concurrent" request to SOAP.
Using LoadGen you can configure it use to number of concurrent threads to send messages. In its config file, it has a section called
<NumThreadsPerSection> which can be used to set the number of concurrent threads that LoadGen will use to send messages.
Read one of my old blogposts where I have talked about using LoadGen for simulating message load for SOAP services.
http://indway-is.blogspot.co.uk/2009/01/loadgen-testharness-for-soap-transport.html
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

How can I set "SOAPAction" http header using SAAJ

When I send soap request, http header's like below
SOAPAction: ""
But, I'd like to send like this
SOAPAction: "http://tempuri.org/HelloWorld"
How can I that using SAAJ ?
My code is
String xml = "<?xml version=\"1.0\" encoding=\"utf-8\"?>\n" +
"<soap:Envelope xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\">\n" +
" <soap:Body>\n" +
" <HelloWorld xmlns=\"http://tempuri.org/\" />\n" +
" </soap:Body>\n" +
"</soap:Envelope>";
Document doc = DocumentBuilderFactory.newInstance().newDocumentBuilder().parse(new ByteArrayInputStream(xml.getBytes()));
DOMSource domSource = new DOMSource(doc);
SOAPMessage message = MessageFactory.newInstance().createMessage();
message.setProperty(SOAPMessage.CHARACTER_SET_ENCODING, "utf-8");
message.setProperty(SOAPMessage.WRITE_XML_DECLARATION, "true");
message.getSOAPPart().setContent(domSource);
message.writeTo(System.out);
SOAPConnection connection = SOAPConnectionFactory.newInstance().createConnection();
SOAPMessage response = connection.call(message, helloURL);
connection.close();
SOAPBody body = response.getSOAPBody();
if ( body.hasFault() )
SOAPFault newFault = body.getFault();
System.out.println("SoapBody has fault.");
System.out.println("code=" + newFault.getFaultCodeAsName());
System.out.println("message=" + newFault.getFaultString());
System.out.println("actor=" + newFault.getFaultActor());
else
System.out.println("Call Successed.");
System.out.println(body);
}

message.getMimeHeaders().addHeader("SOAPAction", "http://tempuri.org/HelloWorld");

How to access (any) soap / rest web services from widget

Hi all,
Is there an API, javascript library etc, which allows accessing (any) soap / rest webservices from widgets?
I know I can access web services from sap j2ee with widget foundation, but I'm still not sure how to access "outside"
web services.
A blog entry about this topic would be greatly appreciated I think, not only by me.
Regards,
Ladislav

As promised, below is the js lib source code. I did not see the attachement option, so you can just create a text file and save it with .js extension.
 function getHdrData( FuncName ) {
 return '<?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:xs="http://www.w3.org/2001/XMLSchema">' +
 '<SOAP-ENV:Header><sapsess:Session ' +
 'xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/">' +
 '<enableSession>true</enableSession></sapsess:Session>'+
 '</SOAP-ENV:Header><SOAP-ENV:Body><ns1:' +
 FuncName +
 ' xmlns:ns1=\'urn:sap-com:document:sap:soap:functions:mc-style\'>';
 function addVar ( VarName, VarValue ) {
 return '<' + VarName + '>' + VarValue + '</' + VarName + '>';
 function getFtrData( FuncName ) {
 return '</ns1:' + FuncName + '></SOAP-ENV:Body></SOAP-ENV:Envelope>';
 function setTable ( TblName, TblType) {
 return '<' + TblName + ' xsi:type=\'ns1:' + TblType + '\'>';
 function closeTable ( TblName) {
 return '</' + TblName + '>';
 function startEntry( ) {
 return '<item>';
 function endEntry( ) {
 return '</item>';
So the following is the basic on how to use this library:
* Set up SOAP envelope
* Get the header data
getHdrData( SOAP operation name )
* If the web service set up the table and record start tags
setTable( variable name, table type ) - Optional
Set new record tag: startEntry() ? Optional
* Set up the fieldname or variable name
addVar( variable name, variable value )
* Set up the table and record end tags
endEntry() ? Optional
closeTable( variable name ) ? Optional
* Set up the footer SOAP envelope
Set footer data: getFtrData(SOAP operation name )
So hopefully that will help you consume SAP Published web services.

External Web Service - User and password in HTTP header

Hi!
How is it possible to add user and password in the HTTP header in a external web service call?
I have created a "Portal Service from WSDL file - Client side" with the wizard in SAP Developer Studio. I following the Java Development Guide - Web Service Security, and use the secured service connection. I have also created a new System Landscape, but should the new system be based on HTTP, my own PAR or what?
How can I check that the user and password is added to the HTTP header or the SOAP envelope? Do I have to scan http traffic with a proxy as Paros or can I find the request sent from SAP EP in the logs?
Cheers
Asle

Hello All,
I have been struggling a bit while putting a reasonable security framework on a jax-rpc style web service. I'm using JWSDP1.2 to set up the webservice. I've tried to outline my problem below. Please correct me where I'm wrong.
I've been through the Sun's WS tutorials, but they are not really clear on security. However, from them I surmised that there are two decent authentication techniques. HTTP Basic and mutual authentication (MA) . Both have their drawbacks though. HTTP Basic suffers from poor encryption while MA is a bit difficult to set up on both client and server sides. Another problem with MA is that there is no central repository for users/passwords.
OK, what I would really like to do is use my own user database to verify users/passwords i.e. use a HTTP Basic like authentication (but at application level) but run it over SSL for encryption. It seems simple, but is it possible?
Also, I have noted that when I use HTTP Basic on the service side, and use a java client, then setting username/password has no effect. In other words, I can always access the web-service, even with wrong username/password.
Sorry for the long post. Hope someone can help. Thanks.

Adding soap action in http header

Hi ,
Can any tell me how configure proxy to add SoapAction in http header of outgoing message from ESB.
Thanks

This can be done using the Transport Headers action in the proxy service's message flow. Simply select the SOAPAction HTTP header and choose whether you want to either copy the value from the inbound request or set it to a new value.
Read more on how to use the action [url http://edocs.bea.com/alsb/docs26/consolehelp/proxyactions.html#wp1274176]here and read my [url http://dev2dev.bea.com/blog/ctomkins/archive/2007/12/sending_an_email_from_aqualogi_1.html]blog post which shows how to set a different header but demonstrates the principle.

HTTP Header fields in SOAP adapter - Part 2

Hi All,
With regards to my previous thread HTTP Header fields in SOAP adapter
my header issue is solved and hence I have closed the thread but still I am not able to make the connection successful. The new problem is below
My vendor requirement is to specify the header as "Ent-sender" but when we give the same in XI in communication channel it automatically convets into uppercase "ENT-SENDER". Due to case-sensitive in vendor server the connection is not gettingestablished.
Please help me out how to solve the problem.
Note: Sorry for the new thread as it was created due to new problem and also the previuos thread is already too long.
Regards,
Dhill

Hi Neaves,
Thank you, I jave seen the note and find the below solution will be some what realated to my prblem.
The nosoap mode lets the adapter send the XI payload directly without wrapping it in the SOAP envelope. Although the main use of this mode is to send some plain text content directly to some web server, one can use this mode to send their own SOAP message (e.g., with arbitrary headers) to an external web service (See related questions). In this case, the XI payload must be formatted in the SOAP envelope.
To use the nosoap mode, the channel must be configured to use no SOAP envelope.
If yes, can you please let me know how to use nosoap mode otherise let me the other possibilities. I am already using tcpg2.zip to trace the SOAP adapter in which it was confirmed that XI is changing the header automatically into CAPS whatever case we give,
Regards,
Dhill

Soap receiver - owerwrite default http header fields

Hi,
I'm using the soap receiver adapter in nosoap mode.
How can I owerwrite the default settings for the header fields in the http request?
The soap adapter will automatically set content-type = application/xml.
I would like for example set "text/xml".
Thanks,
Bela

Dear Mohan,
I tryed with the keep headers option but it didn't change anything to the HTTP header fields.
In the documentation we have the following : Keep Headers
If you want to include the header of the XI message in the Web service message, set the indicator.
Does it mean that I have to create a HTTP header section in the XI message??? Do you have an example?
Best regards,
Bela

Http Header for SOAP message.

Hello,
I need to set some custom HTTP Header when i send the SOAP message to an endpoint.
I tried this..but doesn't solve my requirement.
SOAPMessage soapmsg = messageFactory.createMessage();
MimeHeaders mime = soapmsg.getMimeHeaders();
mime.addHeader("SOAPAction", "xxxx");
mime.addHeader("Sender", "yyy");
SOAPMessage reply = connection.call(soapmsg, destination);
Can anyone please guide me how to set HTTP headers for SOAP?
Thanks,

The following snippet is some code froma stand-alone web service client that I use for testing. It picks up an XML as the payload of the web service, wraps it in a SOAP message and fires it at the web service endpoint.
     System.out.println("Create the SOAP message.\n");
     MessageFactory messageFactory = MessageFactory.newInstance();
     SOAPMessage message = messageFactory.createMessage();
     System.out.println("Creating a DOM object from the JAXB payload.");
     DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
          factory.setValidating(false);
             factory.setNamespaceAware(true);
     DocumentBuilder parser = factory.newDocumentBuilder();
     Document doc = parser.parse("file:payload.xml");
     // Add the HTTP headers.
     message.getMimeHeaders().addHeader("User-Agent", "Mozilla/4.0 [en] (WinNT; I)");
     message.getMimeHeaders().addHeader("Host", "localhost:9080");
     message.getMimeHeaders().addHeader("Content-type", "text/xml");
     message.getMimeHeaders().addHeader("SOAPAction", "http://www.xxx.com.au/wsdl/someWebService");
     message.setProperty(SOAPMessage.CHARACTER_SET_ENCODING, "utf-8");
     SOAPEnvelope envelope = message.getSOAPPart().getEnvelope();
     envelope.addNamespaceDeclaration("n", "http://xxx/webService");
     envelope.addNamespaceDeclaration("xsd", "http://www.w3.org/2001/XMLSchema");
     envelope.addNamespaceDeclaration("xsi", "http://www.w3.org/2001/XMLSchema-instance");
     System.out.println("Adding the payload to the SOAP body.\n");
     SOAPBody body = message.getSOAPBody();
     SOAPBodyElement docElement = body.addDocument(doc);
     System.out.println("This is the SOAP message.\n");
     message.writeTo(System.out);
     System.out.println("\nPutting the payload on the wire.\n");
     SOAPConnectionFactory conFactry = SOAPConnectionFactory.newInstance();
     SOAPConnection connection = conFactry.createConnection();
     URL endpoint = new URL("http://localhost:9080/xxx/services/yyy-webservices");
     SOAPMessage response = connection.call(message, endpoint);
     System.out.println("Payload sent. Closing the connection.\n");
     connection.close();

OSB- Any Soap type Proxy service URL issue.

Hi,
There is an issue which i am facing and stuggling with it for sometime :(
Requirement - Using OSB 11g i had created 12 different services based on WSDLs provided by the client and all of them are working fine.However the client wanted a OSB router service on top of these 12 services which wil search for a string in the input xml and then route it to the required Proxy service (amongst the 12 services developed).
Problem- I was able to create the router Proxy service which was a Any Soap type of proxy service as i didnot have a WSDL for the router service.The router service is working fine when we test it from the OSB console.
When We tried to test the flow from SOAPUI (we used the WSDL of one of the 12 webservices developed and modified the uri to the uri of the router service ie. http://hostname:port/router/routerProxy) and it does not work.
The error returned is ERROR 404 nothing found by this name.
As The router proxy is a Any Soap kind of service i do not have the option of providing the client with the WSDL.
I would want to know how to i call this router service from an external source like SOAPUI so that the client is able to hit it.Also what would be the end point uri of this router service ?
Kindly Help
Thanks
Pranav Shah

Hi anuj,
Here you have the configuration
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:con="http://www.bea.com/wli/sb/pipeline/config" xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config" xmlns:con2="http://www.bea.com/wli/sb/stages/config" xmlns:con3="http://www.bea.com/wli/sb/stages/transform/config">
<ser:coreEntry isProxy="true" isEnabled="false" isAutoPublish="false" isTracingEnabled="false">
<ser:description/>
<ser:binding type="abstract SOAP" xsi:type="con:AnySoapBindingType" isSoap12="false" xmlns:con="http://www.bea.com/wli/sb/services/bindings/config"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:logging isEnabled="true">
<ser:logLevel>debug</ser:logLevel>
</ser:logging>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:pipeline-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:pipeline-alerting>
<ser:ws-policy>
<ser:binding-mode>service-policy-bindings</ser:binding-mode>
<ser:policies/>
</ser:ws-policy>
<ser:throttling enabled="false">
<ser:capacity>0</ser:capacity>
<ser:maxQueueLength>0</ser:maxQueueLength>
<ser:timeToLive>0</ser:timeToLive>
</ser:throttling>
<ser:messageTracing enabled="false">
<ser:detailsLevel>Terse</ser:detailsLevel>
<ser:maxSize>8192</ser:maxSize>
</ser:messageTracing>
<ser:pageAttachments isEnabled="false"/>
<ser:transactions isRequired="false" sameTxForResponse="false"/>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>http</tran:provider-id>
<tran:inbound>true</tran:inbound>
<tran:URI>
<env:value>/testRouter/test</env:value>
</tran:URI>
<tran:inbound-properties/>
<tran:all-headers>true</tran:all-headers>
<tran:provider-specific xsi:type="http:HttpEndPointConfiguration" xmlns:http="http://www.bea.com/wli/sb/transports/http">
<http:inbound-properties/>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router>
<con:flow>
<con:route-node name="RouteNode1">
<con:context/>
<con:actions>
<con3:ifThenElse>
<con2:id>_ActionId-9110389481588294027-8fc6726.12c833ed7e1.-7c90</con2:id>
<con3:case>
<con3:condition>
<con:xqueryText xmlns:con="http://www.bea.com/wli/sb/stages/config">fn:contains(fn-bea:serialize($body), 'ImsersoSiebelContactInsert')</con:xqueryText>
</con3:condition>
<con3:actions>
<con1:route>
<con2:id>_ActionId-9110389481588294027-8fc6726.12c833ed7e1.-7c8f</con2:id>
<con1:service ref="ServiWebEntrada/AltaExpediente/ProxyService/AltaExpedienteProxyService" xsi:type="ref:ProxyRef" xmlns:ref="http://www.bea.com/wli/sb/reference"/>
<con1:operation>ImsersoSiebelContactInsert</con1:operation>
<con1:outboundTransform/>
<con1:responseTransform/>
</con1:route>
</con3:actions>
</con3:case>
<con3:case>
<con3:condition>
<con:xqueryText xmlns:con="http://www.bea.com/wli/sb/stages/config">fn:contains(fn-bea:serialize($body), 'CreaContacto')</con:xqueryText>
</con3:condition>
<con3:actions>
<con1:route>
<con2:id>_ActionId-9110389481588294027-8fc6726.12c833ed7e1.-7c8b</con2:id>
<con1:service ref="ServiWebEntrada/CuidContact/ProxyService/CuidContactProxyService" xsi:type="ref:ProxyRef" xmlns:ref="http://www.bea.com/wli/sb/reference"/>
<con1:operation>CreaContacto</con1:operation>
<con1:outboundTransform/>
<con1:responseTransform/>
</con1:route>
</con3:actions>
</con3:case>
</con3:ifThenElse>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>
Regards
Pranav

OSB - Content length http header missing from business service out message

Hi all,
I am having some diffuclty with a business service in OSB. I created the business service from the wsdl and created a regular proxy service that just routes to the business service. When i run the test console i get the below fault.
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380000: Length Required</faultstring>
<detail>
After some debugging i find that the content length http header is missing from the outbound message the business process creates and sends to the acutal web service which sends back the http 411 fault.
Does anyone know how to configure the message flow of my proxy service to ensure that the outbound message sent from the business service contains that content length http header or any suggestions on how to fix this issue will be appreciated.
Thanks

Disable the "Use Chunked Streaming Mode" property in HTTP Transport Configuration of your business service. By default it remains enabled.
Regards,
Anuj

SSRS web services 401 if you pass "Authorization" http header

We use both SSRS 2008 R2 and 2012. When i access a report using url access (direct ssrs server hit) and add a "Authorization: Bearer xyzelkalklsjsdfalsjdf" http header, i get a 401 from somewhere in the request pipeline. I have a custom httpmodule
registered at the top of the chain which does some OAuth related security checks. But when this header is included, the request never reaches the httpmodule. If i change the header slightly ex: "YAuthorization: ljlxzcvc..", then the request reaches
the httpmodule and everything works. So obviously SSRS is looking for a particular header named "Authorization" and does something with it. Point to note: we have implemented a custom forms authentication module and we are doing some rich authorization
using the extensible ssrs api.
Now my questions are:
1. What is happening here? Who is acting on my request before my HttpModule registered on top in ssrs\reporting service\web.config gets it?
2. How do i ensure my httpmodule executes before whatever component is terminating my request with a 401

Sorry if this sounds like I am new to this but I am.
So, the extended version is the format that would be used if you were not utilizing the files that the wsdl2java function creates?
And this is done to when you want more flexibiility for the user to call your service?
So, you would push to have the stub files used when you want to control how the web service is used?
thanks for the feedback.

Any way to get HTTP header in web dynpro Java?

Is there any way to get HTTP header in web dynpro java? This method gives me the params. Is params same as header? It doesn't have any way to retrieve header data. I am on NW 7.0.19
WDProtocolAdapter.getProtocolAdapter().getRequestObject().getParameter("param");

Dear Faraz,
I'm afraid the code you've pasted is only to retrieve URL parameters.
Have you tried this document to see if it offers any good hint:
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0446f5c-fcb9-2910-e082-88becbe3ddc9]
Not sure if you can process the HTTP header with a WD4J.
An alternative could be to develop some Portal component in plain JAVA working as a proxy to call your WD4J afterwards.
That portal component would process your HTTP header and forward any parameter to your WD4J.
But this is me just guessing.
Kind Regards
/Ricardo

Any Soap Service / http header

Similar Messages

Maybe you are looking for