This is not
the case; the Monitoring Server supports the Dashboard Designer and the preview
sites, but does not come into play when dashboards are viewed through SharePoint.
Instead, SharePoint connects directly to the data sources, so all caching and security
for the user??™s session occurs on the SharePoint server. This is true even if you export
the dashboard directly to SharePoint and don??™t use the web parts directly.
On a related note, administrators might want to consider setting up
ConnectionPerUser in the web.config file. ConnectionPerUser sets up dedicated
connections per user rather than pulling existing connections from a connection pool.
This is useful when applying security on individual users because connections in a
connection pool can only be reused if all the connection information is the same, and
this includes the username and password.
Installing the Planning Server
The Planning Server consists of two different web services: a remote administration
service and a database. These are installed on a web server running Internet
Information Services. The Planning Server will also need access to a SQL Server 2005
server, on which the planning database will be installed. The planning database will
290 B u s i n e s s I n t e l l i g e n c e w i t h M i c r o s o f t O f f i c e P e r f o r m a n c e P o i n t S e r v e r 2 0 0 7
run on SQL Server 2005 Standard Edition, but access to Analysis Services requires the
Enterprise Edition.
Pages:
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376