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.

Similar Messages

Adding custom information in HTTP Header in an outgoing request from GWWS

Is there a way to send custom header information with the a webservice request (HTTP post) that happens via GWWS server?
All the methods I read about deal with managing the soap envelop that gets sent.
We are looking for ways which will allow us to put custom information in the headers.
I am aware there is something we can do using the Salt Plugins.
For example, we can write a Out bound plugin which has a capability of putting the "Authentication:Basic..." in the header.
Then there is message conversion plugin which deals with transformation of message, which gives us control over the soap body.
Is it possible to put information in the header for outgoing request (from GWWS) to a specific web service?
Thanks and Sincere Regards,
Mrugendra

Maurice,
Thanks for confirming this.
It clarifies the doubts that I was having while reading through the documentation Xu pointed to.
Yes, we need to add HTTP Headers (not SOAP header).
For now we just need to add Basic Authentication HTTP Header for outbound service calls.
We have developed a plugin to do that for now.
And even if the salt plugin takes care of adding the Basic Authentication in the HTTP Header for outgoing calls, I guess we do not have any option to include some custom information in the HTTP Header which might be required in the future.
At-least, not unless we request that enhancement.
Bringing the plugin into our mix requires a lot of changes to our architecture including inclusion of AUTHSVR in the UBB,
Which, in turn, makes it imperative to change the endpoint clients of our application.
In addition to that, the incoming web service calls also need to include TUXEDO authentication information, which would again require either communicating the authentication information to the consumers of our service or device some kind of a proxy which would add the authentication information for all the incoming requests!
With these facts in mind, we were wondering if we have an easier way to include the HTTP header information.
As you say, Maurice, it seems it is not possible yet.
Thank you again for your replies.
Sincere Regards,
Mrugendra

Load balance traffic to a service based on a added field in the HTTP Header

I am trying to use HTTP Header Load balancing but the field we want to use in order to load balance is "user-defined", example HTTP_TOTO = toto1.
Do you have any idea on how I could perform this ?
Thanks in advance

Load balancing using pre-defined headers is supported. Not sure if load balancing using user defined fields is possible. You could refer to the following document.
http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_710/bsccfggd/httphead.htm
We would appreciate it if someone could share their experience if they know more about this.

Custom information in HTTP Header in an outgoing GWWS Request

