Start of Content Area

Function documentation Integration in Third-Party Portals  Locate the document in its SAP Library structure

Use

BEx Web applications, enterprise reports, and queries that are displayed on the Web can be displayed using third-party portals.

Prerequisites

Various settings are required when setting up single sign-on for integration using a URL. When integrating using a URL, a trustworthy connection has to be established between two portals.

You have completed the following steps to use single sign-on:

...

       1.      Export the portal certificate in the producer portal.

       2.      Import the (producer) portal certificate in the consumer portal.

For more information about these steps, see SAP Customizing Implementation Guide SAP NetWeaver Business Intelligence Settings for Reporting and Analysis BEx Web Integration into the Portal in the SAP Reference IMG (transaction SPRO).

A third-party provider portal does not normally support SAP logon tickets. However, most non-SAP portals allow the use of X.509 client certificates.

More information: User Authentication and Single Sign-On

Features

You have various options for displaying a BEx Web application or query in a third-party portal. Using a URL: With a URL, you can call an SAP NetWeaver 7.0 iView (as the producer iView) in a third-party portal.

To call an iView using a URL, you have the following options

Call Type

URL

Call iView directly

<PORTAL_PROTOCOL>://<PORTAL_SERVER>:<PORTAL_PORT> /irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2f <FOLDER>!2f <IVIEW_NAME>

Call using BEx iView

(only for SAP NetWeaver 7.0 iViews)

<PORTAL_PROTOCOL>://<PORTAL_SERVER>:<PORTAL_PORT> /irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.pct!2f platform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.bex? TEMPLATE=<TEMPLATE>

Note

Placeholders are not supported. Replace the above placeholders <PORTAL_PROTOCOL>, <PORTAL_SERVER>, and <PORTAL_PORT>, with the Web protocol, portal server, and corresponding port for the producer iView. Replace the <FOLDER> placeholder with the appropriate directory in the Portal Content Directory (PCD). The <IVIEW_NAME> placeholder is for the iView ID.

Do not include any spaces in the URL.

The only difference between BEx Web applications and queries is their URL parameters. If you call the iView directly and call the iView using the application integrator, these URL parameters are defined for the producer iView, so no differentiation is required in the URL. All the required information is defined in the producer iView.

When the iView is called using the BEx iView, you need to enter the URL parameters after the question mark.

More information: BEx Web Application or Query as iView in the Portal.

A source portal provided by a third-party can use all three options for integrating a producer iView as long as it supports the display of external content using a URL.

Activities

The activities required can vary depending on the third-party portal used. To include a URL, see the required activities outlined in the documentation for the third-party portal.

 

End of Content Area