It is not necessary to run the user interface for the Configuration Manager. The
command line tool is called PMServerConfigManger.exe and is located in %program
files%\Microsoft Office PerformancePoint Server\3.0\Tools\MonitoringConfiguration
by default. There are a number of command line switches that can be used; not
specifying any switches loads the GUI, as shown previously in Figures 8-1 and 8-2.
After installing and configuring the Monitoring Server, the Monitoring Central
site can be shown by navigating a browser to http://
:/
central, where the server name is the name of the server running the Monitoring
Server Web Service, and the port number is the port specified during installation (the
default is 40000). Monitoring Central contains only two buttons: the first downloads
and runs Dashboard Designer, while the second takes the user to the Dashboard
Designer Preview Site.
Once Monitoring Server is up and running, it creates two log files in the %temp%
directory. These files are named MonitoringStatus and MonitoringVerbose, and each
has the date appended, as well as an extension of .log. Therefore, the status file for
January 5, 2008, would be MonitoringStatus1-5-2008.log if the system??™s date format
is configured for US English.
Perhaps one of the biggest areas of confusion in PerformancePoint Server is how
connections are made. Most people think that the SharePoint web parts connect to
the Monitoring Server machine, which then connects to the data source.
Pages:
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375