All other components match those as found in Table 8-1.
Figure 8-1 The Monitoring Server Configuration Manager allows the Monitoring Server
components to be deployed on a single server or across multiple servers.
C h a p t e r 8 : P e r f o r m a n c e P o i n t D e p l o y m e n t a n d S e c u r i t y 287
The primary purpose of this screen is to allow administrators to choose whether or
not the Monitoring Server will be installed on a single machine or distributed across
multiple machines. In scenarios that include web farms for scale-out processing, or
with clustered SQL Server machines for high availability, it often makes sense to
separate components. The Monitoring Server Database will be installed only on the
server running SQL Server, and these machines might not even have IIS installed.
The web servers, meanwhile, would have the Monitoring Server installed, but might
not have the Monitoring Plug-in for Report Designer. The server or servers running
SharePoint will host the web parts that display PerformancePoint Server dashboards,
but PerformancePoint Server itself might be running on separate servers. Separating
the components across servers can lead to increased scalability and improved
uptime. Choosing a standalone configuration installation grays out all the check
boxes and installs everything on the local machine.
Choosing to install the Monitoring System Database presents the administrator
with a screen to specify the server name and database name to use for the monitoring
database.
Pages:
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372