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

configuration consideration during installation but is worth mentioning in the discussion of

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 42 highlights

36 Mobility Services Platform 3.2.1 Software Installation Guide required if the MSP Analysis database is used (see connection 6 in Figure 20). This database would be required only if the integrated Analysis feature of MSP is needed. If this feature is not needed, then SQL Server Analysis Services is not needed and the Analysis database will obviously not be used. However, if the integrated Analysis feature is required, the Web Application must connect to the MSP Analysis Database and the only supported connection authentication type is Windows Authentication. This means that if these two components do not reside on the same physical machine, a common domain user must be used to authenticate over this connection. This requires them both to be members of the same domain. Chapter 6 describes an example of this. The MSP Services also require a few important connections to the components shown in Figure 20. Like the MSP Web Application, each of the seven MSP Services also must have file system access to the MSP Files (see connection 4 in Figure 20). In most installations this is not a problem due to the fact that the MSP Services are commonly installed on the same server as these files. The second important connection the MSP Services require is to the MSP Core Database (see connection 5 in Figure 20). This connection is imperative to the submission and retrieval of data from the MSP Web Application to the MSP database in SQL. This actually uses two possibly different connections. One must be used during the installation process to install the database and the other is used as the runtime connection once MSP has completed installation and is running. Chapter 6 describes the difference between these two connections. The supported authentication types for this connection are SQL Authentication or Windows Authentication. The third connection the MSP Services use is a conditional one. This connection is required ONLY if the MSP Analysis database is used (see connection 7 in Figure 20). This database would only be required if the integrated Analysis feature of MSP is needed. If this feature is not needed then SQL Server Analysis Services is not needed and the Analysis database will obviously not be used. However, if the integrated Analysis feature is required, the Services must connect to the MSP Analysis Database and the only supported connection authentication type is Windows Authentication. This means that if these two components do not reside on the same physical machine, a common domain user must be used to authenticate over this connection. This requires them both to be members of the same domain. Chapter 6 describes an example of this. The MSP Services must also be able to connect via FTP to the FTP Servers that will be used to deliver and collect information to Relay Servers for devices. This does not require any special configuration consideration during installation but is worth mentioning in the discussion of the overall architecture of the system. Finally, the last possible connection that will be needed involves the connection between the MSP Analysis Database (including the MSP Cube) and the MSP Core Database (see connection 8 in Figure 20). Once again, this connection is a conditional one and would only be needed if the Analysis database is needed for the integrated analysis. This is the same runtime connection string that the MSP Web Application and MSP Services use to connect to the MSP Core Database. If SQL authentication is used, no special consideration is required. However if Windows Authentication is used, the Analysis Database, needs to be configured to impersonate the domain user for the connection. As you may conclude from looking at Figure 19 and Figure 20, it is possible to create complex distributed systems out of the MSP components which involve several interconnected machines. The benefits of these complex types of setup are described later on. Experienced users may even be able to derive the knowledge needed to successfully create and use such systems. However, due to the fact that these are not common scenarios we do not cover the details of installing such systems in this document.

  • 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
36
Mobility Services Platform 3.2.1 Software Installation Guide
required if the MSP Analysis database is used (see connection 6 in Figure 20). This database
would be required only if the integrated Analysis feature of MSP is needed. If this feature is not
needed, then SQL Server Analysis Services is not needed and the Analysis database will
obviously not be used. However, if the integrated Analysis feature is required, the Web
Application must connect to the MSP Analysis Database and the only supported connection
authentication type is Windows Authentication. This means that if these two components do not
reside on the same physical machine, a common domain user must be used to authenticate over
this connection. This requires them both to be members of the same domain. Chapter 6
describes an example of this.
The MSP Services also require a few important connections to the components shown in Figure
20. Like the MSP Web Application, each of the seven MSP Services also must have file system
access to the MSP Files (see connection 4 in Figure 20). In most installations this is not a
problem due to the fact that the MSP Services are commonly installed on the same server as
these files.
The second important connection the MSP Services require is to the MSP Core Database (see
connection 5 in Figure 20). This connection is imperative to the submission and retrieval of data
from the MSP Web Application to the MSP database in SQL. This actually uses two possibly
different connections. One must be used during the installation process to install the database
and the other is used as the runtime connection once MSP has completed installation and is
running. Chapter 6 describes the difference between these two connections. The supported
authentication types for this connection are SQL Authentication or Windows Authentication.
The third connection the MSP Services use is a conditional one. This connection is required
ONLY if the MSP Analysis database is used (see connection 7 in Figure 20). This database
would only be required if the integrated Analysis feature of MSP is needed. If this feature is not
needed then SQL Server Analysis Services is not needed and the Analysis database will
obviously not be used. However, if the integrated Analysis feature is required, the Services must
connect to the MSP Analysis Database and the only supported connection authentication type is
Windows Authentication. This means that if these two components do not reside on the same
physical machine, a common domain user must be used to authenticate over this connection.
This requires them both to be members of the same domain. Chapter 6 describes an example of
this.
The MSP Services must also be able to connect via FTP to the FTP Servers that will be used to
deliver and collect information to Relay Servers for devices. This does not require any special
configuration consideration during installation but is worth mentioning in the discussion of the
overall architecture of the system.
Finally, the last possible connection that will be needed involves the connection between the MSP
Analysis Database (including the MSP Cube) and the MSP Core Database (see connection 8 in
Figure 20). Once again, this connection is a conditional one and would only be needed if the
Analysis database is needed for the integrated analysis. This is the same runtime connection
string that the MSP Web Application and MSP Services use to connect to the MSP Core
Database.
If SQL authentication is used, no special consideration is required.
However if
Windows Authentication is used, the Analysis Database, needs to be configured to impersonate
the domain user for the connection.
As you may conclude from looking at Figure 19 and Figure 20, it is possible to create complex
distributed systems out of the MSP components which involve several interconnected machines.
The benefits of these complex types of setup are described later on. Experienced users may
even be able to derive the knowledge needed to successfully create and use such systems.
However, due to the fact that these are not common scenarios we do not cover the details of
installing such systems in this document.