Setting up the Soap Header when consuming a web service.

Hi SDN,
I am trying to consume a web service,where I need to pass the soap header for sending the request to the sever.
I am using if_ws_protocol_ws_header->SET_REQUEST_HEADER to set the Username and Password to the soap header. After a lot of trouble shooting I came to conclusion that the Username and Password are not being updated in soap header.
I want to know how to set the soap header? I have tested the web service in the SOAP UI testing tool and it works fine taking the credentials. The webservice is using HTTPS protocol.Do we have any separate config for https. Do I need to pass the nonce and date created in the soap header for sure ? And is there any thing to be configured by basis team?
Here is what I am trying to pass:
' <soapenv:Header>'
      '<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">'
         '<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">'
            '<wsse:Username>XXXXXXX</wsse:Username>'
            '<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">XXXXX</wsse:Password>'
            '</wsse:UsernameToken>'
     ' </wsse:Security>'
      '/soapenv:Header>'
Thank you.

CONCATENATE
'<soapenv:Header>'
'<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"'
'xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"'
'xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">'
'<wsse:UsernameToken>'
'<wsse:Username>XXXXXX</wsse:Username>'
'<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">XXXXXX</wsse:Password>'
'<wsse:Nonce>' XXXXX'</wsse:Nonce>'
'<wsu:Created>' XXXXX '</wsu:Created>'
'</wsse:UsernameToken>'
'</wsse:Security>'
'</soapenv:Header>'
INTO l_string.
I solved my self and its working , Here is what I was passed.
Thank you guys.

Similar Messages

Error when consuming a web service in CF 11

I am consuming a web service in ColdFusion what was written in .NET. Some methods of the web service work fine, but some we get the below error. We have identified the issue is the name of one of the properties in the web service appears to be the issue. The property name is ID. This is a very common property name so I would think someone has run across this before. It appears that maybe ID is a default property for Axis? I can dump the method that works and I see there is a getID() method with a return type of org.apache.axis.types.Id.
If we change the name of the property to something other than ID it works, but this will cause us to refactor a lot of code.
Here is the error I get when I try to call GetRoles method, which contains an ID property:
Cannot perform web service invocation GetRoles. The fault returned when invoking the web service operation is:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: For input string: "i1"
java.lang.NumberFormatException: For input string: "i1"
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: For input string: "i1"
java.lang.NumberFormatException: For input string: "i1"
at org.apache.axis.encoding.ser.BeanDeserializer.onStartElement(BeanDeserializer.java:462)
at org.apache.axis.encoding.DeserializerImpl.startElement(DeserializerImpl.java:393)
at org.apache.axis.encoding.ser.BeanDeserializer.startElement(BeanDeserializer.java:154)
at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java: 1048)
at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
at org.apache.axis.message... ''
I am running CF 11 Update 4.

I am not passing any parameters to the method (it has no parameters). On the ColdFusion side I do not use i1 anywhere. I will check with the .net developer on Monday to see if he is using it anywhere in his code. If he is he is using in consistently as the only methods that work from his service are those that do not have an ID property. All services with an ID property give me the same error message.

Passing SOAP header while invoking a web service partner link from BPEL

I followed the steps of adding bpelx.inputheadervariable. Which is supposed to add the soad header. But after running the BPEL process if I see the message in the console, I don't see the SOAP header. Is there any way to see how the SOAP header is passed or did I set it incorrectly?
This is what the message looks like:
<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:Header>
<ns0:Context xmlns:ns0="http://www.informatica.com/wsh">
<SessionId>[string]</SessionId>
</ns0:Context>
</soap:Header>
<soap:Body>
<ns0:StartWorkflow xmlns:ns0="http://www.informatica.com/wsh">
<DIServiceInfo>
<DomainName>[string]</DomainName>
<ServiceName>[string]</ServiceName>
</DIServiceInfo>
<FolderName>[string]</FolderName>
<WorkflowName>[string]</WorkflowName>
<WorkflowRunId>[int]</WorkflowRunId>
<WorkflowRunInstanceName>[string]</WorkflowRunInstanceName>
<Reason>[string]</Reason>
<Attribute>
<Name>[string]</Name>
<Value>[string]</Value>
</Attribute>
<Key>
<Key>[string]</Key>
<mustUse>[boolean]</mustUse>
</Key>
<ParameterFileName>[string]</ParameterFileName>
<Parameters>
<Parameters>
<Scope>[string]</Scope>
<Name>[string]</Name>
<Value>[string]</Value>
</Parameters>
</Parameters>
<RequestMode>[ETaskRunMode]</RequestMode>
<TaskInstancePath>[string]</TaskInstancePath>
<IsAbort>[boolean]</IsAbort>
<OSUser>[string]</OSUser>
</ns0:StartWorkflow>
</soap:Body>
</soap:Envelope>
I am trying to invoke the 'startworkflow' operation of Informatica web service Dataintegration.wsdl
Edited by: user611166 on Apr 1, 2010 10:10 AM

