Microsoft Office Tutorials and References
In Depth Information
Figure 6-1. PerformancePoint services and related components
The PerformancePoint end-user experience is designed to be very simple. A PerformancePoint dashboard
is deployed as nothing more than a folder containing one or more web pages within a SharePoint library. These pages
contain all of the user interface elements necessary to perform complex business analysis on the underlying business
data. This user interface is designed to require very little specialized training. With some experience, most users
find the scorecards, charts, and reports very easy to interpret and manipulate. All of this content is delivered via
a web browser, of course, but there are also many opportunities to take data offline into office applications such
as Excel for deeper ad hoc analysis.
To deliver this sophisticated user interface, the key performance indicators (KPIs), scorecards, dashboards,
and other BI components must first be defined and deployed to SharePoint. The tool for accomplishing this is the
Dashboard Designer, a Windows application for defining BI components and deploying them to SharePoint.
This tool does not need to be separately downloaded and installed. It is automatically installed as a “one-click”
application when needed. See “Authoring and Publishing PerformancePoint Solutions” later in this chapter for
a tour of this tool. Note that this is a development tool and is not designed for use by most end users. With a little
bit of training, end users can build fully functional dashboards.
At the application layer, PerformancePoint conforms to the typical design of a SharePoint service. It is made up
of a service process and a proxy component. The proxy component provides code running within the IIS application
pool process with access to the functionality of the PerformancePoint service application. The service runs as an
independent process in the operating system and is often deployed on a separate tier of application servers that sits
between the web front-end server and the database servers, as shown in Figure 6-1 .
Search JabSto ::