Building a Composite Portal with Federated Searches

Multiple portals accessing the same user repository can share content. All portals involved in the relationship must import the same users and groups from a single user repository.

There are two scenarios for building a composite portal:

Multiple content portals each possess links to a large number of documents. A single user can visit the separate content portals, always with the same user name and password, and always receive access to the correct content.

In this scenario, each portal acts as both a serving and a requesting portal.
One portal is set up as a master portal rather than a content portal. Through this master portal, users can access content from the various content portals.

In this scenario, the master portal acts as the requesting portal, and the content portals act as the serving portals.

On each serving portal, the administrator creates an incoming federated search that includes the authentication sources that the serving portals share with the requesting portals. All users making requests to a serving portal need to be imported into the portal through one of these common authentication sources.
On each requesting portal, the administrator creates an outgoing federated search for each content portal, selecting No for Send portal authentication. Users will make the requests using their own user accounts.

Parent topic: About Providing Search Access to External Repositories with Federated Searches

Oracle WebCenter Interaction Administrator Guide

Building a Composite Portal with Federated Searches