Understanding Portal Utility Processes

The Synchronize Collection Security Process

The Synchronize Collection Security (PTPP_SCSYNC) Application Engine process updates security for published custom navigation pages and navigation pagelets by adding permission lists, roles, or both from the content references and folders in the navigation collection to the content references for the published navigation page or pagelet.

The Synchronize Collection Security process runs for navigation collection publications according to the Security Access options that are set for the publication on the Publish Collection page. The process runs for navigation collection publications that are published with the Allow Collection Sync option selected. The process is not run for navigation collection publications that are published with the Do Not Allow Collection Sync option selected. The process also removes extraneous security settings for navigation collections that were published with the Public Access option selected.

Run this process when you initially publish or change a navigation page or pagelet with the Allow Collection Sync option selected or after security updates to the items within the collection.

See Publishing Navigation Collections.

The Delete Empty Folders Process

The Delete Empty Folders Application Engine process (PTPP_FD_DEL) deletes portal registry folder references that do not contain child folders or content. The process does not delete empty navigation collection folder placeholders or the My Favorites folder. The user ID running the process must have been assigned the security role of Portal Administrator.

Run this process when you are deleting content references during an upgrade or implementation, and you are removing out-of-date navigation and replacing it with the current delivered navigation. You should also run this process after copying a deleted portal project.

The Clean Portal Project Process

The Clean Portal Project Application Engine process (PTPP_CPPROJ) removes unnecessary and potentially harmful data from a portal project definition before you copy it to the PeopleSoft Interaction Hub. Run this process as a part of an upgrade or implementation when you want to load navigation from a content provider into the PeopleSoft Interaction Hub.

The Clean Portal Project process removes common objects from the content provider portal project which, because they are common, also exist in the PeopleSoft Interaction Hub. Run this process on the portal project before copying it to the PeopleSoft Interaction Hub so that you don't override these common objects configured for use with the PeopleSoft Interaction Hub with the common objects that were configured in the content provider.

The Clean Portal Project process ensures that you copy only the navigation objects that you think are necessary, such as registry structures, templates, and permissions.

WARNING:

Navigation collections cannot be rendered in the PeopleSoft Interaction Hub if the content provider registry is hosted by a remote node.

Because navigation collections actively access the registry, a published navigation collection page or pagelet cannot be rendered for a registry that is hosted by a remote node. If you want to render a content provider navigation collection page or pagelet in the PeopleSoft Interaction Hub, the content provider's registry must be hosted by a local node in the content provider database.

See Administering Portal Definitions Understanding Portal Administration.