In this section: |
If your organization supports a diverse range of customer groups that cover multiple corporate entities or geographic regions, you may need to create portals that make a single set of information available to a variety of groups using a variety of corporate identities.
By organizing users from different functional or business groups into SaaS tenant workspaces and creating customized themes and logos for each one, you can create portals that make the same information available to diverse customer groups in multiple customized environments.
In this specialized portal configuration, each tenant workspace contains the users assigned to a specific entity. As shown in the following image, they also contain files for the logo and theme that customize the portal interface to a look and feel that is familiar and appropriate for the members of the selected group.
A centralized workspace containing users from all tenant groups, supports the portal itself. All development and maintenance of portal content take place within the central workspace, maximizing the efficiency of information delivery.
Users assigned to individual SaaS Tenant groups view these centralized portal pages using the logo and tenant theme that are appropriate for their group.
To allow for varying themes and logo files, the centralized portal uses symbolic IBFS Paths that present users with the portal theme and logo assigned to their group. Symbolic IBFS paths use pre-configured variables, such as ##{WF_PrimaryGroup}, to create a relative path to these resources that are resolved when a user runs the portal.
Once established, the Portal uses relative paths to theme and logo file images stored in SaaS tenant groups and provides administrators with a customized user interface that is efficient and easy to maintain.
The configuration of a Designer Portal that supports multiple SaaS Tenant groups with varying themes and logos is a multiphase process that requires the creation of tenant workspaces for each tenant group and a separate workspace for the content portal.
For more information, see the How to Create a Workspace topic in the TIBCO WebFOCUS® Security and Administration technical content.
The tenant workspace group must be defined as the primary group for each user.
For more information, see the How to Add a User to a Group topic in the TIBCO WebFOCUS® Security and Administration technical content.
Save the tenant_theme.css file in the Hidden_Content folder of the tenant workspace.
For more information about assigning or mapping users to groups, see the TIBCO WebFOCUS® Security and Administration technical content.
In this section: |
How to: |
The symbolic path defined in the Logo field of the centralized portal directs the call for a logo image to a customized logo file in the workspace of the user who issued the request to run the portal.
In order for this link to work successfully, each tenant workspace must contain its own logo file in the Images subfolder of the Hidden_Content folder within the tenant workspace.
Each logo image file must use the same name as the logo file identified in the Logo field of the centralized portal, “logo.”
In this section: |
How to: |
The tenant_theme.css file contains any additional customizations that alter the look and feel of the default portal frame and features.
To ensure that the symbolic IBFS Path in the main portal connects to the tenant_theme.css file for every tenant, you must save it in the Hidden_Content folder of each tenant workspace and include this folder in the full symbolic IBFS path. You must also use the same name for each tenant workspace theme file, tenant_theme.css.
You can use the text editor to create a .css file and enter the classes you wish to add or modify directly.
How to: |
If an individual tenant group needs one or more portal pages that are to be visible only to members of that group, create these pages within the tenant workspace and link to them from the main centralized portal. This limitation ensures that members outside of the tenant group will not see pages intended only for the tenant group.
When you have created a tenant-specific portal page, create a shortcut to it within the tenant workspace. When you create the shortcut within the tenant workspace, the rules of that workspace apply to the shortcut as well as the portal page, and the Navigation bar in the centralized portal will display an entry for the portal page only to users who belong to the tenant group.
You must develop all content for the tenant-specific portal pages within the tenant workspace. The use of content or data sources contained in other workspaces adds an extra group to the configuration that conflicts with the ability of the product to work with ##{WF_PrimaryGroup}.
Use the following generalized steps to create a tenant-specific visualization from new content in WebFOCUS Designer:
Note: Select only data sources that are available within the workspace. Do not use data sources outside of the workspace.
Or
Double-click a field or drag it onto the canvas to add it to the default bucket for that field type.
Prompted filters in the Filter toolbar affect the entire page, while static filters in the Filters bucket affect only the item for which they were created.
The item moves into a container, but no second container is added.
The first item you created moves into a container, and a second container is created.
The entire page, sections, containers, filter controls, and filter cells all have their own set of styling and formatting options.
You can also preview the visualization to see run-time behavior by clicking Run in new window.
Use the following generalized steps to create a tenant-specific visualization from existing content in WebFOCUS Designer:
Or
Create a container for an item by selecting Container on the sidebar and dragging a container onto the canvas, and then adding content to the container.
Note: Select only content that was created within the workspace. Do not include content that was developed outside of the workspace.
The entire page, sections, containers, filter controls, and filter cells all have their own set of styling and formatting options.
You can also preview the visualization to see run-time behavior by clicking Run in new window.
To limit access to a tenant-specific portal page to members of the tenant group, create the shortcut to the page within the tenant workspace. You can copy the shortcut and paste it into the centralized portal structure later.
How to: |
The centralized portal contains all of the links to data sources and content that will be available to tenant users. Content pages, based on a portal template that uses a symbolic reference to tenant_theme.css files, make information available to all users in the appropriate format.
Enter the IBFS Symbolic Path to the variable style sheet file in the Theme field and the Logo field of the main portal. Because you are using IBFS paths that point to the same location in each different workspace, ensure that you use the same location for the logo and theme files in each tenant workspace.
You must develop all content for the centralized portal pages within the centralized portal workspace. The use of content or data sources contained in other workspaces adds an extra group to the configuration that conflicts with the ability of the product to work with ##{WF_PrimaryGroup}.
As you type, WebFOCUS automatically assigns the value you type in the Title field, adjusted to conform to IBFS rules, to the Name field. You can edit or replace this value with a custom name if required.
WebFOCUS also automatically assigns the appropriate IBFS Path to the portal, based on the location of the workspace and the title you enter, to the Path field, and an external version of the path that does not begin with the IBFS parameter in the URL field.
IBFS:/WFC/Repository/##{WF_PrimaryGroup}/Hidden_Content/Images/logo.png
Where:
Is the opening path that identifies the IBFS system, the WebFOCUS Content subsystem, and the Repository where all content folders are located within the IBFS system.
Is the variable that redirects the Path to the primary tenant workspace group to which the user working with the Portal belongs.
Is the folder within each tenant workspace that contains the theme and logo files.
Is the remaining path within the Hidden_Content folder to the logo file. This path must be consistent in all tenant workspaces. In this example, we use a .png file, but you can use other image file formats as well.
Note: You can confirm the validity of the path you use in this field by reviewing the path assigned to the tenant workspace folders in the Properties panel.
IBFS:/WFC/Repository/##{WF_PrimaryGroup}/Hidden_Content/tenant_theme.css
Where:
Is the opening path that identifies the IBFS system, the WebFOCUS Content subsystem, and the Repository where all content folders are located within the IBFS system.
Is the variable that redirects the Path to the primary tenant workspace group to which the user working with the Portal belongs.
Is the remaining path within each tenant workspace to the file containing the theme for members of that tenant group.
Note: You can confirm the validity of the path you use in this field by reviewing the path assigned to the tenant workspace folders in the Properties panel.
Note: When creating pages for the centralized portal, you must only use content that was created within the workspace. Do not include content that was developed outside of the workspace.
How to: |
To include tenant-specific portal pages in the centralized designer portal, you must add shortcuts for the linked pages to the centralized portal.
To ensure that tenant-specific portal pages appear only to the tenant groups to whom they apply, you must create the shortcut to the page within the tenant workspace. You must then copy the shortcut from the tenant workspace and paste it to the portal folder within the workspace that contains the centralized portal.
By creating the shortcut within the tenant workspace, you inherit the security rules of that workspace when you copy and paste the shortcut to the centralized portal workspace. As a result, the shortcuts will be visible in the navigation bar only to tenants who are members of the group.
How to: |
When the designer portal is ready and all tenant workspaces and tenant workspace groups are prepared, you must make the portal and related workspaces available by changing them to Published status.
How to: |
Before you can announce the availability of the portal for general use, you must first ensure that the appropriate theme and logo are assigned to the portal for users from each tenant group.
Remember that the portal fails to display content properly when you run it in the centralized enterprise workspace. You must base your testing on how the portal appears to users from each tenant group, not in the centralized workspace.