This chapter uses the following terminology:
Figure 22.1 shows a list of catalogs from which you can import Web Parts to a digital dashboard.
Figure 22.1 Catalogs of Web Parts
Whether you deploy a local Web Part catalog or a dedicated catalog server, use the instructions in the following section. In addition to setting up your own catalog, you can populate your gallery with two additional online Web Parts catalogs.
The Microsoft Web Part Gallery is a public catalog that is available on the Microsoft Web site and contains a variety of Web Parts authored by Microsoft. You can access the Web Part Gallery only from the Contents page of a digital dashboard, by clicking the Web Part Gallery link. SharePoint Portal Server and the SQL Server digital dashboard are both linked to this catalog in the Contents management page by default. There is another Web Part Gallery that is available from Microsoft, which includes Web Parts from third-party companies. The Microsoft Web Parts in this gallery are in a self-extracting compressed format. You must download, uncompress, and import these Web Parts into your local catalog or catalog server, or directly into your digital dashboard. For more information about public catalogs that are available from the Microsoft Web site, see Appendix B, For More Information.
This section outlines the following steps to create a custom catalog:
You must assemble a collection of Web Parts for your catalog. You can do this using either of the following methods:
You can associate a Web Part with multiple files. A Web Part includes an Extensible Markup Language (XML) document with a .dwp file name extension, and associated resources, such as Extensible Stylesheet Language (XSL) files, Graphics Interchange Format (GIF) files, and, style sheets, if they exist. When you collect Web Parts, verify that you have all of the associated resource files. The resources usually reside in the webpartname_files subdirectory. In the code of the Web Part, you should see the start <resource> tag, the end </resource> tag, and a reference to the resource files. When you import a Web Part, the Web Part automatically imports the resource files and stores them in the proper location. If the RESOURCE elements exist in the Web Part, confirm that the corresponding files are in the proper location.
You can designate a SharePoint Portal Server computer or a computer with the SQL Server dashboard installed to act as a catalog server. A computer with the SQL Server dashboard installed includes a local catalog by default. You must create a local catalog for SharePoint Portal Server.
The advantages and disadvantages of storing the catalog in each location follow:
SharePoint Portal Server. Although you can use SharePoint Portal Server to set up a catalog server quickly and easily, it does not offer categorization of Web Parts. Figure 22.2 shows a catalog setup on a SharePoint Portal Server computer.
Figure 22.2 Web Part catalog on a SharePoint Portal Server computer
SQL Server Digital Dashboard. Offers categorization of Web Parts. This allows you to group them in meaningful categories such as accounting, personal, Internet, and so on.
You can mix and match catalog servers with dashboard servers. This means that you can use a catalog server (using the SQL Server dashboard) with your SharePoint Portal Server and vice versa. Your needs determine which deployment is most appropriate. If you are setting up a computer that is running SharePoint Portal Server for a small group of users and want to quickly give them a custom catalog, it is easiest to create a local catalog on the same server. If you are setting up a single, large catalog server with hundreds of Web Parts for thousands of dashboards and users, you may want to consider setting up a catalog on a computer with SQL Server dashboard installed because of the increased flexibility of categorization.
After you choose a catalog server, you need to populate the catalog and make it available to users. For more information about catalogs, see Appendix B.
You can add, modify, or delete the list of Web Parts that are displayed in the local catalog or a custom catalog of a computer with the SQL Server dashboard installed.
To modify the catalog, edit the Wplist.xml file that resides in the Web folder that contains the Web Parts. This file determines which Web Parts are present in the catalog. It also defines the categories that group Web Parts together. You can edit the Wplist.xml file to add new categories or to modify the list of Web Parts that appear in a catalog.
To create a new category, define a new CATEGORY element for it. To add or delete a Web Part, create or delete a WEBPART element.
A CATEGORY element defines a specific category that you subsequently use to group Web Parts. It is also a container for the following elements:
The following example shows the CATEGORY element for Administration Web Parts:
<Category> <ID>Administration</ID> <Description>Dashboard Administration</Description> </Category>
A WEBPART element defines all of the Web Parts that are contained in a catalog. It is also a container for the following elements:
The following example shows the WEBPART element for the Dashboard View Web Part in the Administration dashboard:
<Webpart> <Title>Dashboard View</Title> <Description>The Dashboard Folder View Web Part displays the hierarchy of dashboards and folders on the administration dashboard. An administrator can remove dashboards or create new ones.</Description> <Filename>Dashboard%20View.dwp</Filename> <CategoryID>Administration</CategoryID> </Webpart>
The Contents management page of a dashboard renders the local catalog and Web Part Gallery catalog based on XML definitions by default. In addition to these predefined catalogs, you can add custom catalogs that organize Web Parts in different categories, or link to third-party catalogs.
To add a new catalog, create a new Web folder in the DAVCatalog root folder. Similar to the Parts folder, use this folder to store the Web Parts you want in the new catalog, and then update the Catalogs.xml file to point to the new catalog. The catalog entries appear in the order in which they appear in the Contents page.
To delete a catalog, remove the definition from the Catalogs.xml file. To modify the contents of the local catalog of a computer with the SQL Server dashboard installed, edit the Wplist.xml file as described previously.
The WEBPARTCATALOG element defines a specific catalog. It is a container for the following elements:
The following example shows how the Catalogs.xml file defines the Local Catalog through the WEBPARTCATALOG element:
<DDF:WebPartCatalog> <DDF:CatalogName>Local Catalog</DDF:CatalogName> <DDF:href>partcatalog.asp?FolderID=_stPortalServer_/_stPortalVRoot_/Parts/</DDF:href> <DDF:Description>Parts available in the Local Catalog.</DDF:Description> </DDF:WebPartCatalog>
The Catalogs.xml file is a dashboard factory file that determines which catalogs are present in the Contents management page. You can use any XML editor to modify this file.
SharePoint Portal Server also supports catalog modifications. You can add Web Parts to a catalog on a computer running SharePoint Portal Server.
You must be coordinator of the workspace and enable viewing of hidden files and folders to see the Portal/Resources folder.
http://server_name/workspace_name/dashboards/gallery?cmd=catalog
When the ?cmd=catalog parameter is added to the end of the URL, a catalog view is displayed instead of a dashboard view.
The following example shows an entry in the Catalogs.xml file of a SharePoint Portal Server computer referring to a catalog server that uses the SQL Server dashboard:
<?xml version="1.0" ?> <DDF:CatalogInformation xmlns:DDF="urn:schemas-microsoft-com:dashboardfactory:"> <DDF:WebPartCatalog> <DDF:CatalogName _loc>My Company's Internal Catalog</DDF:CatalogName> <DDF:href _loc>http://webparts/dashboard/partcatalog.asp?FolderID=http://webparts/DAVCatalog/Parts/</DDF:href> <DDF:Description _loc>A collection of sample parts for use with Microsoft's Digital Dashboard</DDF:Description> </DDF:WebPartCatalog> </DDF:CatalogInformation>