A quick question about WebDynpro SLD and R/3 with concurrent users

[Former Member]

Hello ,

I have a very quick question about Webdynpros and SLD connecting to an R/3 system, when you configure a webdynpro to connect to an R/3 system using SLD, you configure a user name and password from the R/3 for the SLD to use. What I would like to know is when I have concurrent users of my webdynpro, how can I know what one user did in R/3 and what another user did? Is there a way for the users of the web dynpro to use their R/3 credentials so SLD can access the R/3? Like dynamically configuring the SLD for each user?

- I would like to avoid leaving their their passwords open in the code ( configuring two variable to get the users username and password and use these variables as JCO username and password )

Thanks Ubergeeks,

Guy

[Former Member]

Hi Guy

You will have to use Single Sign On to achieve this. In the destination you have defined to connect to R/3 , there is an option to 'useSSO' instead of userid and password. This will ensure that calls to R/3 will be with the userid that has logged into WAS. You wont need to pass any passwords because a login ticket is generated from WAS and passed on to R/3. The userid is derived from this ticket.

For this to happen you will have to maintain a trust relation ship between R/3 and your WAS ,there is detailed documentation of this in help files. Configuration is very straight forward and is easy to perform

Regards

Pran

[sid-desh]

Hi Pran,

One question. For this to work should there be a user having the same userid in both WAS and R/3. I feel for SSO to work same user id has to exsist in both WAS and the R/3 system.

If this is the case then these users have to configured and RFC users as they will make some RFC calls. So for these users do we need purcahse licences again.

I dont have clarity on this issue.

Please provide some sugestions.

Regards

Sidharth

[Former Member]

Hi,

yes - you are right. If you use ticket authentification between the Web Dynpro engine and the R/3 backend, you have to make sure, that both the Web Dynpro engine and the R/3 backend knows the same users.

This could be achived by setting up the UME in an way, that the R/3 users are also used in the Web Dynpro engine.

The second way could be to create "by hand" the needed users in both systems.

Option 1 is obviously the better one

Best regards

Jochen

[sid-desh]

Hi Jochen,

What about the money part here. For creating these users in the production system do we need to purchase licences for these users.

Can you give some suggestions there.

Regards

Sidharth