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.
To include tenant-specific portal pages in the centralized portal, you must add them as linked pages to the centralized portal.
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.
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 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.
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.
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.
This content describes the best practices for TIBCO WebFOCUS® security and administration. It is intended for system administrators.
You can generate WebFOCUS Retail Demo sample data and metadata using the WebFOCUS Server or DataMigrator Server, and use it to test WebFOCUS features with a consistent, preconfigured data source. This sample data set is also used in many examples in technical topics and videos, allowing you to follow along to get the same results.
You can generate these sample files using the following steps.
You can create shortcuts to repository files and Master files. Once a shortcut to a Master file is created, you can use it to build visualizations and reports. Once a shortcut to a repository file is created, you can copy, delete, edit, and run this item. You can also publish and share your shortcuts to make them available for other users and groups.
Note: Only users with the opShortcut privilege are able to create shortcuts. For more information on privileges, see the WebFOCUS Security and Administration technical content.
