Soap Header support - wscomplie

I'm using Sun's wscompile tool to generate th TSI's . While wscompile "successfully" finishes compiling, it generates the following warnings
warning: ignoring header "Header" of binding operations "WorkCentersBITBIV.List" .
The proxies thus generated do not have the SOAP Header support .
Are SOAP Headers not supported by JWSDP1.2 or am i doing something wrong? The relevant part of the WSDL is as below .
Thanks,
Sai.
<message name="WorkCentersBITBIV.List">
     <part name="Request" type="typeens:Requesttype"/>
     <part name="Header" type="typeens:RequestHeadertype"/>
</message>
<binding name="WorkCentersBITBIVListBinding" type="wsdlns:WorkCentersBITBIVListPort">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="WorkCentersBITBIV.List">
<soap:operation soapAction="http://List.WorkCentersBITBIV.BOI.baan.com/action/WorkCentersBITBIV/List"/>
<input>
     <soap:body parts="Request" use="literal" />
     <soap:header message="wsdlns:WorkCentersBITBIV.List" part="Header" use="literal" />
</input>
<output>
     <soap:body parts="Result" use="literal" />
</output>
</operation>
</binding>

We have a problem with using 3 operations. Whenever we compile using wscompile it generates similar warning for the 2nd and the 3rd operation but never for the 1st operation.
Anyone has a clue as to what can be the workaround?

Similar Messages

SOAP Header Support

Are SOAP headers supported in OC4J 9.0.3?
I notice that in OC4J 9.0.4 the proxy code provide the request header support method _setSOAPReaderHeaders(). Is this method also available in OC4J 9.0.3?

We have a problem with using 3 operations. Whenever we compile using wscompile it generates similar warning for the 2nd and the 3rd operation but never for the 1st operation.
Anyone has a clue as to what can be the workaround?

Passing Soap Header in Web Service

Hi Team,
In our application, we have used web service through webservice proxy wizard using the WSDL file. Now due to security reasons we need to pass Soap Header in the webservice call. Can you please help on how to pass soap header in the webservice call ?
Please find the below webservice code/
Long ll_ret
edpmdata ll_ReturnVal
edpmreq lnv_Request_data
//filter lnv_filter
Datawindowchild dwc_child
str_pass l_str_pass
long l_l_row_count, l_l_row
String l_s_code, l_s_modify, l_l_ret
String str_proxy_name = "sohedpmservice"
String l_s_delivery_pref, l_s_email
String ls_url, l_s_ini_file
l_s_ini_file = g_nv_ini.fnv_get_name ()
ls_url = ProfileString(l_s_ini_file,"External", "EDPM_URL", "")
Soapconnection lsc_Conn
sohedpmservice lproxy_obj
lsc_Conn = create Soapconnection
SetPointer (Hourglass!)
Try
ll_ret = lsc_Conn.CreateInstance(lproxy_obj, str_proxy_name, ls_url)
Catch (SoapException e )
Error.fnv_error("0001", This, "ue_process_fields","Error Creating Instance","",FALSE,1,0)
Message.ReturnValue = -1
RETURN -1
end try
IF ll_ret <> 0 THEN
Error.fnv_error("0001", This, "ue_process_fields","Error Creating Instance","",FALSE,1,0)
Message.ReturnValue = -1
RETURN -1
END IF
Try
lnv_Request_data = create edpmreq
lnv_Request_data.value = l_s_party_key
ll_ReturnVal = lproxy_obj.getcommpref(lnv_Request_data)
If ll_ReturnVal.ws_serviceresult.resultcode = '5' Then
Error.fnv_error("0001", This, "ue_process_fields",String(ll_returnval.ws_serviceresult.ws_resultinfo) ,"Error Response ", FALSE, 1,0)
Message.ReturnValue = -1
RETURN -1
End if
l_s_delivery_pref = ll_ReturnVal.deliverymethod
l_s_email = ll_ReturnVal.emailaddr
i_str_pass.s[86] = l_s_delivery_pref
i_str_pass.s[87] = l_s_email
i_str_pass.s[88] = l_s_party_key
Catch ( SoapException a )
Error.fnv_error("0001", This, "ue_process_fields","Error Response","Error Response",FALSE,1,0)
Message.ReturnValue = -1
RETURN -1
end try
Destroy lsc_Conn
Return 1

What version of PowerBuilder?
PB.Net or Classic?
Are you using the SOAP or .Net Engine (if using Classic)?
What kind of header?
There is limited support for passing custom headers in the .Net engine in Classic. The header would need to be defined in the WSDL for the service.
Anything beyond that (e.g., WS-Security) would need to be handled in a WCF client in PB.Net.

