Missing WS_HEADER protocol in client proxy

[former_member185943]

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

[athavanraja · Accepted solution]

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

is it webservice infrastructure or XI

Raja

[former_member185943 · Accepted solution]

Thanks, Raja!

[Former Member]

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

[athavanraja]

Alexandre,

check this thread

https://forums.sdn.sap.com/click.jspa?searchID=7170769&messageID=2863997