An outgoing federated search allows users in your portal to search other Oracle WebCenter Interaction portals or other external repositories.
To enable a federated search between Oracle WebCenter Interaction portals, a relationship must be established between the requesting (outgoing) and serving (incoming) federated portals. For every request issued, the requesting portal sends a portal identification name and password to identify itself to the serving portal. Administrators of both portals involved in a relationship must agree upon a single portal identification name and password. This information is entered in both the outgoing and incoming federated search objects.
To enable a federated search between an Oracle WebCenter Interaction portal and an external repository, a search Web service must be created.
To learn more about federated searches, click here.
To configure an outgoing federated search, perform the following steps:
If you are searching another Oracle WebCenter Interaction portal, next to Send portal authentication, select Yes. If you are not searching another Oracle WebCenter Interaction portal, leave No selected and skip to step 6.
In the Portal identification name box, type the agreed upon name.
In the Portal identification password box, type the agreed upon password.
In the Password confirmation box, type the password again.
User Name Aliasing allows requesting portal users to impersonate serving portal users. To add a group of users from this portal that you want to impersonate a particular user from the serving portal:
Click Add Group.
In the Select Group dialog box, select the groups you want to add and click OK.
To the far right of the group, click .
In the Use this user name alias text box, type the name of the serving portal user whom you want this group of requesting users to impersonate.
When you are done, click to
save the mapping.
Note: When a requesting user tries to search a serving portal, the requesting portal examines the list of mapped groups from the top down; the first group in the list to which the requesting user belongs is used to determine what serving portal user the requesting user will impersonate. Therefore, groups with high levels of security should be mapped at the top of the list, so that requesting users are granted the highest level of security available to them.
To delete a group, select it and click .
To save your settings, click Finish; to cancel this action, click Cancel.
To display the page associated with this help topic: