Skip to end of metadata
Go to start of metadata

Portal Implementation

Find here all answers to Portal Implementation, including SSO issues.

Some common questions and answers...

  • Page:
    Creating transports in EP 7.0x — Transports are used to move PCD objects from one portal instance/landsacpe to another. Here are some details.
  • Page:
    Creating Transport Role in Portal — This WIKI FAQ intends to help the Portal Administrators who wants to give Transport option to developers who develop Portal Content without assigning them super admin priveleges

Single Sign On and Cookies - There are quite a few postings in this forum regarding problems with single sign on (SSO).

  • No content found for label(s) ep_ssochecklist.

Some portal implementation generalizations- similar to FAQs, but more like FGAs (frequently given answers)

SAPGUI and the SAP Portal - how do I start a transaction?

When starting an SAP transaction, you need to decide which variant of SAPGUI to use.

All the SAPGUI variants are just started by the portal, they don't need to be installed in the portal. A portal user logs on to the portal and is presented with one or more options, some of which could start one of the SAPGUI variants. When the user selects the option, a URL is launched from the user's browser that starts SAPGUI. The portal does not run SAPGUI.

SAPGUI for Windows needs to be installed on the desktop of the user who wants to launch it.

SAPGUI for HTML requires extra SAP software called ITS (Internet Transaction Server). This is either installed standalone, which requires a separate web server, or it is also integrated as a service within an ABAP system 6.40 or higher.

SAPGUI for Java is rarely used!

It is not possible to tell at run time whether a user has SAPGUI for Windows installed on their desktop. This means that you may need to provide two options in the user's portal menu - one to start SAPGUI for Windows, the other to start SAPGUI for HTML.

How many SAP transactions should I have in the SAP Portal?

You can manually make iViews to start individual SAP transactions, or you can use the Role Upload option from the System Administration -> Transport menu to build portal roles based on SAP roles.

While this may look like an attractive option, it can lead to a lot of extra work as the roles need to be synchronized. For example, if an option is removed or added to an SAP role, then the portal role would need to be updated to reflect this change.

Instead of building a duplicate portal menu structure that reflects the user's SAP menu structure, a useful transaction to start is SMEN. This transaction launches the user's Easy Access menu, so all their SAP options are visible.