Skip to Content

Missing WS_HEADER protocol in client proxy

Hi!

I generated a client proxy to consume services from 3rd party application, wanted to use standard SAP WS security with user and timestamp, logical port with security profile didn't work, used proxy's header protocol to create my own security header and it worked fine.

Then I generated the new proxy with different set of services from the same application and wanted to do the same thing. To my surprise, there was no header protocol. I debugged the GET_PROTOCOL method and saw that the proxy's attribute table PROTOCOLS does not contain the WS_HEADER protocol (class CL_WSPROTOCOL_WS_HEADER), but instead of it XI_HEADER (CL_WSPROTOCOL_XI_HEADER). I can't use XI protocol (or at least don't know how) - it's completely different and has no SET_REQUEST_HEADER method.

Why in the world would 3rd party application use XI? Can I find this somewhere in WSDL? I have no idea - please give me some hints.

Thanks in advance!

Igor

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jun 04, 2007 at 08:11 AM

    can you check in LPCONFIG transaction what runtime is used (under general settings)

    is it webservice infrastructure or XI

    Raja

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 07:27 PM

    Hi Igor,

    Can you tell me how do you have called your external WebService that uses standard WS Security with user and password, using the proxy's header protocol?

    I'm trying to do it but I keep getting the following error: "SoapFaultCode:1 WSDoAllReceiver: Request does not contain required Security header".

    Can you give me a example how did I do it?

    I've tried also with the logical port's security profile but with no success.

    Thanks in advance!

    Alexandre

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.