Hi,
Try using obtunnel with your bepl console.
Alternatively, if your server is on unix/ linux, try tcpdump to capture packets to a particular server and then open the file in wireshark to analyse the contents.
Wish SOA suite would allow us to view this by default!
Regards,
Sappy

Can't find where to update SOAP header request on a Web Service

Hello,
I am consuming a certain Web Service from a remote Server and succefully created a client proxy for it.
This Web Service requires a String parameter (which is the licence key) to be inserted in the SOAP request header. I've searched at the client proxy I created under Virtual Interface, Web Service Definition and under Web Service Configuration but couldn't find an option which allows me to modify the SOAP header request.
At this link:
http://help.sap.com/saphelp_nw04/helpdata/EN/a2/99af4e693dee43a0519e029549647b/content.htm
There is an explanation on how to transfer existing request parameters from the SOAP body to the SOAP header, but I want to add the header new parameter except the exsiting parameters the Web Service request expects.
I can of course write the request myself but than I loose the whole wizard advantage...
Can someone please tell me where can I find it?
Roy

Ralph Landry1, your link just sends them to the links I provided.
If you have an iPod touch:
For Windows: See iPhone, iPad, or iPod touch: Device not recognized in iTunes for Windows
For Mac OS X: See iPhone, iPad, iPod touch: Device not recognized in iTunes for Mac OS X

Managing cookies when consuming external web services

I am trying to use an external webservice from within an Oracle 10g database (i.e. database is client).
I have the WSDL for the web service, and have successfully imported the JPub-generated Java classes and PL/SQL wrappers to the database.
I am also able to use the web service, but a small detail is missing:
The web service returns a cookie, that has to be set for all subsequent calls to the web service.
How (if at all possible) is this achieved, when I only have the limited PL/SQL wrappers at my disposal?
I have tried to call the (object).setMaintainSession(), and set the value to true (=1 for PL/SQL), but no help there...
I have tried the OWA_COOKIE, OWA, UTL_HTTP packages to see if I can retrieve the cookie from the response in any way, but so far without success.
Any help would be greatly appreciated.
System-info: Oracle 10.2.0.3 (Sun Unix)

After working offline with Chew Ling on this issue, the cause was found to be a mismatch between the java archive files that are loaded when the local OC4J or embedded JDeveloper OC4J runs, and the database driver JAR file that exists in the c:\e900\MISC folder. This is a configuration problem which particularly affects development clients that use a local Oracle database, including the Standalone Oracle DB install that Chew Ling is using, and is a known problem (ref: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=859688.1).
The list of jars that are loaded by the OC4J is held in the C:\e900\system\Classes\SBFProjects.library file, and the solution is to add the ojdbc5.jar Oracle DB driver file to the list.
Dave

How to include the NIWebAppServer.conf when building a web service installer in LV2010

