DUET User Mapping Architecture

[Former Member]

I am very nearby to be involved on a DUET Enterprise discovery project ... which means to install DUET Enterprise on my customer premises. There is a requirement to connect mutiple back-end systems (ERP,CRM,BW).

From an architecture stand-point customer is targetiing to have one DUET Enterprise FP1 environment (with GW) and to connect it to the 3 back systems.

For historical reasons a physical user has ONE LAN Id (JSMITH for example) but mulitple different SAP Userids (naming conventions are different by backend : JSMITH on the ERP, JSMITH1 for CRM and JSMITHX for BW).

According to the few documents I have read (I am still on the paper exercise) it can create an issue for insuring the DUET user mapping as the mapping table does not include the System Id. It seems that currently for using DUET Enterprise "out of the box" it requires SAP Id allignment if we want to have one DUET Enterprise connected to multiple back-end systems.

Am I right ?

If Yes : if we can not change the userid convention in the back end system what is the potential workaround ?

From a long term point of view does it make sense to have this design ?

We must have similar challenge with SAP GUI SSO where we have a dedicated field in SAP backend user profile.

I hope my observation is clear and accurate as it is based only on paper reading.

Thanks by advance for any help.

[Former Member]

Hi,

although you can easily connect multiple backend system to the Gateway server you are right that the different user-ids will be a problem.

In the "default configuration" you can have a different username in SharePoint, but then the usernames for the Gateway and the connected backend system has to be the same (since we are using Trusted System connections for RFC calls and SAP Assertion Tickets for Web Service calls). Both technologies currently do not support a usermapping that you would require.

There migth be workarounds (like trying to use SAML for authentication to connect to the backend system in which you could perform a usermapping), but this depends very much on the version of the backend system.

Especially from a long term perspective I think it would make more sense to have a common set of users Ids accross all your system (and I know that this is not a small project...).

Regards,

Holger.