Change the Login Id on JCO dynamically ???

[Former Member]

Hello All,

We have developed a Web Dynpro application, where in we have made BAPI calls and the changes are being done in the backend R/3 tables.

Now, these changes get reflected in the backend by the user-id with which the JCo destination is being created.

Is it possible that, we can take the user logged in and connect to the back end using his corresponding backend id.

I read on the forums about Logon Ticket, but I guess Logon Ticket requires that the portal userid should be same as the backend id.

This is not the case with us.

In our case we have the portal id as - "ABC", and the backend which the JCo should use is "12345".

Should I handle this scenario with usermapping ???

Is there any other method ?????

Thanks and Regards,

Samta

[Former Member · Accepted solution]

Hello samta,

You successfully answered your own question .

Yes, this scenario should be handled with user-mapping.

You should perform 5 operations:

1. Configuration in the backend system. see:

2. Define a system in <i>System Administration > System Configuration > System Landscape</i>.

3. Define this system as the SAP Reference system in <i>System Administration > System Configuration > UM Configuration</i>.

4. Maintain user maping to this system.

5. Choose Logon Ticket as the logon method for the model data JCO Destination.

If you need more details regarding any of the steps, feel free to ask.

Hope that helps,

Yoav.

[Former Member · Accepted solution]

Hey Yoav,

Thanks a lot for your prompt reply.

That was indeed very detailed explanation.

Just correct me if I am wrong -

I need to create a SAP Dedicated R3 System, and set the "Logon Method" as User Mapping and here i specify the backend mapped id and password for this user.

Now I create a Jco destination with the Logon method as "Logon Ticket"

That means, i dont need to import the Logon ticket generated by the R/3 system here in my portal, rite ?

Thanks in advance,

Samta

Message was edited by:

samta nichani

[Former Member · Accepted solution]

Hi simta,

One thing at a time:

1. It doesn't matter what Logon Method you set in the SAP Sytem you define, since you won't use it to connect to the backend system, just for user mapping. Anyway, "User Mapping" is not a logon method.

2. You are right regarding the JCO destination.

3. > That means, i dont need to import the Logon ticket generated by the R/3 system here in my portal, rite ?

Wow. something very wrong here.

The R/3 system doesn't generate the logon ticket -

The Portal does!

And you should make configurations in the R/3 system to accept tickets from your Portal, as described in the referenced weblog.

Yoav.

[Former Member · Accepted solution]

Hey Yoav,

Thanks a million!!!

Yes, now I am clear with quite of the stuff.

(1) In the system created, it doesnt matter whether I enter the Logon type as "UIDPW" or "LOGON TICKET". But I need to enter the "User Mapping Type" as "admin,user", so that I can specify the mapped id and password for the user.

(2) JCO needs the "Logon Method" as "LOGON_TICKET"

(3) Oops sorry, I just messed up with things.

Ye rite I need to download the verify.der file from portal and import it on the backend R/3 system

Thanks a lot for your timely response,

Samta

[Former Member · Accepted solution]

Hi samta,

Everything is right now.

Just note you don't forget number 3:

3. Define this system as the <b>SAP Reference system</b> in System Administration > System Configuration > UM Configuration.

Only the mapping for a system which is defined as the SAP Reference system is used in the logon-ticket.

When a user logins to EP, a check is made if he has a mapping for the SAP Reference System (If there is such a system).

If so - the ticket is generated on the mapped name.

Otherwise - the ticket is generated on the user's logon name.

This ticket will now be the user's ticket for ALL systems that are authenticating the user in the Logon-Ticket method.

Yoav.

[Former Member · Accepted solution]

Hello,

I am still unable to resolve this issue.

I have created a system under System Admin as u said.

But these systems dont appear in the dropdown for creating JCO destinations rite ?

The systems tht we get there are the systems we configure in SLD ?

So how do i specify usermapping and where ?

Please help.

Thanks in advance,

Samta

[Former Member · Accepted solution]

Hello Samta,

You should configure user mapping in EP through:

User Administration > User Mapping (for any user or group)

or through the portal personalization link (for the loggen-on user).

(In the JCO destination you should keep the System you defined in SLD, no change is needed here apart for defining "ticket" as the authentication mode)

Hope it's clearer now,

Yoav.

[Former Member · Accepted solution]

Hello Yoav,

I understood what u mean to say.But am still unable to resolve this puzzle.

Really sorry for all the trouble.

(1) I have created a system in the System Admin -> System Config pointing to the backend say System Alias "TEST_UD1"

For this system i have specified the user mapping and have personalized his portal id with a backend id.

(2) While configuring SLD, the backend system that appears in the SLD is "SAP_UD1"

(3) While creating JCO, i create a JCO for "SAP_UD1" and specify the logon as - LOGON TICKET.

But how shall the JCO come to know that it has to refer to the system with alias name "TEST_UD1" and fetch the mapped data across this.

As i can have multiple systems created under System Admin -> System Config which point to the application host UD1.

I am really confused abt this

Please help

Thanks,

Samta

Message was edited by:

samta nichani

[Former Member · Accepted solution]

Hey Sam,

Got to system admin - > um config-> security settings tab -> under sap reference system specify the new system.

and go thru these likns to get a better idea of your requirement.

http://help.sap.com/saphelp_nw04/helpdata/en/0b/d82c4142aef623e10000000a155106/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/98/9b2f41893a6e24e10000000a155106/frameset.htm

regards,

your friend ))

[Former Member]

Solved issue

[Former Member]

Unable to resolve this issue