Hi all,
I'm build a LabVIEW 2010 web service and creates a deployable setup installation as described in Web Services FAQ:
http://zone.ni.com/devzone/cda/tut/p/id/7747#toc12
but also would like to include my .conf file for the NI Application Web Server. The file is located in:
C:\Program Files\National Instruments\Shared\NI WebServer\NIWebAppServer.conf
This is where all settings (listening ports, SSL, users etc.) are configured.
If I look in LabVIEW 2009 build instructions for web services:
http://digital.ni.com/public.nsf/allkb/62B9C2D5C91EE8B28625778800609FF2?OpenDocument
they include this file, but it is a new procedure in LV2010 (as seen in the top link) and I can't seem to get this conf file included and installed on the deployed system automatically for LV2010. Today, I must copy it manually.
Any ideas of how to do this?
Thanks,
Mattias

Having the same problem, even if pointing the installer to install the particular file, the installer will install its own some default file. Did you find any solution?
/Carl

Proxy error when consuming External Web Service (WSDL) in ABAP

Hi all,
I am trying to consume an external WS in ABAP but I have some issues :
1. Is it allows to use tag <xsd:complexcontent> with restrictions and extensions in it ? If not, how can I replace it ?
2. Do we need to still change the <complexType> structure such as :
Coding, not working:
<xsd:complexType name="OrderRequestMsg">
<xsd:sequence>
<xsd:element name="shop" type="xsd:string"/>
u2026
</xsd:sequence>
</xsd:complexType>
<message name="OrderRequest">
<part name="input" type=" tns:OrderRequestMsg"/>
</message>
Coding, working::
<xsd:element name="OrderRequestMsg">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="shop" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<message name="OrderRequest">
<part name="input" element="tns:OrderRequestMsg"/>
</message>
3. When I am testing the WSDL they send me in SOAPUI, I don't have any issue but when I am trying to integrate in ABAP, it is blocking on an URL saying it cannot find it (the URL http://fk.se/SHS/xsd/tanden)
<xsd:schema version="20110317" targetNamespace="http://fk.se/SHS/xsd/tanden" xmlns:tns="http://fk.se/SHS/xsd/tanden" xmlns:xmime="http://www.w3.org/2005/05/xmlmime" elementFormDefault="qualified" attributeFormDefault="unqualified">
Do I need to change something ? Since when I am modifying it, it cannot find the type reference afterwards...
Thanks in advance for your answer.

Hy Brad, I got the same error by trying to generate a 'Consumer Proxy' from a external WSDL. u2019Incorrect value: XSD name space not available'. I have solved it in this way: The report RSSIDL_DESERIALIZE_DEMO has the same check routines as the R3-Proxy Generator. I debugged this report using a saved external WSDL and compared it with using a saved WSDL (Server) generated under /nse80.
-> In the WSDL, in part message the "type" isnu2019t allowed, because the dezerialization is done already.
Coding, not working:
<xsd:complexType name="OrderRequestMsg">
<xsd:sequence>
     <xsd:element name="shop" type="xsd:string"/>
      u2026
</xsd:sequence>
</xsd:complexType>
<message name=" OrderRequest">
<part name="input" type=" tns:OrderRequestMsg"/>
</message>
Coding, working::
<xsd:element name="OrderRequestMsg">
    <xsd:complexType>
       <xsd:sequence>
        <xsd:element name="shop" type="xsd:string"/>
   </xsd:sequence>
</xsd:complexType>
</xsd:element>
<message name="OrderRequest">
     <part name="input" element="tns:OrderRequestMsg"/>
</message>

How do pass the UserID and Password in the SOAP header for web services

I am encountering issues trying to pass the userid and password in the SOAP header when consuming a 3rd party web service. Rostewitz posted something similiar but I don't know how to type iv_xml. Any help would be greatly appreciated.
Thank you,
jpina

It helps to post a link to a thread when you refer to it. If you are trying to implement that solution though, you can look at the parameter of the corresponding method being called. The parameter has type 'SIMPLE' which means that it is compatible with all of the predefined elementary ABAP types. In this case, you should use 'STRING'.

WSSE usename token not in the SOAP Header

