Administering the portal content and resources for virtual portals

When creating a virtual portal using the Virtual Portal Manager portlet, the portlet also creates default portal content and resources for the virtual portal. This default content is determined by the default XML script file for initializing virtual portals. In general, we can administer portal resources for a virtual portal just like you do for a normal portal installation.

We must be aware that some resource types are scoped to a particular virtual portal and cannot be accessed from outside of that virtual portal. Such scoped portal resource types are assigned to only that one portal. Sharing of these resource types between virtual portals is not possible. This restriction is imposed by the portal system and provides a secure isolation between virtual portals. We cannot change this behavior.

Other resource types are not scoped. They are shared among all virtual portals of the same installation. To restrict such resource types to particular virtual portals, we can define their visibility by using Portal Access Control. These access restrictions should usually be defined by the master administrator of the portal installation. For more information about scoping of portal resources for virtual portals, see Planning for virtual portals and Separating and sharing resources between virtual portals.

• To change the content globally and before creating a virtual portal, modify the default XML script that specifies the initial content for virtual portals. For details about how to do this see Preconfiguring the default content for virtual portals.

• To change the content specifically and after creating a virtual portal, use either of the following portal tools:

  1. Use the Manage Pages portlet of the virtual portal. We can have the subadministrator of the virtual portal do this.

  2. Use the XML configuration interface to import content into the virtual portal. We can use this portal tool only from the initial portal installation.

  Note: When creating a virtual portal, the portlets that are associated with HCL Web Content Manager are not included in the virtual portal, even if we deployed these portlets as part of your original portal installation. To use any of these portlets in a virtual portal, we must manually create a page and add the portlets:

  • Authoring portlet: Select Web Content Authoring when we are adding the portlet.

  • Web Content Viewer portlet: Select Web Content Viewer when we are adding the portlet.

Parent topic: Administering virtual portals

• XML configuration interface

• Plan for virtual portals
• Separating and sharing resources between virtual portals
• Preconfiguring the default content for virtual portals
• The XML configuration interface

References: