How to configure WS Addressing via soamanager?

[Former Member]

Please look as this forum question to:

Can you tell me how to configure ws addressing via soamanager for a consumer proxy (logical port) ?

Now we have searched for two days without a answer. We find some information about WebService Addressing is supported from SAP:

http://help.sap.com/saphelp_smehp1/helpdata/de/44/624479f7e608fae10000000a422035/frameset.htm

And we find in soamanager configuration -> logical port -> WS Addressing

There are two opportunities:

- Protocol: WS-A

- Paramater:

We donu2019t know what parameter we have to enter for wsa to. Please, can you give us some hint?

Thanks in advance

[Former Member]

While creating logical port use wsdl and everything will be set accordingly. WS-A addressing not mandatory to set and you can leave it to default.

Configuration of WS-A depends on services you are consuming, either opt for "Suppress..." option or leave it to default.

Regards,

Gourav

[Former Member]

But I need to configute wsa to without wsdl file. So please help to configure "wsa to" manually.

Nobody an idea how to configure "wsa to" manually?

Edited by: SAP User on Apr 5, 2011 4:28 PM

[Former Member]

Hi SAP user,

I don't think there is any problem configuring WS-A manually, you can select either of the options but you must make sure what your service provider support, so better first check with service developer or view wsdl (if available) to see if it support WS-A.

Usually 3rd party services (in .Net) not configured for WS-A so you should suppress id transfer else keep the default which is selected there.

I strongly recommend to use wsdl to configure proxy and it will pickup required settings automatically else use "trial and error" approach.

Regards,

Gourav

[Former Member]

The service provider supported web service addressing (wsa).

1. Logical Port based on WSDL:

If I use wsdl file for creation of logical port I get the following error:

SRT framework exception. Error on WSDL-Parsing. Exception on Library-Handler

Any idea where can I find more information about that error? Maybe in the Log file? I have no ideau2026 Any hint to solve the problem?

2. Logical Port u2013 manually:

For wsa-to I need to configure:

a) An endpoint which I define in soamanager-> transport settings -> transport bindings

e.g. URL Access Path: <ServerName>

URL Access Path: <path>

b) An WSA-To destination endpoint reference: I donu2019t know where and how to insert the endpoint referenece in soamanager

3. Does anybody know how to insert reference parameter via soamanager (webservice addressing): Should it be key value pairs in u2018u2019 or u201Cu201D or xml-syntax? Please can anybody post an example for reference parameter.

Thanks in advance

[Former Member]

Hi,

Please check if you got correct wsdl, try to open it in internet explorer and test wsdl address in SOAP UI or WSNavigator.

Check how you are passing wsdl to create logical port (add "?wsdl" at the end of url if it is not there)

WS-A parameters are in SOAP header and SOAP Runtime will take care of adding required parameters in SOAP header, just configure what is asked in Logical Port (no additional parameter required).

Under "Messaging" tab you can define whether to use WS-A message ID or SAP Message ID or want to suppress Id transfer.

I again want to stress on the point that you should use WSDL (file or URL) to create endpoint to set all required parameter automatically, if you want to configure manually then you must know wsdl endpoint address etc.

Regards,

Gourav