Background:
Webservice with four methods; OpGet, OpCreate, OpGetList, OpSet. Setup a jcx with this webservice URL, generate a test harness from workshop, and running this test harness and looking at the SOAP messages being send and received to verify that the web services are working. The OpGet is working since it doesn't require user credentials. But the OpCreate is currently not working. Remedy is rejecting it because of access control.
Problem #1:
Need to pass the user credential in the SOAP header. Here's the required information in WSDL regarding Authentication.
<wsdl:operation name="OpCreate">
<soap:operation soapAction="urn:SimpleWebService/OpCreate" style="document"/>
<wsdl:input>
<soap:header message="s:ARAuthenticate" part="parameters" use="literal">
</soap:header>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
Solution that I have implemented so far:
I have setup a WSSE file with the simple username/password in the <wsSecurityOut> element and was expecting to see this in the SOAP Header element in the WSDL message. When I look at the SOAP message in the test harness that I have generated in Workshop, I don't see this credential information. I have set the "ws-security-service property to the wsse file. I know that the harness has seen the wsse file since it gives me warning about having the password in simple text without encryption.
Shouldn't I be seeing this userNameToken information in the SOAP Header when I run the test harness (jws) from workshop? As you can see below (Problem #2) no SOAP header is being generated.
Problem #2:
I see that in the SOAP message that test harness is sending wrong "xsi:type" information. It seems to be sending the "StatusType" for all the parameters except the one "Status" where it needs to?
SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns:OpCreate xmlns:ns="urn:SimpleWebService">
<ns:Assigned_To xsi:type="ns:StatusType">donnab</ns:Assigned_To>
<ns:Short_Description xsi:type="ns:StatusType">testing from weblogic 8.1 SP3 Workshop</ns:Short_Description>
<ns:Status>New</ns:Status>
<ns:Submitter xsi:type="ns:StatusType">donnab</ns:Submitter>
</ns:OpCreate>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Here's the WSDL where the OpCreate is defined:
<xsd:element name="OpCreate" type="s:CreateInputMap"/>
<xsd:complexType name="CreateInputMap">
<xsd:sequence>
<xsd:element name="Assigned_To" type="xsd:string"/>
<xsd:element name="Short_Description" type="xsd:string"/>
<xsd:element name="Status" type="s:StatusType"/>
<xsd:element name="Submitter" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>

I've never been able to see that information because I assume Weblogic server strips it out the minute it receives it and uses it to authenticate the user against a principal in the server.
You can get ahold of this info, though. In your .jws file, in workshop, add this as a context:
/** @common:context */
JwsContext context;
In your web services method, access the context to get the username:
context.getCallerPrincipal().getName();
That will return a String w/ the username passed in the username token.
-Becky

Handling of SOAP Faults in SOAP Clients consuming PI Web services

Hi there,
the following is in regards to SOAP fault error handling in a SOAP client that consumes a Web Service published by PI.
I have been reading a number of threads and blogs in regards to this topic and I am still left with some open questions which I hope to get some final answersclarifications through this thread.
In particular the blogs
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI      - Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
XI: Propagation of meaningful error information to SOAP Client     - XI: Propagation of meaningful error information to SOAP Client
have caused by attention.
Both of these threads are realating to the Fault Message type one can use to return errors back to a SOAP Client (.Net, Java, etc.).
In our scenario we published a number of Web Services through PI that provide functionality to integrate with an R3 back-end system using inbound ABAP Proxies.
The services are standardised and will be consumed by a number of .NetJava applications and systems. The reason for the use of ABAP proxies is the customer specific application logic that is executed in the backend system. The Web services are synchronous and don't use ccBPM in the middle. Transformations are performed in PI combined with various lookups to set default values before the message is passed into the ABAP Framework of the R3 back-end system. The lookups are done against the R3 back-end system using the PI RFC Lookup feature.
The inbound proxies currently return application errors as part of the response message back to the SOAP client. For more critical errors we introduced the use of Fault message types as the method to return the information back to the SOAP Client. This is all working satisfactory.
The questions I have are as follows.
1. When an error occurs at the IE level (e.g. mapping error), ABAP Proxy framework level (e.g. conversion from XML to ABAP format) or Adapter Framework level (Adapter releated error) a different SOAP fault message structure is returned to the SOAP Client than the one    used for the application errors. The SOAP fault message structure used in this case is the standard SOAP fault used by PI to return system errors back to the caller. For those SOAP fault messages there is no payload generated that could be mapped to the SOAP fault structure used for the application errors. This would be preferrable as there would be only one Fault message structure used for both inbound ABAP proxy generated fault messages and PI generated fault messages.
Also the error messages generated by PI can be quite cryptic and difficult to interpret at the client end and could be filtered     ranslated during message mapping if the payload of the PI generated SOAP fault message could be accessed in a message mapping.
Point 3 of the above thread 2759 indicates that this would be possible but doesn't outline how. Could somebody please clarify this for me as I don't believe that this is really possible ???.
My idea instead was to use the PI SOAP fault message structure to also return application errors. Therefore I would create a Fault message type that matches the PI SOAP fault structure. This would enable the SOAP Client to handle only one SOAP Fault error structure. Would that be something to look into instead ?????.
2. We have been looking at using the integrated WEB AS SOAP adapter instead of using the AF Sender SOAP adapter. While playing with this we encountered differences in the content returned through the SOAP fault generated by PI. A sample is below. Shouldn't the content of these SOAP faults be the same if the error that caused it is the same. Also the SOAP fault returned by the IE SOAP adapter is much more    useful in this particular case. Both errors below are the same, a conversion error from XML to ABAP took place in the inbound ABAP proxy framework of the back-end system.
SOAP fault returned when using SOAP Sender adapter of AF
<!see the documentation>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIProxy:PARSE_APPLICATION_DATA:
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
     at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:916)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
