Start of Content Area

Function documentation Integration into an SAP NetWeaver 7.x Portal  Locate the document in its SAP Library structure

Use

The general recommendation from SAP is to use just one portal. In light of the special requirements that arise when using a portal with BEx objects (like load requirements and various versions between consumer and producer portal), an exception is made here.

The content from multiple portals can be integrated in a single central portal. The main difference between the integration options is whether administration of iViews and other portal content is carried out in just one portal or distributed to multiple portals. Distributed administration makes it possible to separate tasks of BEx authors and portal administrators more clearly.

When integrating an SAP NetWeaver 7.x portal with BEx objects (the producer portal) with another SAP NetWeaver 7.x portal (the consumer portal), you have the following options:

      Application Integrator

The general recommendation is to use one portal for administration of portal content. To make BEx objects from the producer portal available to users in a consumer portal, we recommend using the Application Integrator Service. This allows connection to various applications from various systems. Administration is performed centrally in one portal, in this case in the consumer portal.

When using Application Integrator, BEx authors just create the BEx objects. The portal administrators create the iViews for the BEx objects with the corresponding properties and navigation structure for the users.

      Federated Portal Network

The federated portal network supports distributed administration of portal content to multiple portals and provides users with central access to the content.

In this case, the BEx authors create the BEx objects, the corresponding iViews and the underlying navigation structure. The portal administrators create the general navigation structure and integrate the BEx objects and the associated structure.

If you use portals in the federated portal network to make BEx objects from a producer portal available in a consumer portal, you have the following options:

       Remote delta link for sharing individual iViews

You can use remote delta links to share content from different SAP NetWeaver portals in a single portal role. The portal role is created in the consumer portal.

       Remote role assignment for sharing portal roles that contain iViews

Remote role assignment allows you to integrate a complete portal role from the producer portal into the consumer portal.

       WebDAV for information broadcasting of precalculated BEx applications and online links in Knowledge Management.

WebDAV cannot be used to display iViews from the producer portal in the consumer portal.

Sharing content between two or more SAP NetWeaver portals is facilitated by the federated portal network capabilities of SAP NetWeaver 7.x. Remote delta links and remote role assignment are two different ways of sharing content. Each of the two options has specific advantages.

By setting up a federated portal network, you can integrate BEx objects I that run on your BEx portal (the producer portal) into your corporate portal (the consumer portal).

More information:

Implementing a Federated Portal Network

'Remote Delta Link' Mode

'Remote Role Assignment' Mode

Prerequisites

If you want to use the Application Integrator Service or federated portals for integration purposes, note the following prerequisites:

      User administration needs to be set up in such a way that the user IDs in the consumer portal are identical to the user IDs in the producer portal.

More information: User Persistence

      Complete the required configuration steps in the federated portal network. The configuration activities are also required for the Application Integrator Service to enable single sign-on (sso) between the portals.

More information: Implementing a Federated Portal Network

      Make sure that the settings required for including iViews and roles have been made.

More information:

Preparing Your Producer

Preparing Your Consumer

      Check whether you need to set access to URLs from BEx. This is the case if users only intend to call the URLs from BEx from the consumer portal, without having to log on to the producer portal.

More information: Setting Up Access to URLs from BEx in the Federated Portal Network

Application Integrator Service

If you use the Application Integrator Service, enter the ID of the producer portal as the system alias when creating the iView. The system creates this producer ID when implementing a federated portal network.

Background documentation

Alternatively, you can create a system object manually. Note the following:

       The WAS host name must be the host name of the producer portal.

       You have to perform the SSO configuration manually. See Configuring Single Sign-On (SSO) Between SAP EP 6.0 and the SAP NetWeaver 7.0 Portalsapurl_link_0001_0009_0014.

Federated Portal Network

If you use the federated portal network, the conditions must be met for using Information Broadcasting with the federated portal network.

More information: Setting Up Broadcasting Using WebDAV Repository Managers

Features

Application Integrator

You create iViews and enter the producer ID (or your own system object) as the system alias. The iViews exist in the federated portal network. When an iView is called up, the system recognizes that it should actually be run from the producer portal.

This is comparable with the existing integration of BEx objects from SAP NetWeaver 2004 into a portal.

More information: Application Integrator

Federated Portal Network

Including iViews and Roles

More information:

Workflow: Remote Delta Link

Workflow: Remote Role Assignment

Distributing Content from BI with Information Broadcasting by Using WebDAV

More information: Setting Up Broadcasting in Federated Portal Networks

 

 

End of Content Area