Example Custom Installation Scenario - Motorola MSP3-CNTRL-SW-1 - Mobility Services Platform Control Edition Installation Manual

42 Mobility Services Platform 3.2.1 Software Installation Guide
Make sure Microsoft SQL Server 2005 Enterprise or Standard edition is installed on the
database server. (Chapter 7 describes how to upgrade from SQL Server 2005 Express to
SQL Server 2005 Enterprise or Standard edition.)
All servers must be part of the same Domain.
A SQL Server login with 'sysadmin' rights must be present in SQL prior to installation.
This login can use either SQL Authentication or Windows Authentication. This login can
be removed when installation is complete.
Create or select an existing Domain user for use with MSP. The Domain user does not
need to be the member of any special Domain groups. This user will be the MSP runtime
user that is used for authentication.

Example Custom Installation Scenario

Figure 21 depicts an example custom installation scenario. This depiction is the specific scenario
covered by this chapter. The figure shows the two separate machines involved, the pre-requisite
components and the MSP components that correspond with them. The Installer Features column
on the right provides the name of the MSP component associated with each as it appears in the
MSP Installer feature tree itself. The diagram below also uses several example names that will be
referenced by many of the figures throughout this chapter. If at any point during the process of
the install you are unsure as to the meaning of the names used in any screen capture given, you
can refer back to this diagram to understand which SQL or Application Server component is being
referenced.
The PC serving as the Database Server has SQL Server 2005 Standard or Enterprise installed
and for the purposes of this scenario includes both the Database Engine and the Analysis
Services (SSAS). The SQL Server installation contains a single SQL Server instance, named
RemoteInstanceName in which both the Database Service and the SSAS are installed. If the
SSAS component is not required for your installation based on the criteria provided earlier, your
install experience will be slightly different from the one described here. The example name used
to indicate this server is RemoteSQLServer.
The PC serving as the Application Server has IIS and .NET 2.0 installed and for this scenario
assumes that all of the MSP services and User Data files reside on this server as well. Again, if
your setup requirements involve deviations from this, your installation experience will be different
from the steps described here. The example name used to indicate this server is MSPAppPC.
Table 4 – SQL Users and Table 5 – Domain Users list the user accounts referenced throughout
the rest of this chapter. These users are only examples or default names. If your setup requires
different user names, you must make sure they are correctly substituted for these and they have
the correct permissions. If using Windows Authentication for either the installation connection or
the runtime connection, the corresponding SQL user from Table 4 will not be needed. When
running the install on the Application Server you should be logged in as the domain user created
for the install. Both domain users listed in Table 5 must be created prior to beginning the
installation process.
Any installation scenario that involves more than one server machine will require running the
installation on each machine involved. Steps A and B in the Custom Setup Overview demonstrate
this.