Siebel Analytics Web Administration Guide > Managing Siebel Analytics Web Security >

Guidelines for Setting Up Siebel Analytics Web Security in the Web Catalog and Dashboards

To set up a secure Web Catalog and secure dashboards, you must understand the information presented in the previous chapters, because you will be working with Web Catalog, dashboards, and Web Groups.

This section contains the following topics:

Creating Siebel Analytics Web Groups

When you create a Web Group, a shared Web Catalog group folder is automatically created. For more information about Web Groups, see Types of Siebel Analytics Web Groups. For more information about the group folder, see Setting Up the Siebel Analytics Web Catalog Structure.

Setting Up the Siebel Analytics Web Catalog Structure

The Web Catalog has two main folders:

Figure 6 shows the recommended higher-level folder structure for the Web Catalog.

Figure 6.  Recommended Catalog Folder Structure

The Web Catalog structure shown in Figure 6 makes it easier for users and administrators to reorganize content and make shared dashboard sections available. This, in turn, facilitates My Dashboard creation by allowing users to select from shared content.

Items shown within brackets ( [ ] ) are optional. Items shown within angle brackets ( < ) should be replaced with the appropriate name.

Group Folder

When you create a Web Group, the system automatically creates a shared folder for the group. All members of the Web Group are automatically given Read permissions to this folder. These permissions are inherited by any subfolders that you create.

Group folders hold shared dashboard content that pertains to only members of the Web Group. The shared content can be further organized into subfolders under the Group folder.

NOTE:  You may want to remove this folder and grant group permissions to other folders if there is no group-specific content.

Common Folder

Dashboard sections that are shared across groups are saved in a Common folder under the /Shared folder. Content can be organized into subfolders under the Common folder.

Requests Folder

When you create requests in Siebel Answers that you want to share, save them in a Requests folder in the /Shared folder.

Create a folder for each subject area in the Requests folder for storing requests against that subject area. This allows you to manage permissions at the level of the subject area. If two or more subject areas are closely related, so that users with permission to one would almost always have permission to the other, you could create a single folder to store requests against both subject areas.

NOTE:  If a user is given permission to a request in the Web Catalog that references a Subject Area to which the user does not have permission, the Siebel Analytics Server still prevents the user from executing the request.

In cases where you have requests that span subject areas (requests that involve SQL subqueries), you can put them in the folder for any of the subject areas, or create a new folder for users that have permission to these subject areas.

For more information about working with the Web Catalog, see Administering the Siebel Analytics Web Catalog.

Setting Permissions To Siebel Analytics Web Catalog Items

Before setting permissions to the Web Catalog items you have created, review the information in About Setting Siebel Analytics Web Permissions.

Create Shared Siebel Intelligence Dashboards

After setting up the Web Catalog structure and setting permissions, you can create shared dashboards and content for reuse by others. If you did not specify a dashboard when creating a group, you can create one now, selecting the appropriate group folder.

The advantage to creating shared dashboards is that sections that are created in the shared dashboard are actually shortcuts to folders in the /Shared folder. As such, you can remove them and add them again in a different column, page, or even a different dashboard. Users can quickly create a My Dashboard from existing shared sections by clicking the Add Folder link and selecting the appropriate folder from the /Shared/Group or /Shared/Common folders in the Web Catalog.

If you plan to allow multiple users to modify the Web Group's default dashboard, consider putting these users into another group. For example, suppose you create a Web Group called Sales and create a default dashboard called SalesHome. Of the 40 users that are members of the Sales group, suppose that there are three who need to have the ability to create and modify content for the SalesHome dashboard. It is recommended that you create a SalesAdmin group, with the same permissions of the primary Sales group. Add the three users who are allowed to make changes to the SalesHome dashboard and content to this new SalesAdmin group, and give this group the appropriate permissions to the Web Catalog. This allows them to create and modify content for the SalesHome dashboard. If a user no longer requires the ability to modify dashboard content, you can change the user's group membership to Sales. If an existing Sales group member needs to have the ability to create dashboard content, the user's group membership can be changed to SalesAdmin.

