Configuring Customized Portal Desktops for Tenants 

Use

The portal desktop is the presentation area which displays onscreen content to the users of a tenant. A portal desktop comprises a framework page, which is made up of structural iViews and pages, and any number of portals themes. For general information, see Portal Desktops, Portal Themes, and Framework Pages.

All documentation references in this topic are located in the Portal Administration Guide.

By customizing the portal desktop it is possible to have different branding elements and navigation concepts for each tenant running in the same multitenant portal. For example:

·        A customized portal theme can present branding elements of the tenant's organization, such as its logo in the portal header area, and the brand colors of the tenant's organization.

·        A customized framework page can present a unique navigation concept in the portal, such as a one-level top-level navigation, hover-based menus, or navigation restricted to the Detailed Navigation iView.

This procedure is optional. If you do not create a custom portal desktop or modify the default display rules, each tenant will receive the default portal desktop shipped with the portal.

 

Prerequisites

·        To work with portal desktops and display rules, you are assigned access to the Portal Desktop Editor and Portal Display Rules Editor, respectively. Note that both editors are integrated into the same tool (Desktops & Display Rules) which is assigned by default to the standard system administrator role.

·        You have been assigned at least administration read-writepermission to the Portal Catalog folder in which you want to create or edit a portal desktop object.

·        You have been assigned at least administration read permission to copy the relevant framework page, theme, portal desktop, and portal display rule objects.

·        You have been assigned at least administration read-writepermission to edit the relevant framework page, theme, portal desktop, and portal display rule objects.

 

Activities

·        Global and tenant content administrators can create and edit framework pages using the Page Editor (see Portal Pages).

·        Global and tenant administrators can create and edit the portal themes for each tenant using the Theme Editor (see Creation of Themes by the Theme Editor).

§         To customize the logo and branding images in the portal header, create a new theme for the tenant and modify the relevant images in the masthead area. Note that the masthead area contains several properties that apply to the complete masthead display; each property pertains to a different segment of the masthead. Then, assign the new theme to the tenant's portal desktop object.

§         Tenant business users see only the themes that have been assigned to their portal desktop.

·        Global and tenant administrators can create and edit the portal desktop objects for each tenant by integrating custom framework pages and portal themes, using the Portal Desktop Editor. For more information, see Creating and Editing a Portal Desktop.

·        After a portal desktop has been created, global or tenant administrators must assign the portal desktop to users of the tenant through display rules using the Portal Display Rules Editor. For more information, see Portal Display Rules and Defining Portal Display Rules.

·        The Portal Desktop Editor, Portal Display Rules Editor, and Theme Editor are assigned by default to the standard system administrator role; however, the standard system administrator role must not be assigned as a whole to a tenant administrator. If you want a tenant administrator to work with these editors to manage its own portal desktop objects, display rules, and themes, you need to create a new role for the administrator with the required iViews, or add them to an existing delegated administrator role.

·        All standard themes shipped with the portal are located in a single folder (Portal Content/Themes). If you want tenant administrators to use the Portal Desktop Editor, a global administrator can set up tenant-specific folders under the Portal Content/Themes folder and then assign the required portal permissions so that tenant administrators see their themes only.

·        If you allow tenant administrators to work with the Portal Display Rules Editor, you must carefully consider if you want them to be able to access the portal's master rule collection (main_rules). The master rule collection defines all display rules for all global users and tenants of the portal (see Master Rule Collection). Depending on how you have named the rules, the names of all tenants defined in the portal may be visible to all tenant administrators.

To overcome this, you can assign the master rule collection to a global administrator only, and allow the tenant administrators to work with an isolated tenant-specific rule collection. The global administrator can then nest the tenant-specific rule collections into the master rule collection.

The global administrator must verify the contents of any tenant-specific rule collection before nesting it in the master rule collections.

 

Example

The following example demonstrates how content administrator and system administrator work together to create customized portal desktops for three tenants, each displaying their personalized logo in the portal header.

...

       1.      In the Portal Content Studio, the content administrator creates a new sub-folder in the Portal Catalog for each tenant under the Portal Content/Themesfolder.

       2.       In the Theme Editor, the system administrator does the following:

                            a.      Creates a new portal theme for each tenant.

                            b.      Saves each theme in the tenant's folder under Portal Content/Themesfolder.

                            c.      In each theme, assigns the portal header images to the relevant properties in the masthead area.

                            d.      Adjusts the look and feel, such as background and foreground colors, of each theme to match the corporate branding identity of the tenant customer.

       3.      In the Portal Content Studio, the content administrator creates a delta link object from the standard Default Framework Page object (located in the Portal Content/Portal Users/Standard Portal Users folder) in the Desktop folder of each tenant.

System administrators can also copy framework pages using the Portal Desktop Editor.

       4.      In the Portal Desktop Editor, the system administrator creates a delta link object from the standard Default Portal Desktop object (located in the Portal Content/Portal Users/Standard Portal Users folder) in the Desktop folder of each tenant.

       5.      In the portal desktop object created for each tenant, the system administrator does the following:

                            a.      Removes all default SAP themes.

                            b.      Removes all default framework pages.

                            c.      Adds the new theme you created for the tenant.

                            d.      Adds the new framework page you created for the tenant.

                            e.      Sets the new theme and framework page as default.

       6.      In the Master Rule Collection object (main_rules) located in the Portal Content/Portal Administrators/Super Administrators folder, the system administrator adds a rule for the users of each tenant. For example:

IF User = tenanta*

THEN Portal Desktop = pcd:portal_content/Tenants/TenantA/Desktop/defaultDesktop

IF User = tenantb*

THEN Portal Desktop = pcd:portal_content/Tenants/TenantB/Desktop/defaultDesktop

IF User = tenantc*

THEN Portal Desktop = pcd:portal_content/Tenants/TenantC/Desktop/defaultDesktop

IF User = *

THEN Portal Desktop = pcd:portal_content/every_user/general/defaultDesktop