Thủ thuật Sharepoint 2010 part 81 pot

608  CHAPTER 20 PerformaNcePoiNt services aNd BUsiNess iNtelligeNce 9. This chart report can now be added to a dashboard, and then Designer can be used to publish the dashboard to the Dashboards library. This exercise is left to readers to do on their own. The result is displayed in Figure 20-27. FIGURE 2027 This completes the process for verifying the PerformancePoint installation and configuration, as well as the brief introduction of the Dashboard Designer’s capabilities. Reusing Designer Objects PerformancePoint objects can be reused by different authors. For example, the Workspace Browser can copy and paste items in the same or different display folders, provided the items remain within the same site collection. To illustrate this capability, you will make a copy of an object, make some changes to it, and then save it to a different website in the same site collection: 1. Create a new website in the same site collection as the Business Intelligence Center, and use the Business Intelligence Center template. For this example, name the site BI Center II. 2. Open Dashboard Designer. In the Workspace Browser, click PerformancePoint Content. In the Home tab of the Ribbon, click Refresh. 3. Click the Add Lists button in the Workspace group in the Ribbon. This should reveal the Add Lists dialog shown in Figure 20-28. You should see an entry for BI Center II, FIGURE 2028 Introduction to Dashboard Designer  609 and Data Connections and PerformancePoint Content. Click BI Center II and then click OK. This should add a second PerformancePoint Content entry to the Workspace Browser. The first entry is for the original website; the second is for the website you just created in step 1. 4. You now need to make a copy of the objects that you would like to modify and reuse. Expand the folder that contains the dashboard item you want to reuse. Select the object and then right-click the object and choose Copy. For this example, select the Chart Report. 5. Select the new PerformancePoint Content entry and paste the object there as shown in the Workspace Browser in Figure 20-29. 6. Rename the Chart Report to Chart Report v2. Save the copy of the chart to SharePoint, and confirm that the report has been saved to the PerformancePoint Content library in the BI Center II website. You can now make any necessary changes to this report without affecting the original report or any dashboards that use the original report. The previous discussion focused on reusing PerformancePoint objects by different authors in the same site or across different sites in the same site collection. This is a very practical use case that occurs frequently within an organization. Another scenario that is also very common and critical to an organization is the object promotion process, which takes PerformancePoint objects created in one SharePoint farm and then copies them to another farm. This example includes creating objects in an authoring or development environment, moving them to a test environment, and then finally moving them into a production environment. You’ll learn how to do that next. Promoting PerformancePoint Objects across Environments Dashboard Designer should be used to create PerformancePoint objects in a development envi- ronment so that the authoring process does not negatively impact the production environment. Obviously, once the objects have been developed, there needs to be a promotion process to move them into a test environment and subsequently into a production environment. Dashboard Designer content includes metadata with information about objects such as dashboards, KPIs, filters, score- cards, data sources, and reports. As you plan your promotion process, there are several things to keep in mind: Moving content across servers requires that the destination SharePoint Server’s version, ser-  vice packs, hotfixes, and so on are the same as those of the source SharePoint Server. Dashboard Designer objects need to have unique names to ensure that objects on the destina-  tion server are not overwritten. Obviously, this requires some planning as you set up each of the different source and destination environments. You can simplify this by implementing an object naming convention that includes information such as server, site, library, etc. Make sure there are no missing dependencies when you import objects and when you are cre-  ating the workspace file. As you’ve seen, the objects have dependencies on data connections, just as dashboards have dependencies on the objects contained in the dashboard. FIGURE 2029 610  CHAPTER 20 PerformaNcePoiNt services aNd BUsiNess iNtelligeNce All data sources must have unique names—even when the data sources reside in different dis-  play folders. When promoting objects to production, make sure that your data sources point to the pro-  duction server. The process used in this example imports the workspace containing the objects to be promoted into the designer and then deploys them to the proper server. Let’s see how the promotion process works using Dashboard Designer: 1. Open Dashboard Designer in the SharePoint site to which you want to promote the content. Ensure that you are connected to the site by checking the lower-left corner of the designer for connection information. 2. Click Import Items on the Home tab to open the Import Items dialog. 3. Navigate to the workspace file (<name>.ddwx) in the Import Items window. Select the file and then click Open. This will display the Import Items to SharePoint dialog, shown in Figure 20-30. FIGURE 2030 4. As you can see, Figure 20-30 displays the first step to import content using a wizard. There are three steps in the process: location mapping, importing, and the results. The purpose of this dialog is to choose the destination for the items to be imported. Administrators are warned that imported items will overwrite existing items in the destination that have the same name. The window contains a list of folder names beneath two column headings labeled Import from and Copy to. If items have the same name, as shown in the figure, you can distinguish Introduction to Dashboard Designer  611 source and destination by placing the cursor over the item; a tooltip will display the neces- sary information. Note that items beneath the Copy to column are hyperlinked so that the specific location at the destination can be selected. For each location under Copy to, click the destination folder. The Add List dialog opens, enabling you to select a destination for the dashboard content or object. You must select a destination list or library in order for the Next button to be enabled. 5. Once the destination information is selected, you have two other options to consider, although neither option is enabled by default or required for the import: Import data sources that already exist in the destination—This option will overwrite  data sources that already exist in the destination if the workspace file being imported contains a data source with the same name and display folder. If this option is not selected, data sources with the same name and display folder will be skipped. Import items with missing dependencies—This option will import items that have  missing dependencies. These objects must be repaired manually at the destination. For example, if a scorecard is missing a related KPI, the import process will import the scorecard but a warning dialog appears in the wizard if the condition is detected in the workspace file. 6. Once selected, click Next. On completion, the dialog shown in Figure 20-31 is displayed. This dialog indicates the status of the import, the number of new items created, the number of items updated, the number of items skipped, and the number of items that failed to be imported. There is also an option to view a log with a more detailed summary. FIGURE 2031 7. You’ll also notice in Figure 20-31 an option to add the imported items to your workspace, which is enabled by default. Click Finish to complete the promotion process. 612  CHAPTER 20 PerformaNcePoiNt services aNd BUsiNess iNtelligeNce IMPORTING PERFORMANCEPOINT SERVER 2007 CONTENT TO PERFORMANCEPOINT SERVICES 2010 The following discussion applies to companies that have dashboard content stored inside PerformancePoint S erver 2007 that they would like to import into PerformancePoint Services 2010. Content import must be performed by a SharePoint 2010 farm administrator. Planning SharePoint 2010 provides a wizard-driven process for importing dashboard content from PerformancePoint Server 2007 (PPS2007) into PerformancePoint Services (PPS2010) in SharePoint Server 2010. The import wizard walks the administrator through the process of importing dash- boards, scorecards, data sources, KPIs, and so on. After the data import process is complete, the administrator or object author must deploy each individual dashboard to their new SharePoint Server 2010 locations. Before performing the import, you must be aware of several key factors that may affect the integrity of the import. These are summarized in Table 20-4. TABLE 204: Factors for Consideration When Planning the Import Process TOPIC DESCRIPTION Report types PerformancePoint Services does not support all the report types that were available in PerformancePoint Server 2007. The following report types are not supported and will not be imported: Trend Analysis Charts, Pivot Tables, Pivot Charts, and Spreadsheets. Local administrators PPS2007 makes the local server administrator a PPS2007 administrator. In SharePoint Server 2010, that individual is not automatically made an adminis- trator, but can be assigned manually if necessary. Dashboard creation and deployment These apply to PPS2010. The farm administrator requires at least Contribute permissions on content lists and data source libraries to create and edit dashboard items. Site collection administrators need at least Contribute permissions on data source libraries only. The site administrator or site mem- ber needs at least Contribute permissions on content lists and data source libraries. Anyone deploying objects from Dashboard Designer to SharePoint Server 2010 must have at least Designer permissions. User access and content security PPS2010 uses the SharePoint Server 2010 user access and content security model, which is very dierent from that of PPS2007. PPS2007 has its own server and database for storing metadata and content, and security is applied globally at the server level and on each individual object. In PPS2010, meta- data and content is stored in lists and libraries. . objects from Dashboard Designer to SharePoint Server 2010 must have at least Designer permissions. User access and content security PPS2010 uses the SharePoint Server 2010 user access and content. PerformancePoint Services 2010. Content import must be performed by a SharePoint 2010 farm administrator. Planning SharePoint 2010 provides a wizard-driven process for importing dashboard content. In SharePoint Server 2010, that individual is not automatically made an adminis- trator, but can be assigned manually if necessary. Dashboard creation and deployment These apply to PPS2010.