WebFOCUS Application and Enterprise Editions
Testing the Designer Portal User Experience
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.
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.
Procedure: How to Publish a Designer Portal
- Sign in as an administrator, if you are not signed in already.
- Right-click the portal in the content area of the WebFOCUS Home Page and select Publish from the shortcut menu.
Adding Tenant-Specific Portal Pages to the Centralized Designer Portal
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.
Creating a Centralized Designer Portal for Common Use
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.
Creating Tenant-Specific Designer Portal Pages
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.
Creating Tenant-Specific Theme CSS Files for Designer Portals
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.
Assigning Customized Logos to Tenant Workspaces for Designer Portals
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."
Understanding the Configuration Requirements for Designer Portals That Use Multiple Themes or Logos
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.
As a best practice, we recommend that you use the following workflow when creating a Multi-SaaS Tenant portal using symbolic IBFS paths.
Testing the Portal User Experience
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.
How to Test the Portal User Experience
For each tenant group: