Portal Registry

The portal registry is collective term used to describe the online navigational structure of the PeopleSoft Internet Architecture (PIA) portal. The portal is made up of folders and content references (CREFs).

This article provides some help around the portal registry.

Portal registry entries don't appear after migration

First, double check that the portal registry entries have been migrated successfully.

PeopleTools > Portal > Structure and Content

Navigate to whereever your portal entries should be and make sure they are there.

Also check the database using the following query to ensure your content references/folders exist:

select * 
where PORTAL_OBJNAME like 'Your Portal Object Name';

If they are not there, go back to your project and check that:

  • The necessary portal registry definitions are in your project
  • The upgrade flag is set and the action is set to copy

They might not appear since there is always a lot of caching when you migrate registry objects. Once quick way to test this is to add a dummy registry entry anywhere in the navigation (eg a content reference pointing to an external site and make sure you save it) and the database save forces a cache refresh and this will then show up the cached entry.

Make sure you then delete your dummy entry you created. This is good for development when you are migrating between databases and do not want to bring down the web server to delete the cache.

Registry Search Index

This is the verity search engine's index which is used to find portal registry entries in PeopleSoft. The application engine used to build the registry search index is PORTAL_INDEX

You can run this from:

PeopleTools > Portal > Build Registry Search Index

Portal Security Sync

To run portal security sync, you need access to every single folder and content reference in the portal.

NOTE: portal security is based on menu security for content references (CREFs) but folder security is set at the portal level.

The two specially delivered roles that will give you this is:

  • PeopleSoft Administrator
  • Portal Administrator

Be warned however that PeopleSoft Administrator is all powerful!. So it is safer to give someone portal administrator if their job involves running portal security sync.

I've found that if you don't have a role that gives you access to the entire portal structure, the portal security sync application engine program (PORTAL_CSS) will run to no success (abend) with a message like this in the standard output (.stdout) file:

First operand of . is NULL, so cannot access member ItemByName. (180,236) 
Name:CheckParentFolder PCPC:2339 Statement:40
Called from:PORTAL_CSS.CREFPERM.GBL.default.1900-01-01.Step01.OnExecute Statement:202
No Comments
Back to top