+

Search Tips   |   Advanced Search

Virtual Portal Configuration Service

The Virtual Portal configuration service (WP VirtualPortalConfigService) enables us to specify properties for the default virtual portal and for specific virtual portals.


Property syntax

There are several ways we can define properties for virtual portals:

    URL context for the virtual portal
    Property format: context.virtual_portal_context.property.property_name.property_value

    Example: context.vp1.property.property1.true

    Host name of the virtual portal
    Property format: hostname.virtual_portal_hostname.property.property_name.property_value

    Example: hostname.vp1.example.com.property.property1.true

    The default keyword
    The default keyword is used to identify the default virtual portal. The default virtual portal has no dedicated URL context or host name.

    Property format: default.property_name.property_value

    Example: default.property1.true

    The global keyword
    The global keyword is used as a fallback property if there no more specific property defined for a virtual portal.

    Property format: global.property_name.property_value

    Example: global.property1.true

Replace the following variables when defining specific properties:

    property_name
    The name of the property we are defining.

    property_value
    The value of the property we are defining.

    virtual_portal_context
    The URL context of the target virtual portal.

    virtual_portal_hostname
    The host name of the target virtual portal.

We can determine the URL context and the host name of the target virtual portal with the Manage Virtual Portals administration portlet.


Evaluation order

The portal evaluates properties for virtual portals in the following order and returns the appropriate value:

  1. The portal checks for a specific property defined for a virtual portal by the context, hostname, or default keyword. The value of the property is returned.

    If we define conflicting values for a virtual portal with different properties, the results can be unpredictable. For example, this issue can occur if we define one value with the context keyword and a different value with the hostname keyword. To avoid problems, use only one value.

  2. If no specific property is defined for a virtual portal, the portal checks for a property defined by the global keyword. The value of the property is returned.

  3. If no global property is defined, the value null is returned.


Parent Portal service configuration