Using Message ID in the SOAP header (Sender)

Hi Experts,
The scenario is SOAP to IDoc.
We have requirement to insert the Message ID in the SOAP header for avoiding duplicate messages from the SOAP client.
Please note SOAP client is unable to support URL parameter, so we have to use Message ID in the SOAP header.
So please suggest how to insert the Message ID in the SOAP header (WSDL) , and do we need to implement any mapping to retrieve the Message ID value from the SOAP header - to create a PI message.
Thanks in advance.
MK

But I want to know how we update the WSDL with the required Feild(messageID).
I dont think you can update the wsdl url to include the messageID field...if you notice the other fields in the wsdl you will find all are static...however your messageID will be dynamic.....so just ask the SOAP client application to append the MessageId field and send the message.....at runtime the message id will be extracted by PI......did you test the scenario?...if no then test it once so that if there is an error we will come to know...
Regards,
Abhishek.

How to Digital Signature Payload not SOAP header

Hi Gurus,
How to Digital Signature Payload not SOAP header.
Thanks,
imommam

Hi Imommam,
As of now B2B does not have support for it. If you have any specific requirement, please log a SR with support.
Regards,
Anuj

Passing Parameter through SOAP Header in ODIInvokeWebService

How to pass parameters in SOAP Header in ODIInvokeWebService and not just in SOAP Body?
Background:
One of our web service provider expects certain parameters set in SOAP Header. Currently, ODIInvokeWebService allows to set parameters through SOAP (Request) Body and not through SOAP Header.
How can we set and send parameters in SOAP Header when using ODIInvokeWebService. Can we set this in a request file. Any workaround?
BTW is this a limitation in the tool. If yes, I am looking for a work around. I can setup a proxy service/servlet and re-route the request to the provider but I would like to know if there is a work that can be done easily through ODIInvokeWebService before I look for other options.
Appreciate your help.
Thank you.
-Muthu

Hi Muthu ,
This is not supported by the ODIInvokeWS Tool.
There are some ER logged against this and may be it will get implemented in ODI 11g
Sutirtha

Accessing Soap header in webservices

Hi,
My webservice needs to read a soap header "locale" and do some processing based on this soap header.
I understand the concept of handlers..but anywhere I see examples, the handler handles it and returns the data back.
My requirement is that once this locale is retrieved, each of the webservice method should be able to read this locale, and do some processing based on that, as they need to return the localized data.
I am not sure if I am missing something, but not yet able to find a direct way of doing it..
Any response would be highly appreciated..
Thanks

user10455639 wrote:
Yes I can..what I still dont understand from yourr email is why are you askign this..
"if you can get the soap header"
Because any header we should be able to retrieve from this context...Because I saw the following statement from [JavaDoc | http://e-docs.bea.com/wls/docs103/javadocs/weblogic/wsee/jws/JwsContext.html#getInputHeaders()].
<<<<<<<<<<
....The SOAP headers used by WebLogic Workshop to manage conversations are included in the list of headers returned.
<<<<<<<<<<
If it works, then just use it :) because it is public supported
Edited by: LJ on Apr 23, 2009 10:04 PM
Edited by: LJ on Apr 23, 2009 10:21 PM

Web Services Test Page: No input fields for SOAP header parameters?

Hello,
we're using OracleAS / OC4J 10.1.3.1 and have developed a web service that has some self defined SOAP header parameters.
I would like to use the Web Services Test Page provided by the OAS but it seems that there is no opportunity
to provide input values for these SOAP header parameters.
Do I miss something there or is it not supported by OAS?
I've read the documentation but could not find a clue.
any help is appreciated,
Regards,
Martin

I hear you. As you have probably heard, OC4J is being replaced by WebLogic Server and the 10.1.3.x releases are the last that will be produced. We'll do maintenance on it of course, but little/no new feature work. This would be a new feature we'd have to add, so I'm afraid there's not much chance in having it done.
It's not ideal, and of course more work for you, but if you want to provide your client with a test page that exposes the SOAP headers as form fields, you could always develop and ship one yourself.
-steve0

SOAP header ReliableMessaging was not understood

Dear Friends,
I am working on File to Soap scenario.
In File I have selected QoS as EO.
From ECC File is picking but posting to target system is not working.
In RWB I got the following error. i.e
Received XI System Error. ErrorCode: ADAPTER.SOAP_EXCEPTION ErrorText: soap fault: SOAP header ReliableMessaging was not understood. ErrorStack:
Please give me support.
Thanks & Regards,
Shalini Shah.

