Webdynpro - Check if a portal user has a user in R/3 Backend

[Former Member]

Hi Experts,

i have following problem, and maybe some of you can help me out with an idea or (much better) a solution:

Our Company is running an Enterprise Portal on NW2004s (SPS 18). Currently i am developing a Java WebDynpro Application for the portal called Transactionstarter. Withhin this application a portal user can simply add a backend System (R/3), a transaction and a Description. This information will be stored in a xml file in userhome in KM. When the user clicks the description, SAP WinGui will open with the transaction he defined before. We use SSO for opening the transaction if the user has a backend user. If not, the loginscreen of the backend will appear.

All this works fine.

Now we have the requirement for an automated system check.

The portal user can run an initial system check. This system check should check all configured backend systems if the portal user has a user in R/3 backend.

But how can i check if my portal user exists in backend?

I cannot use JCO because we have a lot of Systems (more than 300 all together) and i don´t want to create a destination for every system. Or did i misunderstood something with JCO?

Does anyone of you have a solution, how i can check every system, if the portal user has also a backend user?

Thanks in advance.

Regards

Pascal

[Former Member]

Hi Pascal,

with JCO you can use also the method JCO.createClient:

public static JCO.Client createClient(java.lang.String client,
                                      java.lang.String user,
                                      java.lang.String passwd,
                                      java.lang.String lang,
                                      java.lang.String mshost,
                                      java.lang.String r3name,
                                      java.lang.String group)

Creates an instance of a client connection to a remote SAP system (with load balancing)

Parameters:
client - SAP logon client
user - SAP logon user
passwd - SAP logon password
lang - SAP logon language
mshost - Host name of the message server
r3name - Name of the SAP system
group - Name of the group of application servers
Returns:
the newly created client

for connections to other systems. So you can avoid to create destinations

Regards

Matteo

Edited by: Matteo Fusi on Apr 1, 2009 11:33 AM

[Former Member]

Thanks for your quick reply Matteo,

Your answer was verry helpful for me.

Finally i solved the problem.

The only problem with your solution was, that i need a username and a password.

Since we have Single Sign On to our backends i cannot provide a username and a password for the createClient call.

But i found a solution in this [thread|;.

Now it works

Thanks for your help

Regards

Pascal