SOAP fault using integrated SOAP adapter of PI IE
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>System Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context/>
               <code>ABAP.PARSE_APPLICATION_DATA</code>
               <text>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXSBE20FF604BAFEF8D990A XML Bytepos.: 564 XML Path: ns1:CreatePORequest(1)POHEADER(2)COMP_CODE(1) Error Text: Data loss occurred when converting ############################## Kernel ErrorId: CONVT_DATA_LOSS))</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I have been reading threads for hours without being able to find one that answers questions 1 or provides a blog that outlines the approach one should take for error handling in SOAP clients that consume PI Web Services (and covers both PISystem generated faults and faults raised in Proxies).
There may already be a blog or thread and I just missed it.
Any comments are welcome.
Thanks. Dieter

Hi Dieter,
As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
Kind regards,
Wojciech
btw nice thread

How to populate the SOAP Header in JCD/BP while consuming WebService?

Hello,
I am trying to invoke a external webservice through both JCD/BP in JCAPS513 and as per wsdl defination we need to send user and token information in the SOAP Header. When I imported the WebService defination into the JCDP/BP, I do not see message part corresponding to SOAP Header. Can anyone help me here?
Here is the WSDL message, operation & binding details:
<wsdl:operation name="GetOrderID"> <wsdl:operation name="GetOrderID"> <wsdl:message name="GetOrderIDSoapIn">
<wsdl:part name="parameters"
element="tns:GetOrderID"/>
</wsdl:message>
<wsdl:message name="GetOrderIDSoapOut">
<wsdl:part name="parameters"
element="tns:GetOrderIDResponse"/>
</wsdl:message>
<wsdl:message name="GetOrderIDWebServiceCredential">
<wsdl:part name="WebServiceCredential"
element="tns:WebServiceCredential"/>
</wsdl:message>
<wsdl:input message="tns:GetOrderIDSoapIn"/>
<wsdl:output message="tns:GetOrderIDSoapOut"/>
</wsdl:operation>
<soap:operation soapAction="http://xxxxxx.xxxx.xxx/V2/GetOrderID"
style="document"/>
<wsdl:input>
<soap:body use="literal"/>
{color:#ff0000} *<soap:header message="tns:GetOrderIDWebServiceCredential"*
* part="WebServiceCredential"*
* use="literal"></soap:header>*{color}
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>

Hi Ganesh,
Please go through this link.
http://www.sapag.co.in/SAP-XI-SOAP-Adapter-FAQ'S.html
I think this would be helpful for you..
Reward points if useful,
Swamy Kunche

How to set the SOAP Header while publishing to Queue in the mediator

Hi,
I am trying to publish the message to a JMS AQ, from the Mediator service in the 11g Soa Suite. I want to add some properties as SOAP Header to the message and send it to the JMS AQ. I have seen the mediator process calling BPEL process, passing the SOAP Header values. In the BPEL process, we have the section <soap:binding> inside that I can give the <soap:header>and set the values.
Could any one tell me how to do this in Mediator service which is calling the JMS AQ using adapter?
Thanks,

The solution in this thread is for VS .NET as this is the forum for CR in .NET.
With Foxpro, I suspect you want to create a new thread in the SAP Crystal Reports - Legacy SDKs forum.
Make sure you specify the exact version of CR used.
- Ludek

How to modify the soap header of ebxml control?

I need to change the soap header information of the ebxml control
from
<eb:CPAId>http://www.openuri.org/cpa</eb:CPAId>
to
<eb:CPAId>MyString</eb:CPAId>
and I want to add some additional information to the header such as the wsse feature
<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/12/utility">
<wsse:UsernameToken>
<wsse:Username>1234</wsse:Username>
<wsse:Password>5678</wsse:Password>
<Organization>abc</Organization>
<Domain>DEFAULT</Domain>
</wsse:UsernameToken>
</wsse:Security>
Does anyone know where I can change the type value?
Thanks, Kun

Your code works. But if I place the TextInput in the formItem
and form tags, the Y value becomes 0. You can try this one:
<?xml version="1.0"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml">
<mx:Form paddingBottom="0" paddingTop="0"
paddingRight="0">
<mx:FormItem label="Title:">
<mx:TextInput width="275" id="newSongTitle"/>
</mx:FormItem>
<mx:FormItem>
<mx:Button id="submitSongData" label="Add Song"
width="150"/>
</mx:FormItem>
</mx:Form>
<mx:Text text="{newSongTitle.x}" width="322"/>
<mx:Text text="{newSongTitle.y}" width="322"/>
<mx:Button label="set Y" click="{newSongTitle.y =
newY.value}"/>
<mx:NumericStepper id="newY" value="50" minimum="0"
maximum="400"/>
</mx:Application>

