Microsoft Office Tutorials and References
In Depth Information
Microsoft Office SharePoint Server
After a user or the calling application is authenticated, authorization is done against the resource being
requested. This can be any resource in the SharePoint store. The scenarios and examples in this topic
cover libraries of workbooks, specific workbooks, and dashboards. Office SharePoint supports specific
rights, and users or groups of users can be granted these rights. For example, a user may have the rights
to open, view, and edit a workbook in the browser and the client, or the user may have only the right to
view the workbook in the browser.
Office SharePoint Server also includes a single sign-on (SSO) store. This provides an additional
mechanism by which users are authenticated, and is especially relevant for scenarios that include workbooks
connected to external data sources. The SSO store infrastructure is pluggable, and third-party solutions
can replace the built-in solution.
Chapter 8 describes the security model, the various authentication mechanisms, and the specific user
rights in more detail. Later in this topic, you will see how Excel Services uses this infrastructure to load
workbooks, query external data sources, and provide results.
Web Part Pages
A key underlying concept for Office SharePoint Server is Web Part Pages . Practically all the web pages
served by Office SharePoint Server are Web Part Pages. This is an ASP.NET 2.0 technology that enables
you to place numerous web parts (equivalent to web controls) on a single web page, and defines how
these web parts are laid out, as well as how they can interact with one another. Office SharePoint
Server ships with a large selection of out-of-the-box web parts, and developers can create their own
and deploy them to the server. Out-of-the-box web parts enable you to display documents in a specific
document library, views on a task list, RSS content aggregation, a list of links, and simple Hypertext
Markup Language (HTML) or rich text content, among other things. Excel Services has a web part
component as well, through which spreadsheets are rendered in the browser.
Web parts can have numerous properties that control and customize them. Many of these settings can
be personalized so that different users will receive different behaviors when they view the same page.
Using this functionality, it is possible to set up a page that includes a list of tasks, and users logging in
will see the tasks assigned to them.
Web parts on the same page can also interact, passing data between them. For example, the author of
a Web Part Page can connect a web part that lists workbooks in a document library to an Excel Services
web part. A user viewing the page can select from the list of workbooks, and the selected workbook is
displayed. Behind the scenes, the workbook URL is passed between the two web parts.
Web parts are the foundation for building composite applications as well as BI dashboards.
Content Storage and Management
Office SharePoint Server provides the default content store for Excel Services scenarios. The core storage
container is a document library , which, in turn, is associated with a site. Document libraries are
conceptually equivalent to file system folders. As shown in Figure 1-4, they can contain virtually any file,
including images, Word documents, PowerPoint presentations, Excel workbooks, and web pages. Document
libraries can also contain additional document libraries or subfolders.