Dashboards are stored in a special folder, _Portal, that is hidden (unless the option to show hidden items is checked when working with the Web Catalog). The hidden _Portal folder is located directly underneath a group folder, as shown in the example in Figure 7. Because the dashboard is contained in the Group folder, all the permissions you set to the group folder are inherited.

Figure 7.  Dashboard Folder Structure in the Catalog

You can create multiple dashboards within a group folder, each of which has its own folder in the /_Portal folder, named from the dashboard name that you assign.

Underneath the specific dashboard folder, for example, /_Portal/SalesGroup Dashboard, are folders that correspond to the pages you have created in the dashboard.

Within the page folder are folders for the columns. Column folders are assigned names automatically by the system. Within the column folders are the sections (folders or shortcuts to folders) that contain the items or shortcuts to items that appear in the dashboard.

For more information about creating shared dashboards, see Creating and Deleting Shared Siebel Intelligence Dashboards.

Adding Shared Siebel Intelligence Dashboards Pages and Content

After you have created dashboards, you can add pages and content.

Adding Pages and Content

For information about adding pages and columns, see Analytics Web Online Help.

Adding Sections

A section is a folder, or a shortcut to a folder, that appears within a dashboard. For the procedure for adding sections to a dashboard, see Creating and Deleting Shared Siebel Intelligence Dashboards.

When adding requests from Siebel Answers to a section, do one of the following:

If you are working with content that is specific to a number of group folders, you might want to create a new folder directly underneath the /Shared folder to use, and set permissions to the new folder to Read for the appropriate groups.

Adding Shared Siebel Analytics Content

You can create shared content that can be used within shared and My Dashboard sections. For example, you could create a library of images by creating a folder called Images in the /Shared/Common folder. Add this folder as a section in a dashboard, perhaps the My Dashboard of the administrator (although it does not really matter because once you place the images in the section you can remove it from the dashboard). Remember, it is a shared section, so the folder still exists in the shared portion of the Web Catalog. Edit the section and click the Image link to add each image that you want in your library.

NOTE:  If there are a number of libraries that you want to make available for sharing, you might want to create folders within the /Common folder called /Sections, and /Content or /Libraries, so it is easier distinguish when using the common sections and content in other dashboards. To use the shared content in a section of My Dashboard, the user can edit the desired section, click the link Item from Catalog, navigate to the /Shared/Common/Images folder, and click the image to include.

This same mechanism should be used for any logos, images, scripts, links, copyrights, and so on, that might be used in more than one dashboard or dashboard section. This allows you to change the item in one location and have it immediately reflected in all dashboards.

In this version of Siebel Analytics Web, the links Existing Request and Item from Catalog function identically. They allow you to choose any item, including existing requests, from the Web Catalog. This places a shortcut to the item you select in the section.

Testing the Siebel Intelligence Dashboards

Before releasing dashboards and content to the user community, perform some tests.

To test the dashboard

  1. Verify that users with appropriate permissions can correctly access it and view the intended content.
  2. Verify that users without appropriate permissions cannot access the dashboard.
  3. Verify that styles and skins are displayed as expected, and that other visual elements are as expected.
  4. Correct any problems you find and test again, repeating this process until you are satisfied with the results.

Setting Up a Virtual Directory For Shared Siebel Analytics Documents

It is recommended that you set up a virtual directory on the Web server for shared documents. Name the directory /DashboardFiles and map it to a shared network directory of the same name.

This allows users with the appropriate permissions to publish files to this folder, and reference these files by their relative URL names rather than by their fully qualified network share names, for example, /DashboardFiles/AnnualReport.doc instead of \\SharedServer\CommonShare\DashboardFiles\AnnualReport.doc.

Releasing Siebel Intelligence Dashboards To the User Community

After testing is complete, notify the user community that the dashboard is available, providing the relevant network address.


 Siebel Analytics Web Administration Guide
 Published: 11 March 2004