Hi,
ReliableMessaging header only supports "BestEffort", "ExactlyOnce" or "ExactlyOnceInOrder" values ... Are you setting this QoS using your own way (and using QoS acronyms - EO, EOIO, BE - instead of those values) or using adapter's settings ?
Rgds
Chris

Generating Web Service with SOAP Header

Hello,
I have a WSDL for a web Service using document encoding and with a soap header.
I generate a jws file using WL Workshop 81.SP4 but I always have this error message :
ERROR: AjoutContactService.jws:13: The binding for AjoutContact does not declare one part.
ERROR:      SUGGESTION: A document literal binding must have at most one part. Make sure you have a WSDL that declares just one part for each message with a document literal binding.
The header is a recent adding on an existing Web Service, and I can't change the wsdl definition. I also need to use data contained by the header in conjunction with data in the body.
Is it a limitation with workshop or a problem with with my binding file ?
I give sample of my two wsdl files.
Given wsdl file
     <wsdl:message name="inputAjoutContact">
          <wsdl:part name="body" element="xsdin:NouveauContact"/>
<wsdl:part name="header" element="xsdinhead:EnTeteRequete"/>
     </wsdl:message>
     <wsdl:message name="outputAjoutContact">
          <wsdl:part name="body" element="xsdout:StatutAjoutContact"/>
     </wsdl:message>
     <wsdl:message name="faultAjoutContact">
          <wsdl:part name="body" element="xsdfault:Exception"/>
     </wsdl:message>
     <wsdl:portType name="AjoutContactPortType">
          <wsdl:operation name="AjoutContact">
               <wsdl:input name="ParametresEntree" message="tns:inputAjoutContact"/>
               <wsdl:output name="ParametresSortie" message="tns:outputAjoutContact"/>
               <wsdl:fault name="ParametresException" message="tns:faultAjoutContact"/>
          </wsdl:operation>
     </wsdl:portType>
binding file
          <wsdl:operation name="AjoutContact">
               <soap:operation soapAction="urn:#AjoutContact"/>
               <input>
<soap:header part="header" use="literal"/>
<soap:body parts="body" use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
<fault name="ParametresException">
<soap:fault use="literal" name="ParametresException" />
</fault>
     </wsdl:operation>

Hi,
This appears to be a known limitation and is addressed by CR227689
which has a workaround that needs the wsdl to be modified.
I am not sure if this is possible given that we don't control the wsdl most times.
Could you please open a BEA support case and refer to CR227689?
Vimala-
p.s:
I found some info on the issue which could help:
1) Refer to <http://lists.oasis-open.org/archives/regrep/200306/msg00071.html>
you will see that only one part is allowed in the message part for doc/literal webservices Snippet from the above link
"Also, keep in mind that WS-I BP permits only one <part> on document/literal messages, so to be WS-I compliant, you would have to include it in the message structure. "
2) Refer to http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html#refinement35722968 <http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html>
below R2208)
"For document-literal bindings, the Profile requires that at most one part, abstractly defined with the element attribute, be serialized into the soap:Body element."
This implies Soap body contains message which contains a at most one part.

Extension of Standard SOAP Header Information in SOAP Adapter

We are currently trying to call an eBay Web Service via SAP XI and we are using the SOAP Adapter in XI to achieve this.
The following Authentication Information is required in the SOAP Header for accessing the eBay Web Service:
- Token
- ApplicationID
- DevelopmentID
- CertificationID.
Unfortunately, the standard SOAP Adapter supports only certain SOAP Header Information (like User Authentication or Certificate Authentication).
Is it possible to extend the SOAP Header Information in the SOAP Adapter (or somewhere else in XI) beyond the standard configurations?
Thanks for your support.
Alexander Bange

Hi Jin,
thanks for your input and sorry for my late reply but I wanted to wait for feedback from SAP who actually confirmed your recommendation.
I had a second thought about this and it came to my mind that I actually don't want to extend the SOAP Header elements but simply fill the mentioned authentication elements with values. This cannot be done in the message mapping as only the SOAP body elements (i.e. the payload) can be mapped.
Do you know if and how I can fill the SOAP header elements with values in XI?
I already tried to include this information as fixed values in the WSDL description and load it into XI. Then I looked into the WSDL description and an error message occured stating that XI could not parse the XML Document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(:main:, row:18074, col:54)).
If there is no solution for the latter, I will have to try nosoap solution. Still this would be a little awkward.
Thanks again for your valuable support.
Best Regards.
Alex

