Setting Up Broadcasting Using KM Navigation iViews or CM Repository Managers

Use

In addition to the options for setting up information broadcasting in federated portal networks using WebDAV repository managers, the following options are also available:

Information broadcasting using KM navigation iViews
Information broadcasting using CM Repository Manager
Information broadcasting using the Information and Content Exchange protocol (ICE)

Overview

Solution	KM Navigation iViews	CM Repository Manager	Information and Content Exchange Protocol (ICE)
Storage	The documents are stored in the Producer Portal	The documents are stored in the file system (not in a database) as type fsdb. This means that the documents are stored in the file system and the properties are in the database.	The documents are stored in the Producer Portal
Procedure	The documents are displayed using the KM navigation iView (created in the producer portal). The KM navigation iView is called remotely from the consumer portal.	The KM of the producer portal and the KM of the consumer portal access the same storage (file system). This would result in a competing creation and modification of the documents. The users must therefore have read only access to the documents in the consumer portal. A time delay is possible because of the synchronizer. In the default setting, the By Request setting is active, so the time delay is not usually critical.	The documents are regularly copied from the KM of the producer portal to the KM of the consumer portal. A delta copy is possible using incremental updates so that only modified documents are copied. In the consumer portal, the documents should not be modified because the changes are overwritten during the next copy phase. The users therefore have read-only access in the consumer portal.
Common Storage	Different producer portals have different storages for their respective documents. It is not technically possible to combine these storages in a common storage.	It is possible to store documents from different producer portals and from the consumer portal in a common storage.	The common storage of documents from different producer portals is possible.
KM Properties	All KM properties are available.	Not all KM properties from the producer portal are visible in the KM of the consumer portal.	All KM properties are available.
KM Services	All KM services are available. Some services, such as subscription, use the Central Worklist iView for notification for each producer portal. This iView must also be integrated using remote role assignment or a remote delta link.	KM services (such as subscription) are possible in the consumer portal.	The documents are copied. KM services can be used, but two independent versions of one document exist.

More information:KM Properties

Prerequisites

The SAP NetWeaver versions in the consumer portal and the producer portal form a valid combination.
For more information, see SAP NetWeaver Library: Function-Oriented View → Enterprise Portal → Portal → Implementing Advanced Portal Scenarios → Implementing a Federated Portal Network → Planning and Concepts → Version Interopability.
You have created a connection between the producer portal and the consumer portal.
For more information, see SAP NetWeaver Library: Function-Oriented View → Enterprise Portal → Portal → Implementing Advanced Portal Scenarios → Implementing a Federated Portal Network → Managing FPN Connections → Creating FPN Connections.
Ensure that Single Sign-On is set up between the portals.
To set up information broadcasting using KM navigation iViews, you must configure a federated portal network.
For more information, see SAP NetWeaver Library: Function-Oriented View → Enterprise Portal → Portal → Implementing Advanced Portal Scenarios → Implementing a Federated Portal Network → Preparing Your Portals.
To set up information broadcasting using CM repository managers, you must create CM repository managers.
More information:CM Repository Manager
To set up information broadcasting using the Information and Content Exchange protocol (ICE), you must meet the necessary prerequisites.
More information:Content Exchange Concepts

Procedure

Setting Up Information Broadcasting Using KM Navigation iViews

If it is not necessary to store the documents from the different producer portals in a common storage, we recommend that you set up information broadcasting using KM navigation iViews.

Create a KM navigation iView in the producer portal.
More information:KM Navigation iView
Integrate the KM navigation iView into the consumer portal using remote role assignment or a remote delta link.
For more information, see SAP NetWeaver Library: Function-Oriented View → Enterprise Portal → Portal → Implementing Advanced Portal Scenarios → Implementing a Federated Portal Network → Consuming Content from Remote Producer Portals.
Note
You can also integrate a KM navigation iView using a URL iView. We only recommend this course of action in connection with an SAP NetWeaver 2004 portal (SAP EP 6.0).
1. Create a URL iView in SAP EP 6.0.
  More information:Using the URL iView Wizard
2. Enter the URL of the KM navigation iView from the SAP NetWeaver 7.1 portal as the URL.
Alternatively, you can use a generic application integrator iView. The advantage of this is that you do not have to define an absolute URL. You define the protocol, the host name, and the port in a system object in the portal system landscape.

More information:Working with the Application Integrator

Setting Up Information Broadcasting Using CM Repository Managers

If it is necessary to store the documents from different producer portals and from the consumer portal in a common storage, we recommend that you set up information broadcasting using CM repository managers.

More information:CM Repository Manager

Setting Up Information Broadcasting Using the Information and Content Exchange Protocol (ICE)

More information:Content Exchange Concepts

Caution

This solution is quite time consuming and is therefore not recommended.

Result

Users can use information broadcasting to broadcast BEx objects to various federated portal networks.