Content of a virtual portal

The content of a newly created virtual portal can vary, depending on the method by which we create the virtual portal. We can change the pre-configured content for virtual portals. When creating the virtual portal using the Virtual Portal Manager portlet, the portlet starts an XML configuration interface script that creates the initial content of the new virtual portal. The content of a virtual portal is similar to that of a full portal installation, but some administration portlets that manage global portal settings are not included in the default content of virtual portals. For example, the administration portlet Virtual Portal Manager is installed as part of the initial portal installation only. It is not part of the default content of virtual portals created. Use it only in the initial portal installation.

Default roles and access permissions to the subadministrators of the virtual portal:

• Administrator to the content root (Administrator@content root) of the virtual portal
• Editor to portlet instances (Editor@portlet entities) created for the new virtual portal.

We can modify the roles and access permissions for the subadministrators of a virtual portal manually according to the business needs:

• To change the roles and access permissions for subadministrators on the portlets globally and before creating a virtual portal, configure the Virtual Portal Manager portlet accordingly. See Pre-configuring the subadministrators for virtual portals.

• To change the roles and access permissions specifically and after creating a virtual portal, use the Portal Access Control portlets. If we do this change in the initial portal installation, we can change the access permissions on the virtual portal as a whole. If we do this change in the virtual portal itself, we can change the access permissions on the individual resources of the virtual portal.

To change the content of virtual portals, it can be done by one of the following ways:

• To change the content globally and before creating a virtual portal, advanced master administrators can reconfigure the XML script that specifies the initial content for virtual portals. See Pre-configuring the default content for virtual portals.

  When we modify or replace this XML script, plan ahead and apply special care. We can add or remove some content to enhance or reduce the functionality of a virtual portal to a certain extent. The following portal resources are mandatory content of a virtual portal and must be included in a customized XML initialization script for virtual portals:

  • Content Root (wps.content.root)
  • Login (wps.Login)
  • Administration (ibm.portal.Administration)

  Depending on the functionality that to make available, more content is required. For example, to allow templating. Include Application Root (wps.application.root) and Templates (ibm.portal.Templates).

• To change the content specifically and after creating a virtual portal, use either of the following portal tools:
  • Use the Manage Pages portlet of the virtual portal. The subadministrator of the virtual portal can do this change.
  • Use xmlaccess.sh to import content into the virtual portal. This procedure can be done only from the initial portal installation.

If we use the configuration task create-virtual-portal to create a virtual portal, the new virtual portal created is empty. Create the content for the virtual portal. For example, we can do this using xmlaccess.sh. See xmlaccess.sh.

Parent Plan for virtual portals

Related concepts:
xmlaccess.sh
Pre-configure the subadministrators for virtual portals
Pre-configure the default content for virtual portals
Technotes for virtual portals