In this section: |
How to: |
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 centralized 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 is appropriate for their group.
To allow for varying themes and logo files, the centralized portal uses symbolic IBFS Paths to 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 Collaborative 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.
As a best practice, we recommend that you use the following workflow when creating a Multi-SaaS Tenant portal using symbolic IBFS paths.
For more information, see the How to Create a Workspace on the WebFOCUS Home Page topic in the TIBCO WebFOCUS® Security and Administration technical content.
For more information, see the How to Add a User to a Group topic in the TIBCO WebFOCUS® Security and Administration technical content.
For more information about assigning or mapping users to groups, see the TIBCO WebFOCUS® Security and Administration technical content.
How to: |
The symbolic path defined in the Custom Theme CSS field of the centralized portal redirects the call for a theme to a customized CSS theme file in the workspace of the user who issued the request to run the portal. In turn, the customized CSS theme file includes a property that identifies the logo to use for the tenant workspace.
This two-stage link enables users to overcome the limitation of the variable file path that can only call a single file, and ensures that the appropriate logo and theme are called for when users open the portal.
In order for this link to work successfully, each tenant workspace must contain its own tenant_theme.css file in the Hidden_Content folder, a subfolder within the Hidden_Content folder entitled Images, and its own logo image file within the Images subfolder.
Each CSS theme file must use the same name as the theme file identified in the Custom Theme CSS field of the centralized portal, "tenant_theme.css." You can use different names for logo image files, but you must ensure that the tenant_theme.css file for a workspace contains the correct name of the logo image file assigned to that workspace.
How to: |
The tenant_theme.css file contains the .bip-logo class that identifies the address of the tenant workspace logo file in the background-image property. It also 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 Page Designer to create this file interactively as described in How to How to Configure Customized CSS Theme Files for Tenant Workspaces Using the CSS Editor. As an alternative, you can use the text editor to create a CSS file and enter the classes you wish to add or modify. If you use this method, be sure to open the text editor from the Hidden_Content folder within the tenant workspace, and select the CSS format, and ensure that all entries conform to syntax requirements and include valid data.
Your cursor changes to a crosshair. You can also click the Highlight inspected element button to pinpoint the element that you want to style more easily.
The Classes field is automatically populated with the correct CSS class name for the selected element, in our example bip-banner-top.
Note: You can also select elements from the Elements drop-down list, or, if you know the CSS class name of the element, you can type it in the Classes field. You can also use the Search field to search for a CSS class using keywords.
In our example, type .bip-banner-top
In our example, type background-color:#56b7e6;.
The banner instantly changes color to the specified hue, as shown in the following image.
Note: If you have entered an invalid CSS class or attribute, the browser rejects it and the change is not reflected in the portal appearance. Any hexadecimal color value you enter is automatically converted into the equivalent RGB value.
Where
is the name of the image file that contains the logo.
background-position:center;
background-repeat:no repeat;
height:45 px;
width:150 px;
For example:
.bip-logo { background-image:url(“Image/CompanyOneLogo.png”); background-position:center; background-repeat:no repeat; height:45 px; width:150 px; }
If a custom CSS file is already applied to this portal, your changes will be saved in that file. If the changes are new, the Save As dialog box opens.
In this section: |
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.
The new stand-alone portal page displays in the workspace. You can now copy, move, and link this portal page to portals.
In this section: |
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 Custom Theme CSS field of the centralized portal. Because you are using an IBFS path that points 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.
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/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.
How to: |
To include tenant-specific portal pages in the centralized portal, you must add them as linked pages to the centralized portal.
The new linked portal page displays in the portal.
How to: |
When the 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 to make the portal and its contents available to all users with their appropriate level of access.
How to: |
Before you can announce 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.
For each tenant group: