Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Easy question

Hi,

I've been asked to set up a portal version of SAP Logon so we can look at SSO. We have ECC 6.0 portal and systems as well as some 4.6C.

I've got everything working, but have a few remaining issues.

I created seperate pages inside the same workset, one page per instance. The role is set as an entry point.

1. Does that sound like a sound approach?

2 The problem is when the user logs on, it attempts to immediately log them onto the system attached to the first page, in our case the development 4.6C system. Most people are not defined in the development 4.6C system and have no reason to attempt to log on, so this is inappropriate. I want to present the options to the end users, but not attempt to automatically log them on. Any thoughts?

Points will be awarded.

Thanks and best regards,

Russ Brooks

replied

Hi Russ,

Every transaction iview require you to fill in a system. So if you have created the systems for Dev, QA and Production in the Portal, then connect your transaction iview as below.

1) Dev_Role for client 1

Dev_IView for client 1: System target Dev (remember..its system alise that you use here). TC: SBWP (example)

20 Dev_Role for client 2

Dev_IView for client 2: System target Dev (remember..its system alise that you use here) TC: SU3 (example)

3) QA_Role

QA_IView: System target QA (remember..its system alise that you use here) TC: SBWP

4) PRD_Role

PRD_IView: System target Dev (remember..its system alise that you use here)TC: SBWP

So, to show SSO with different systems/enviornment, whenever a user is assigned with the role mentioned above, he/she will see the Transaction appear in the iview (of course, he/she should have the authorisation to run the transaction), be it if the transaction is in Dev or QA or Prod, the Portal will just show it and the user will not know which environment that transaction iview connected to which system.

Basically, you have have as many system as you want in the Portal and link as many iviews to different systems (one to one relationship that is). Hopwever, its a good rpactise to keep your landscape clean. For example on what was setup on my side. And of course, a good overview of the concept is important..agree )

What we have here is that we have 3 tier landascape Portal.

Dev Portal: Link to Sandbox/Dev systems (BI and ERP etc)

QA Portal: Link to QA systems (BI and ERP etc)

Prod Portal: Link to Prod systems (BI and ERP etc)

Hope that helps.

Ray

Edited by: Raymond HENG on Oct 9, 2008 4:54 PM

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question