Hello Xu,
Hello Everyone,
With reference to the recent post activity in the post:
[Adding custom information in HTTP Header in an outgoing request from GWWS|https://forums.oracle.com/forums/thread.jspa?threadID=2366358&tstart=0]
We are looking for an option to send custom header information with the a webservice request (HTTP post) that happens via GWWS server.
I prematurely marked that post as answered since we got a link to documentation in one of the answers, which suggests that problem has been taken care in TUXEDO11gR1.
However, it would be difficult (almost impossible) for us to move to 11gR1 immediately.
Since I marked that post as "answered" and I did not know if replies in that post will get any attention, I opened up this post.
Xu (He) suggested (in reply to my previous post) that there might be a patch for our problem.
It would be wonderful/perfect if we can get a patch for 10gR3!
We are using the following:
TUXEDO10gR3 PATCH LEV=44
SALT Patch Lev = 15
Please do let us know.
Thank you again
Sincere Regards,
Mrugendra

Maurice,
Thanks for confirming this. (in the post: [Adding custom information in HTTP Header in an outgoing request from GWWS|https://forums.oracle.com/forums/thread.jspa?threadID=2366358&tstart=0] )
It clarifies the doubts that I was having while reading through the documentation Xu pointed to.
Yes, we need to add HTTP Headers (not SOAP header).
For now we just need to add Basic Authentication HTTP Header for outbound service calls.
We have developed a plugin to do that for now.
And even if the salt plugin takes care of adding the Basic Authentication in the HTTP Header for outgoing calls, I guess we do not have any option to include some custom information in the HTTP Header which might be required in the future.
At-least, not unless we request that enhancement.
Bringing the plugin into our mix requires a lot of changes to our architecture including inclusion of AUTHSVR in the UBB,
Which, in turn, makes it imperative to change the endpoint clients of our application.
In addition to that, the incoming web service calls also need to include TUXEDO authentication information, which would again require either communicating the authentication information to the consumers of our service or device some kind of a proxy which would add the authentication information for all the incoming requests!
With these facts in mind, we were wondering if we have an easier way to include the HTTP header information.
As you say, Maurice, it seems it is not possible yet.
Thank you again for your replies.
Sincere Regards,
Mrugendra

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

How do I set the Http Header POST URL in SAAJ?

Hi ,
I am a newbie in the field of web services. I was trying to create a SOAP request with Http Header POST information having a POST url like
the following:
POST /OMASTI.xml HTTP/1.1
Content-Type: multipart/related; boundary="eladeladeladeladeladeladeladeladelad"; type=text/xml; start=11814460
Content-Length: 54596
Host: unspecified
SOAPAction: ""
to that effect I did the following in the SAAJ client:
MimeHeaders md = message.getMimeHeaders();
md.setHeader("SOAPAction" ,"\"\"");
md.setHeader("POST" ,"/OMASTI.xml");
However what I got was :
POST / HTTP/1.1
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
SOAPAction: ""
POST: /OMASTI.xml
Content-Type: multipart/related; type="text/xml"; boundary="----=_Part_2_32124414.1153146262750"
Content-Length: 3352
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.5.0_07
Host: www.google.com
Connection: keep-alive
I have two POSTs in the header. How do I fix it? Please Help ASAP.
Regards,
Zeus

Hi,
Please forgive my ignorance. I did the same as you said. and then checked the Http request being sent out using ethreal software... it was the same as I had told earlier. Is only POST supported by the connection object? And the does the URL that comes in the Mime header as POST refer to the URL to which the request was sent? what I mean is that if the mime header says
POST /OMASTI.xml HTTP 1.1, does it mean that the URL that was passed to the connection object was "/OMASTI.xml" ? I had given the url as http://www.google.com to test the request being sent.. I only have a sample SOAP request which shows a HTTP header with the post url as I said before. I need to create a SOAP request with the same sort of Http header and the body needs to follow a certain OMA-STI protocol. My experience in the SOAP domain is almost nil. So please enlighten me.
Thanks in advance,
zeus

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.

BC Ecommerce SOAP Error: Server did not recognize the value of HTTP Header SOAPAction

I am trying to add a product to an ecommerce site with this soap action: Product_UpdateInsert
I have followed this very brief instruction: https://jollyrogers.worldsecuresystems.com/catalystwebservice/catalystecommercewebservice. asmx?op=Product_UpdateInsert
I have a html page in a secure area with a jQuery ajax soap script.
I get the this error when I run the script:
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Server did not recognize the value of HTTP Header SOAPAction: https://jollyrogers.worldsecuresystems.com/CatalystDeveloperService/CatalystEcommerceWebse rvice/Product_UpdateInsert.</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>
I have also tried to add a header with the Soap action with the beforeSend in the ajax call.
This must have been solved before I suppose?
Here is my script:
<!DOCTYPE html>
<html lang="en">
<head>
<title>Test SOAP Request</title>
    <script type="text/javascript" src="//code.jquery.com/jquery-1.10.2.min.js"></script>
    <script type="text/javascript" src="//cdnjs.cloudflare.com/ajax/libs/jquery-cookie/1.3.1/jquery.cookie.min.js"></script>
    <script type="text/javascript" src="//cdnjs.cloudflare.com/ajax/libs/underscore.js/1.5.1/underscore-min.js"></script>
    <script type="text/javascript" src="//cdnjs.cloudflare.com/ajax/libs/backbone.js/1.0.0/backbone-min.js"></script>
    <script type="text/javascript" src="//cdn.worldsecuresystems.com/bcapi/bcapi-0.0.1.min.js"></script>
</head>
<body>
<script>
var wsUrl = "https://jollyrogers.worldsecuresystems.com/catalystwebservice/catalystecommercewebservice. asmx";
var soapRequest =
'<?xml version="1.0" encoding="utf-8"?> \
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> \
<soap12:Body> \
    <Product_UpdateInsert xmlns="https://jollyrogers.worldsecuresystems.com/CatalystDeveloperService/CatalystEcommerceWebse rvice"> \
      <username>myEmailAdress</username> \
      <password>mySecretPassw</password> \
      <siteId>1894001</siteId> \
      <productList> \
        <Products> \
          <productCode>ZJAWEyuuyN</productCode> \
          <productName>My test product</productName> \
          <description>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</description> \
          <smallImage>/images/product1/small.jpg</smallImage> \
          <largeImage>/images/product1/large.jpg</largeImage> \
         <cataloguesArray> \
             <string>/Store/</string> \
          </cataloguesArray> \
          <pricesSaleArray> \
            <string>US/19.95,3/17.96,7/16.96</string> \
          </pricesSaleArray> \
          <pricesRetailArray> \
            <string>US/20,5/19,8/20</string> \
          </pricesRetailArray> \
          <pricesWholesaleArray> \
            <string>US/20,5/19,8/20</string> \
          </pricesWholesaleArray> \
          <wholesaleTaxCodeArray> \
            <string>US/0.00</string> \
          </wholesaleTaxCodeArray> \
          <taxCodeArray> \
            <string>GB/VAT</string> \
          </taxCodeArray> \
          <groupProducts> \
            <string>580H0036BL</string> \
            <string>ACAI60</string> \
            <string>ABC-123</string> \
          </groupProducts> \
          <groupProductsDescriptions> \
            <string>Lorem ipsum dolor sit amet</string> \
            <string>consectetur adipisicing elit</string> \
          </groupProductsDescriptions> \
          <supplierEntityId>1234</supplierEntityId> \
          <supplierCommission>0</supplierCommission> \
          <weight>30</weight> \
          <tags>NEW!</tags> \
          <unitType>string</unitType> \
          <minUnits>0</minUnits> \
          <maxUnits>2</maxUnits> \
          <inStock>43</inStock> \
          <onOrder>3</onOrder> \
          <reOrder>2</reOrder> \
          <inventoryControl>true</inventoryControl> \
          <canPreOrder>true</canPreOrder> \
          <custom1>Text in custom field 1</custom1> \
          <custom2>Text in custom field 2</custom2> \
          <custom3>Text in custom field 3</custom3> \
          <custom4>Text in custom field 4</custom4> \
          <popletImages>/images/image1.jpg;/images/image2.jpg;</popletImages> \
          <enabled>true</enabled> \
          <deleted>false</deleted> \
          <captureDetails>true</captureDetails> \
          <downloadLimitCount>20</downloadLimitCount> \
          <limitDownloadsToIP>0</limitDownloadsToIP> \
          <isOnSale>true</isOnSale> \
          <hideIfNoStock>true</hideIfNoStock> \
          <productAttributes>Size*|5|Y:L||UK/2|US/20,S||UK/1|US/10</productAttributes> \
          <isGiftVoucher>false</isGiftVoucher> \
          <enableDropShipping>true</enableDropShipping> \
          <productWeight>0</productWeight> \
          <productWidth>0</productWidth> \
          <productHeight>0</productHeight> \
          <productDepth>0</productDepth> \
          <excludeFromSearch>false</excludeFromSearch> \
          <productTitle>My product title</productTitle> \
          <cycletypeId>3</cycletypeId> \
          <cycletypeCount>-1</cycletypeCount> \
          <slug>my-product</slug> \
          <hasVariations>true</hasVariations> \
          <variations> \
            <ProductVariation xsi:nil="true" /> \
            <ProductVariation xsi:nil="true" /> \
          </variations> \
        </Products> \
      </productList> \
    </Product_UpdateInsert> \
</soap12:Body> \
</soap12:Envelope>';
$.ajax({
     type: "POST",
     beforeSend: function(xhr){xhr.setRequestHeader('SOAPAction', 'https://jollyrogers.worldsecuresystems.com/CatalystDeveloperService/CatalystEcommerceWebse rvice/Product_UpdateInsert');},
     url: wsUrl,
     contentType: "text/xml",
     dataType: "xml",
     data: soapRequest,
     success: processSuccess,
     error: processError
function processSuccess(data, status, req)
   if (status == "success")
   alert("Success!");
function processError(data, status, req)
   alert("Failed!");
   alert(req.responseText + " " + status);
</script>
</body>
</html>

This line is a target namespace so it should not be changed: <Product_Retrieve xmlns="http://tempuri.org/CatalystDeveloperService/CatalystEcommerceWebservice"> It is very easy to think that it's a placeholder and that it should be replaced with your own url, which it should not and which will fail.
This works now:
<!DOCTYPE html>
<html lang="en">
    <head>
        <title>Test 7 SOAP Request</title>
        <script type="text/javascript" src="//code.jquery.com/jquery-1.10.2.min.js"></script>
    </head>
    <body>
        <script>
            var SoapMessage = '<?xml version="1.0" encoding="utf-8"?> \
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> \
<soap12:Body> \
<Product_Retrieve xmlns="http://tempuri.org/CatalystDeveloperService/CatalystEcommerceWebservice"> \
<username>Your Email</username> \
<password>Your password</password> \
<siteId>1894001</siteId> \
<productCode>HHKDKXS5MB</productCode> \
            </Product_Retrieve> \
            </soap12:Body> \
            </soap12:Envelope>';
            var url = "https://jollyrogers.worldsecuresystems.com/catalystwebservice/catalystecommercewebservice. asmx";
            $.support.cors = true;
            $.ajax({
                type: "POST",
                url: url,
                data: SoapMessage,
                dataType: "xml",
                processData: true,
                contentType: "text/xml; charset=\"utf-8\"",
                success: function (msg) {
                    alert("suc: " + msg);
                error: function (msg) {
                    alert("Failed: " + msg);
        </script>
    </body>
</html>

How to send a signed SOAP message with additional HTTP Header fields

Our Partner's integration requirements are that we send them asynchronous SOAP messages, that are digitally signed, and whose HTTP headers contains 5 or 6 additional header fields, of which 3 or 4 will need to be dynamically set during the message mapping. I believe we can use the HTTP adapter for adding new fields to the HTTP header, but don't believe it supports signing. I believe that the SOAP adapter supports signing, but I'm not clear on how to use it to add fields to the HTTP header. What is the most straight-forward way to achieve both the signing of the message and the addition of the HTTP header values?
Thanks,
Kurt

>>>What is the most straight-forward way to achieve both the signing of the message and the addition of the HTTP header values?
Use Java mapping for both.
1) Signing the message
You can digitally sign the soap message using many standard api like WSS4j? or refer Java XML signature API which comes in Jdk1.6.
Refer these links
WSS4J - http://ws.apache.org/wss4j/axis.html
Java XML signature : http://java.sun.com/developer/technicalArticles/xml/dig_signature_api/
2) >>whose HTTP headers contains 5 or 6 additional header fields, of which 3 or 4 will need to be dynamically set during the message mapping
Use Dynamic configuration API to set the additional header fields during message mapping.

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();

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.
<b>Note:</b> 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.
<u><b>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.</b></u>
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

Http Header for a SOAP message using SAAJ.

Hello java community,
I need to set the 'SOAPAction' field in the HTTP Header of a soap message. I am using SAAJ to build the message.
Does anyone know how to do this?
Help is greatly appreciated as always.

You have to put a Handler in front of your WebService to intercept it.

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

SOAP HTTP header in SOAP request

Hi,
How to add the soap HTTP additional header in the SOAP request?
I want to add the headers not through coding. I want to add it manually.
I can able to add the HTTP headers through SOAPUI. But i need to add the same inside the request.
Could someone please help me?

I am sending the SOAP request through SoapUI.
Here is the sample request which i have used.
<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:req="http://requisition.api.newscale.com">
<soapenv:Header>
<req:AuthenticationToken>
<req:Username>***</req:Username>
<req:Password>***</req:Password>
</req:AuthenticationToken>
</soapenv:Header>
<soapenv:Body>
<req:getRequisitionStatus>
<req:loginUserName>***</req:loginUserName>
<req:requisitionId>123456</req:requisitionId>
</req:getRequisitionStatus>
</soapenv:Body>
</soapenv:Envelope>
Here i have to add the additional HTTP header with this request.

OdiIinvokeWebService - SOAP - HTTP header

Using OdiIinvokeWebService and HTTPS protocol, can an HTTP header be passed with the SOAP request?
Thank you

I am sending the SOAP request through SoapUI.
Here is the sample request which i have used.
<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:req="http://requisition.api.newscale.com">
<soapenv:Header>
<req:AuthenticationToken>
<req:Username>***</req:Username>
<req:Password>***</req:Password>
</req:AuthenticationToken>
</soapenv:Header>
<soapenv:Body>
<req:getRequisitionStatus>
<req:loginUserName>***</req:loginUserName>
<req:requisitionId>123456</req:requisitionId>
</req:getRequisitionStatus>
</soapenv:Body>
</soapenv:Envelope>
Here i have to add the additional HTTP header with this request.

Adding soap action in http header

Similar Messages

Maybe you are looking for