SOAP Receiver : Dynamic URL configuration vs. TAuthKey capability

[Former Member]

Hello all,

I plan to use dynamic URL configuration of web service URL in SOAP Receiver CC. I got an idea, which is more or less described on SDN already. But one thing bothers me a lot.

In my scenario we talk about 10 and more WebServices' URLs to be called dynamically. The WS call will include also authorization username:passwd and it is expectable, that each WS will have different uname:passwd definition to be authorized with.

I made a capability analysis of SOAP Receiver CC - tab Advanced - Authetication keys and there are prepared only 10 possibilities to define password for authentication key (which I'll handle to CC via TAuthKey parameter).

In the help page http://help.sap.com/saphelp_nw04s/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm there is a note regarding authentication key:

If authentication is required for the receiver system, you can enter a password with confirmation for each key value. This means that you do not need to write passwords in the enhanced message header.

So in other words there should be a way, how to send to CC even the password with other adapter-specific message attributes. (or maybe I miss the meaning of this comment, like the other way is to develope own module for CC and process additional attribs from enhanced message header)

Does anyone have some experience with handling the authentication data in "enhanced message header" ?

Thanx for you info in advance.

Regards

Tom

[Former Member]

Hi all,

I got an idea that the solution could be to use "Enhanced receiver determination" and use a set of Services-CommChannels with special naming convention. With this (little bit complicated) scenarion I'll get a possibility to define more then one SOAP Receiver CC => I'll get more than 10 options to store the logon password.

What do you think ?

Points for ideas guaranteed.

Tom