Show TOC

 Integration of BEx and BW objects into Other PortalsLocate this document in the navigation structure

Use

BEx Web applications and queries that are displayed on the Web can be displayed as iViews in different portals. You can also use information broadcasting with other portals.

An SAP NetWeaver 7.x portal is required to display a BEx Web application or query using the BEx Web runtime (SAP NetWeaver 7.x). This portal can be used either specifically for content from SAP NetWeaver BW and SAP BEx or company-wide (as an enterprise portal). If this portal is to be used only to display BEx and BW objects, you may need to integrate these objects into another (company-wide) portal. This (company-wide) portal may be one of the following:

  • SAP NetWeaver 2004 portal (SAP EP 6.0 based on SAP Web AS 6.40 Java)
  • SAP NetWeaver 7.x Portal
  • Third-party portals
    Note

    A portal that exposes its content for consumption by other portals in the network is called the producer portal. A portal that accesses and uses content provided by other portals in the network is called a consumer portal. At runtime, iViews that are running in a producer portal are remotely displayed in the consumer portal.  The terms producer iView and consumer iView are used in the same way.

The following integration options are supported, whereby an SAP NetWeaver 7.x portal with BEx and BW objects is used as the producer portal:

Overview

Consumer

SAP NetWeaver 2004

(SAP EP 6.0)

SAP NetWeaver 7.x Portal

Third-Party Portals

Producer (*)

iView

iView

Remote delta link (federated portal network)

URL iView

Role

(not supported)

Remote delta link or remote role assignment (federated portal network)

(not supported)

Information Broadcasting

WebDAV (**)

WebDAV (**)

(not supported)

(*) In this table, the producer is the SAP NetWeaver 7.x portal with the Java-based BEx Web runtime.

(**) Note that information broadcasting supports the storage of documents or online links in KM folders only; it does not support storage as personal documents (My Portfolio view) or in collaboration rooms.

Single Sign-On is also supported for this type of integration.

Note

To integrate a BEx Web application (SAP NetWeaver 7.x format) into an SAP Enterprise Portal 6.0, the Web browser must fulfill the prerequisites for SAP NetWeaver 7.x.

For more information, see the Product Availability Matrix (PAM) on SAP Service Marketplace at service.sap.com/netweaver → SAP NetWeaver <Release Name> Release-Specific Information → Product Availability Matrix.

Features

An iView from an SAP NetWeaver 7.x as producer portal is integrated in different ways depending on the SAP NetWeaver release of the consumer portal:

  • In an SAP NetWeaver 2004 consumer portal (SAP EP 6.0), you have to create a new iView that points to the BEx Web application that is located on the producer portal.

    More information: Integrating into an SAP NetWeaver 2004 Portal (SAP EP 6.0)

  • In an SAP NetWeaver 7.x consumer portal, you can use the federated portal network capabilities. You must create a reference (remote delta link) to an existing BEx Web application iView that is located in the producer portal. Alternatively, you can assign users in the consumer to a remote role (located in the producer portal) that contains a BEx Web application iView.

    More information: Integration into an SAP NetWeaver 7.x Portal

  • In a third-party portal, the connection between the consumer portal and producer portal is made using a direct URL to the BEx Web application.

    More information: Integration into Third-Party Portals

You can only incorporate an entire role with multiple iViews from an SAP NetWeaver 7.x producer portal into another SAP NetWeaver 7.x portal by using a federated portal network. You use remote role assignment to do this.

Various options are supported for using information broadcasting to distribute BEx objects to various portals. We recommend the use of WebDAV.

More information: Setting Up Broadcasting in Federated Portal Networks