Usage scenarios for virtual portals

 

+
Search Tips   |   Advanced Search

 

 

Overview

There are several architectures for delivering multiple portals...

  • Multiple JVMs on multiple physical machines. Portal servers running on multiple server boxes.

  • Multiple JVMs on multiple virtual machines. Portal servers running in a virtualized data center.

  • Multiple JVMs on single machine. Portal servers running on single server.

  • Single JVM on single machine. Single portal server supporting multiple portals.

Virtual portal benefits...

  • Allows a single or shared infrastructure to support several diverse end user groups.

  • Greater value from hardware or software that is not used to its full potential. Reuse a single software license to service several groups of users.

  • Reduced administration effort and quicker deployment of new portals within the existing infrastructure.

Virtual portals share a single JVM and the portal configuration database. Portlet applications are shared across virtual portals. If individual portlet configurations are required, portlet applications can be cloned for the use in a specific virtual portal.

If a shared JVM is not acceptable for the usage scenario, use true portals and have multiple full portal installations on the same hardware unit.

 

Common or separate virtual portal administration

Will each virtual portal be administered by its own group of administrators, or will you have a central administration group for the entire portal installation and all virtual portals ?

We can select a specific group of subadministrators, who can manage the resources and users of a particular virtual portal. The master administrator of the portal installation can set up the privileges of the subadministrators individually for each virtual portal.

If you do not require a specific subadministrator group for each virtual portal, the portal administrators can share the administrative work for all virtual portals.

 

Single or separate user populations

Will a single user population for the entire installation be sufficient, or does each virtual portal need its separate user population ?

With multiple virtual portals we can have dedicated a user population for each virtual portal and ensure that only members of that population can access the virtual portal. This is achieved by using the realm concept provided by the Member Manager. We can configure Member Manager as a custom user registry.

If a common user population for all the virtual portals is sufficient, we can configure a single LDAP instead.

 

Usage scenarios for virtual portals

The following sections describe three typical usage scenarios for virtual portals:

 

Scenario 1: Multi-Portal Enterprise

In this scenario a single enterprise owns and operates multiple different virtual portals on a single portal installation. For example, this scenario can support virtual portals for different parts of the organization such as:

  • Development, production, and marketing
  • Organizations or branches in different locations and foreign countries
  • Affiliate or franchise business models
  • Different branding.

These are some of the typical features of such a virtual portal configuration:

  • The portal installation is operated by the company itself.

  • A common group of administrators is responsible for the administration of all the virtual portals in the installation.

  • The pages and the look and feel are customized individually for each virtual portal.

  • The portlet applications are shared between the virtual portals.

  • All virtual portals share the same single user population.

  • The portal installation typically has between ten and thirty virtual portals.

 

Scenario 2: Workgroup Service Provider

In this scenario one central organization provides virtual portals for a large number of small, decentralized, and independent teams. For example, this can be teamrooms for project management in small work units. This scenario supports virtual portals for different parts of the organization as follows:

 

Scenario 3: Hosted Enterprises

In this scenario a service provider hosts and operates independent enterprises on the same portal installation. For example, this scenario can support virtual portals for different tenants or service customers, such as:

  • A service provider who supports services for small businesses of the same type.

  • A provider who offers services for medical doctor practices.

  • A central banking service provider who offers services to different branches of banks.

The requirements for this scenario include the following:

 

Related information

  1. About multiple virtual portals
  2. Planning for virtual portals
  3. Administering virtual portals
  4. Virtual portals reference
  5. Portal configuration
  6. The XML configuration interface
  7. Administering the portal

 

Parent topic:

Multiple virtual portals