E.1 Understanding the Navigation Collections Creation Process

Loading the PeopleSoft Interaction Hub with the content provider registry structures, using the full navigation load, does not include Navigation Collection definitions. This appendix gives a step-by-step guide to import the content provider navigation collections into the PeopleSoft Interaction Hub, copy them to the created site, and update the navigation collection objects to enable rendering them from the PeopleSoft Interaction Hub in the created site. The net result is that the Navigation Collection definition and the navigation page from your content provider are maintained in the PeopleSoft Portal Solutions database, as well as updated in and rendered out of the PeopleSoft Interaction Hub. The content reference links in the navigation collections are still rendered out of the content provider database.

Note:

This appendix assumes that a full navigation load for the portal registry structures has been made from the content provider database into the PeopleSoft Interaction Hub. This appendix also assumes the full navigation folders have been copied to the created site in the PeopleSoft Interaction Hub.

The following is an overview of the tasks that are necessary. More explicit directions for each step are given later in the appendix:

  1. Determine the name of the Navigation Collection definitions that you want to copy.

  2. Create a PeopleSoft Application Designer project in the content provider database that contains the delivered Navigation Collection definition objects and images.

  3. Export the project from the content provider database using Copy Project to File.

  4. Import the project into the PeopleSoft Portal Solutions database using Copy Project from File.

  5. Copy the delivered Navigation Collection definitions using Structure and Content from the delivered site (for example, EMPLOYEE, CUSTOMER, SUPPLIER) into the created site in the PeopleSoft Portal Solutions database.

  6. Export Pagelet Wizard definitions for Navigation Collection pagelets from the content provider and import them into the PeopleSoft Interaction Hub using Data Mover.

  7. Update the content provider delivered Navigation Collection links (in the PeopleSoft Interaction Hub) to reference the PeopleSoft Interaction Hub created site name.

  8. Update the content provider delivered Navigation Pages (in the PeopleSoft Interaction Hub) to render from the PeopleSoft Portal Solutions, not the content provider.

  9. Update the content provider delivered Navigation Pagelets (in the PeopleSoft Interaction Hub) to render from the PeopleSoft Portal Solutions, not the content provider.

If you have a development content provider database that has the same navigation collections as your production database, you can perform tasks 1 and 2 from the development database.

If you have a development PeopleSoft Portal Solutions database that has the same portal names and registry structures as your production database, you can perform tasks 3 through 6 on the development database.

To move the updated navigation collection definitions and navigation pages into your production database, you can create a project that contains these objects in your PeopleSoft Portal Solutions development database, and then copy that project into your PeopleSoft Portal Solutions production database.

Note:

After you copy a project that contains portal registry structures into a database, you must delete the application server cache, and then stop and restart both your web server and the application server.