Motorola MSP3-CNTRL-SW-1 Installation Guide - Page 12

Custom Setup, Things to Consider Before Installing

Get Motorola MSP3-CNTRL-SW-1 - Mobility Services Platform Control Edition PDF manuals and user guides View all Motorola MSP3-CNTRL-SW-1 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

6 Mobility Services Platform 3.2.1 Software Installation Guide There is one exception to the above list of configuration requirements that is still supported by the typical setup type option. • The MSP Core Database (SQL database) can be remotely installed to an instance of SQL Server 2005 that is installed on a separate server. The runtime connection must be able to use SQL Authentication and SQL Server Analysis Services are not installed as part of that instance.This configuration will not install the Analysis Database component and therefore will not support integrated analysis. Custom Setup If the desired installation configuration does not meet the above requirements, the custom setup type option must be used when installing MSP. This includes the following requirements: • Windows Authentication is required for runtime connections. • SQL Server Analysis Services is on a separate server than the MSP Server components. The custom setup type option allows configuration of the following: • Configuration of MSP Web Application and MSP Services to run as a domain user to allow Windows Authentication to SQL Server 2005. • Specifying a different name to use for the MSP catalog. • Creating a non-default SQL Authentication user if Windows authentication is not being used. • Specify a different SQL Server instance to use for the Analysis Database. • Installing a redundant MSP Server for high availability configurations. • Distributing MSP Server components across on multiple servers. Things to Consider Before Installing • In MSP 3.2.1 the package files and plug-in definition documents are now stored in the database. (For more details see Chapter 6 - Architecture Overview and Installation Planning) • If multiple servers are being used, then they must be members of the same domain or trusted domains. • The file system permissions, usernames and passwords used by MSP, database connection string properties, and any other configuration property set during install should NOT be changed after the MSP installation completes. • SQL Server 2005 Express is not supported for use with MSP if Data Collection is required. You will need SQL Server 2005 Standard or Enterprise if you ever plan to use Data Collection or Data Collection WITH integrated Analysis. • MSP configuration items and permissions set during install can easily be changed by uninstalling MSP and reinstalling. When you uninstall and choose to not delete user data, the key information is not lost. You can simply reinstall and alter the configuration options as needed.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
6
Mobility Services Platform 3.2.1 Software Installation Guide
There is one exception to the above list of configuration requirements that is still supported by the
typical setup type option.
•
The MSP Core Database (SQL database) can be remotely installed to an instance of
SQL Server 2005 that is installed on a separate server.
The runtime connection must be
able to use SQL Authentication and SQL Server Analysis Services are not installed as
part of that instance.This configuration will not install the Analysis Database component
and therefore will not support integrated analysis.
Custom Setup
If the desired installation configuration does not meet the above requirements, the custom setup
type option must be used when installing MSP.
This includes the following requirements:
•
Windows Authentication is required for runtime connections.
•
SQL Server Analysis Services is on a separate server than the MSP Server components.
The custom setup type option allows configuration of the following:
•
Configuration of MSP Web Application and MSP Services to run as a domain user to
allow Windows Authentication to SQL Server 2005.
•
Specifying a different name to use for the MSP catalog.
•
Creating a non-default SQL Authentication user if Windows authentication is not being
used.
•
Specify a different SQL Server instance to use for the Analysis Database.
•
Installing a redundant MSP Server for high availability configurations.
•
Distributing MSP Server components across on multiple servers.
Things to Consider Before Installing
•
In MSP 3.2.1 the package files and plug-in definition documents are now stored in the
database. (For more details see Chapter 6 – Architecture Overview and Installation
Planning)
•
If multiple servers are being used, then they must be members of the same domain or
trusted domains.
•
The file system permissions, usernames and passwords used by MSP, database
connection string properties, and any other configuration property set during install
should NOT be changed after the MSP installation completes.
•
SQL Server 2005 Express is not supported for use with MSP if Data Collection is
required. You will need SQL Server 2005 Standard or Enterprise if you ever plan to use
Data Collection or Data Collection WITH integrated Analysis.
•
MSP configuration items and permissions set during install can easily be changed by
uninstalling MSP and reinstalling.
When you uninstall and choose to not delete user
data, the key information is not lost.
You can simply reinstall and alter the configuration
options as needed.