This allows the administrator to change both the server and database name
to conform to any existing standards and allows for the installation of a database
to occur on another server instead of requiring the setup routine to be run on both
servers. Installing the database on a different server requires that the user account
running the installation has administrative privileges on the SQL Server machine
or that the user person performing the installation use the Provision an Existing
Database option. The Provision an Existing Database option allows the database
administrator on the target SQL Server machine to create a blank PPS Monitoring
database. This means that installers of PerformancePoint Server can provision it and
can have their tables created on that centralized SQL Server machine.
The next step in the installation process is to specify the account under which the
Monitoring Server service will run. This is called the Service Identity, or SI, account,
and all Monitoring Server work is done under this SI account. The SI account is used
by the IIS application pool, which is where all the Monitoring Server processes run.
The default is to use the Network Service account, but a good practice is to create a
domain account specifically for PerformancePoint Server. The reason for this is that
the SI account will have to have permissions to Analysis Services cubes, and having
the SI run under Network Service account means granting cube permissions to the
Network Service account, an account under which many other applications may be
running.
Pages:
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373