Understanding the Portal Registry Load Process

The Portal Registry Load process provides a file-based method to bulk-load content and folder references into the portal registry.

The registry load process is one methodology for providing access to content from a content provider system in a PeopleSoft Interaction Hub system. However, the content references available through this methodology are only as current as the last registry load. Content references are not dynamically updated as they are created or deleted. An alternative methodology, unified navigation, federates PeopleSoft applications under a single portal system and dynamically provides access to content references on those content provider systems.

See Understanding Unified Navigation.

Loading data into the portal registry involves two staging tables:

• EO_PE_LOAD_DTL

• EO_PE_LOAD_FLDR

The PORTAL_REG_LOAD Enterprise Integration Point (EIP) delivers both an application message and a file layout in the form of a comma-separated value (CSV) file. You can:

• Use your own application programming interfaces (APIs) to match the PORTAL_REG_LOAD message format.

• Export the data to a spreadsheet, save it as a CSV file, and follow the steps we provide for the inbound flat-file utility.

  See Preparing to Run the Portal Registry Load Process.

For the inbound flat-file definition, use the layout and message combination: PORTAL_REG_LOAD.

The result of the flat-file utility is a published PORTAL_REG_LOAD message. When the portal subscribes to the message, you see the data in the tables EO_PE_LOAD_DTL and EO_PE_LOAD_FLDR.

After the file data is in the staging tables, run the Registry Load process to load the data into the portal registry.