Microsoft Office Tutorials and References
In Depth Information
Chapter 3: Architecture
This chapter goes behind the scenes and explains how the scenarios discussed in Chapter 1 work.
After reading this chapter, you should have a better understanding of what Excel Services does,
and how it does it.
The first part of this chapter begins with a discussion of the Microsoft Office SharePoint Server
architecture. It then examines the main components of Excel Services — the Excel Calculation
Server (ECS), the Excel Web Access (EWA) Web Part, and the Excel Web Services API — and the
flow of information between them.
The second part of this chapter examines the basic operational concepts of Excel Services: sessions,
workbook operations, querying from external databases, caching, scaling the system, thread
management, and charting.
The last section of this chapter revisits many of these topics and a few more from the point of view of
performance. It recaps the architecture of the server and describes how you can make the most out of
the hardware. Here you will explore the use of load balancing, networking, memory resources, CPU
resources, I/O, and charting, as well as the interaction between the client machine and the browser.
Getting to Know Excel Services
To get started, take a look at a simple scenario and the main server components that are involved.
Say you are a user who authors an Excel workbook and saves it to a SharePoint document library.
You create a new SharePoint web page and add an EWA Web Part to it. You modify the EWA
properties to point it to the workbook. Then you browse to the web page to see the workbook displayed
as HTML in the browser inside the EWA. Figure 3-1 shows an example of what this web page might