Motorola Mobility Services Platform 3.2.1, Руководство по установке, Страница: 41 / 72

Chapter 6 – Architecture Overview and Custom Installation Planning
35
Figure 20
In Figure 20 each of the major components of MSP are represented by a circular region. This is
intended to be a component-wise overview that is independent of the particular server machine
on which each is actually installed. Installation scenarios range from the simplest case where all
components are installed on the same server to more complex scenarios where each is on a
different server. The point is that as long as the necessary components exist and the integrity of
the connections between them remains constant, the system will function correctly as a whole.
The arrowed lines indicate the usage connection between two component modules. In other
words, the first module “connects to” the second module and uses the information obtained from
it to do work. It also can be thought of in terms of the first one depending on the second one for
some information. The Console UI component, for example, connects to the MSP Web
Application service using an http or https protocol to retrieve the information for a particular page
to display (see connection 1 in Figure 20). While the Console UI is dependent upon the MSP Web
Application for this information, at the same time the Web Application is dependent upon the MSP
Core database for its information. From Figure 20, you can start to see how the components
interact to exchange information. You can also start to get an idea of what connection properties
and user permissions might be required for each connection.
The MSP Web Application requires several important connections starting with the MSP Files
(see connection 2 in Figure 20). The MSP Files component consists of both application program
“bin” files and temporary file folders used by the MSP Application They also contain a special
Archives folder which holds a backup of all Packages stored in your MSP database. None of
these folders contain irreplaceable data but the folder structure must remain in tact. In most
scenarios, these MSP Files reside in the \Motorola MSP directory on the same machine as the
MSP Web Application.
The second important connection the MSP Web Application requires is to the MSP Core
Database (see connection 3 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 illustrates the difference between these two connections. The
supported authentication types for this connection are SQL Authentication or Windows
Authentication.
The third connection the MSP Web Application uses is conditional. This connection is ONLY