Skip to Content
Author's profile photo Former Member

Portal Content Directory Persistence Layer Browser

h3. Limitations of the PCD inspector    Some of you have probably used the PCD inspector  ( in order to browse through the Portal Content Directory and its objects (such as iViews, pages, roles, worksets, and systems). But the public release of this inspector is read-only and you cannot change the content of the pcd from this tool.   h3. There is another tool!   Initialize and provide the password for your PCD user on the database. After you’ve done this you will get up the content of the PCD divided into three areas.   h3. Usage of plbrowser   As just mentioned, the content of the plbrowser is divided into three areas:  * Namespace data  * Namespace user  * Namespace schema    The namespace data area is the most usefull. Here you can find all applications deployed and all the portal content (iviews, pages++) plus more. Try right clicking on an object or folder and select attributes. You can now see what attributes this object has, and which values each attribute has.   The namespace user area seems to contained user specific data which has been defined through personalization. In order to find out for which user the data is defined for, right click cryptic folder name (such as LY9gIye1X6nMOaoFaAfbGFOLmts~) and select attributes. The attribute with name defines the user which the values are stored for. I would believe you could reset personalized values using this functionality, but I haven’t tested it.   The namespace schema area I actually do not know what represents.   In my experience as a portal consultant I’ve only used the tool twice and both times it was to delete some unwanted data. One time we had a theme that wouldn’t disappear and the only way to thoroughly get rid of it was to delete it completely from the PCD. The second time it was used, we had a portal core service that was in the PCD due to a rampup installation that we had to delete. You see that in newer portal versions, core services are not put in the PCD and this caused some problems. For example if we ran appclear on a node, the synchronization procedure caused the old version of the core service to be synchronized instead of the new one.    There is also functionality to check the consistency of the database, for example in order to find parent-less objects, attributes which do not belong to any object and so on. I am not sure if it is safe to delete them though.   h4. Small caution when deleting objects   image

Assigned tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Pankaj Kumar
      Pankaj Kumar
      I almost fainted after seeing twelve .. in the classpath.
      Author's profile photo Former Member
      Former Member

      Nice discovery.   There was a nasty piece of content that just could not be removed because it crashed the Portal when you tried to expand the PCD structure.   This tool removed it which has had a +ve impact on performance.