How to add Custom Attributes in the SOAP header for OWSM

Hi,
I like to know how to add the Custom Attributes in the SOAP header for OSWM username token authentication.
Currently we are getting the header element like
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
here we need to add the attribute "soap:mustUnderstand="1" , so the element will look like
<wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
Any info on this will be helpful.
Thanks,
ArunM

Hi Jay, you can make it in more than 1 way.
I suggest you the following:
- create an URL iview that points to any URL you want.
- define a Resource that points to the iview (with a window name, to open in new window)
- define an Area that points to the resource
- add your new Area to the your current Area Group
Regards!

Calling A Secured webservice using Username and password in the Soap header

I want to call a secured webservice.
The Username and password should be sent with the payload in the SOAP Header
as
<wsse:Security S:mustunderstand="0" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken wsu:Id="SecurityToken-XXXXXXXXXXXXXXXXXXXXXXXXX" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>uname</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">pwd</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
Can you please send me the steps?
I tried with giving the username and password under Service Account.
I tried to create a wspolicy under business service. But nothing works...
Please help me at the earliest.
Also please give me steps in sequence.

Now i made sure that the endpoint is available!
Now am getting this error:
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380002: localhost1</faultstring>
<detail>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380002</con:errorCode>
<con:reason>localhost1</con:reason>
<con:location>
<con:node>RouteNode1</con:node>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
Also in the invocation trace i can observe the following things:
Under Invocation Trace:-
========================
     Receiving request =====> Initial Message context
     ===============================================
     under added header:-
     ==================
     <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     </soap:Header>
     under RouteNode1
================
     Route to "TargetMyService_BS"
$header (request):-
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
Under Message Context changes:-
*===============================*
I can find this element also:-
con:security>
*<con:doOutboundWss>false</con:doOutboundWss>*
*</con:security>*
eventhough we enabled ws security, how the above tag can be false?
I think its getting failed to populate the header with the required login credentials.
The other doubt i have is:-
=================
I have chosen the service account type is static...is this right?

Setting up the Soap Header when consuming a web service.

Similar Messages

Maybe you are looking for