Access SOAP:Header section

Hello,
I need to call a WebService with some extensions in the SOAP:Header. I don't find a solution without a custom develop Adaptermodul which renders the whole SOAP request and uses the SOAP Adapter without the SOAP functions.
What do you think ?
Regards,
Gerald

Hi,
We have the same problem with SP14.
Looks like the soap adapter can't handle soap headers correctly.
A workaround may be to use the http adapter instead and generate the xml envelope messages for request and parsing the response. We have tried this for document based soap and it works.
Obbviously you would like to have the soap adapter fixed so it can support soap headers.
Best regards otto

Weblogic 7 sp2 missing SOAP header

Hi, I have been using a JAX-RPC Handler to add an element to the SOAP header of
my requests. Everything was working fine until I upgraded from Weblogic 7 to
Weblogic 7 service pack 2. Now, the server doesn't see the SOAP header that I
have inserted.
I can see the header when I print out the SOAP message in my Handler. I even
added a second handler, just to verify the header was being saved. However, when
I use a utility to view the network packets going from the client to the server,
I can see clearly that the header information is not being included.
Downgrading from service pack 2 makes everything work again, but I would prefer
not to do that. Any clue why my SOAP header is missing?

Bruce Stephens <[email protected]> wrote:
Hello,
This is a known problem. Please contact support ([email protected]) for
a
patch.
Thanks,
Bruce
jagar wrote:
I've come across the same problem with WLS 7.0 SP2. Any Idea how thisissue got
resolved?
thanks,
jagar.
"Chun Hsu" <[email protected]> wrote:
Hi, I have been using a JAX-RPC Handler to add an element to the SOAP
header of
my requests. Everything was working fine until I upgraded from Weblogic
7 to
Weblogic 7 service pack 2. Now, the server doesn't see the SOAP header
that I
have inserted.
I can see the header when I print out the SOAP message in my Handler.
I even
added a second handler, just to verify the header was being saved.
However,
when
I use a utility to view the network packets going from the clientto
the server,
I can see clearly that the header information is not being included.
Downgrading from service pack 2 makes everything work again, but Iwould
prefer
not to do that. Any clue why my SOAP header is missing?
CR102544 has been filed for issue.
thanks
Jong

Create XML with digital sign and SOAP header...

Hi.
With ABAP, I need create an XML file iwith SOAP envelope. The message has to be signed and the sign data saved in the ws-security part in the SOAP header. I have to sign the file with a X509v3 certificate in base64.
Somebody can tell me how can create the SOAP header and sign it with ABAP for the XML.
Thanks.

Please refrain from implementing WS-Security yourself.
NWAS ABAP 7.x provides support for WS-Security - in both roles, as Consumer and Provider.
The right approach is to generate a proxy based on a given WSDL.
What kind of (message-based) authentication is demanded by the WS Provider?
Other info source: see https://wiki.sdn.sap.com/wiki/display/Security/SingleSignonforWeb+Services
Edited by: Wolfgang Janzen on Jul 8, 2009 12:11 AM

WS-Security: Custom/Proprietary tokens in SOAP Header

Hi All,
We are conusming a web service hosted by an external system. They seem to support WS-Security, but they need custom/propriety token for the field <wsse:BinarySecurityToken/> in the SOAP header,
Is there any possiblity to use standard Web Services Security profile in SOAP receiver adapter and achieve this task.
Thanks for your time.
Best Regards,
Sudharshan N A

Hi,
how are you testing? do you use the test page from enterprise manager? If so, change the input to "XML View" and add the SAML Header. They usually look like this
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
<env:Header>
<wsse:Security env:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<saml:Assertion MajorVersion="1" MinorVersion="1" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" AssertionID="SAML-MYBrexylXmDyTN9kS08Ygw22" IssueInstant="2011-06-21T12:43:52Z" Issuer="www.oracle.com">
<saml:Conditions NotBefore="2011-06-21T12:43:52Z" NotOnOrAfter="2011-06-21T12:48:52Z"/>
<saml:AuthenticationStatement AuthenticationInstant="2011-06-21T12:43:52Z" AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password">
<saml:Subject>
<saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">tester1</saml:NameIdentifier>
<saml:SubjectConfirmation>
<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>
</saml:SubjectConfirmation>
</saml:Subject>
</saml:AuthenticationStatement>
</saml:Assertion>
</wsse:Security>
</env:Header>
<env:Body>
</env:Body>
</env:Envelope>
cheers Nicolas

Soap Header support - wscomplie

Similar Messages

Maybe you are looking for