Definition of Terms

Unified navigation requires that two types of nodes be defined on both the local portal system and the remote content provider systems:

Term	Definition
Cluster	In the context of unified navigation, multiple content provider systems are federated by the portal system into a single cluster.
Content provider system	A content provider system is a PeopleSoft application, such as PeopleSoft HCM, PeopleSoft FSCM, and so on, that provides content to other systems. In the context of unified navigation, the portal system federates the content provider systems into a single cluster.
Default local node	The default local node is the predefined local node that designates the system on which the database is installed. Default local nodes generate security artifacts, such as PS_TOKEN, and participate in Integration Broker integrations. For example, in the PeopleSoft FSCM database, its default local node is PSFT_EP. In the PeopleSoft HCM database, its default local node is PSFT_HR. In the context of unified navigation, each participating default local node must have an active definition in all participating systems, must be identified to the integration gateway, must be established as in-network for the integration node network (on the portal system only), and must be established as a trusted node for single signon.
Local node	A local node is any node that is local to the system on which the application content references are registered. Local nodes are designated as either the default local node or as a portal host node. For example, PSFT_HR and HRMS are defined as local nodes on a PeopleSoft HCM system. Conversely, PSFT_HR and HRMS are defined as remote nodes on a PeopleSoft FSCM system.
Portal host node	A portal host node is the node that hosts a specific portal registry and the portal's content. For example, ERP, HRMS, and CRM all host the EMPLOYEE portal on PeopleSoft FSCM, PeopleSoft HRMS, and PeopleSoft CRM systems, respectively. In the context of unified navigation, each participating portal host node must have an active definition in all participating systems and is used as the content provider node for remote folders and pagelets.
Portal registry	The portal registry is the collection of all registered content references for a specific portal. A portal registry contains folder definitions and content reference definitions in a tree-like structure. A portal registry is defined on a portal host node.
Portal system	In the context of unified navigation, any PeopleSoft application can be designated as the portal system that federates all participating content providers into a single cluster. Note: In a unified navigation cluster, only one PeopleSoft application can serve as the portal system. All other systems in the cluster are referred to as content provider systems. In other contexts—for example, a standalone PeopleSoft application system—the PeopleSoft application itself serves as its own portal system.
Remote node	A remote node is any node that is remote to the system on which the configuration process or content access is being performed. For example, PSFT_HR and HRMS are defined as local nodes on a PeopleSoft HCM system. Conversely, PSFT_HR and HRMS are defined as remote nodes on a PeopleSoft FSCM system.