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

instances may or may not be the same. While these types of installations are not common

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

40 Mobility Services Platform 3.2.1 Software Installation Guide In a High Availability configuration, you create a primary application server and at least one secondary application server that you can switch to manually in case of a primary server failure. There is no limit to the number of secondary application servers that can be installed, however, only one can be allowed to run at any given time. Such secondary application server(s) are installed and configured exactly like the primary application server, except, all MSP-related services on the secondary server(s) are inactive. The HA configuration assumes that the Database Server exists in a failsafe, backed-up environment. The end user is responsible for implementing the backup and failover procedures that best suit their needs. In most cases, the HA installation is very similar to the most-common custom installation scenario with a few additional steps. The process of switching from the primary to any secondary server is a manual one; there is currently no way to have MSP switch over automatically if and when the primary server fails. There are a couple important manual steps that would have to be taken to successfully switch over. These are out of the scope of this document. The Distributed System is another type of custom setup scenario. This is also not covered in any significant detail, but should be mentioned that the various components of MSP Server can be distributed over several servers. Distributed systems provide the most benefit when used in very large-scale enterprise deployments with a well-defined IT policy need. One could, for example, dedicate one server to simply run the MSP web application, while the additional seven MSP services could be spread out over two or more additional servers. Another prime example of a distributed system occurs when the SQL Server running the Database Engine resides on a different server than the SQL Server instance running the Analysis Services. Also, the SQL instances may or may not be the same. While these types of installations are not common installation scenarios, MSP is capable of utilizing such configurations and the powerful flexibility they provide. One of the standard benefits of using MSP is that it provides a relatively high degree of scalability using only the minimum published hardware and software requirements. MSP achieves this from a single management server by leveraging the multi-tiered architecture where Relay Servers are used to transfer information to and from devices. Information about the scalability numbers are published in Chapter 1 of the MSP 3.2.1 Users Guide. However, for very large deployments it is also possible to further extend your enterprise scalability using a distributed system described above. It is recommended that you contact Motorola Support in advance if you plan to implement such systems.

  • 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
40
Mobility Services Platform 3.2.1 Software Installation Guide
In a High Availability configuration, you create a primary application server and at least one
secondary application server that you can switch to manually in case of a primary server failure.
There is no limit to the number of secondary application servers that can be installed, however,
only one can be allowed to run at any given time. Such secondary application server(s) are
installed and configured exactly like the primary application server, except, all MSP-related
services on the secondary server(s) are inactive. The HA configuration assumes that the
Database Server exists in a failsafe, backed-up environment. The end user is responsible for
implementing the backup and failover procedures that best suit their needs. In most cases, the
HA installation is very similar to the most-common custom installation scenario with a few
additional steps. The process of switching from the primary to any secondary server is a manual
one; there is currently no way to have MSP switch over automatically if and when the primary
server fails. There are a couple important manual steps that would have to be taken to
successfully switch over. These are out of the scope of this document.
The Distributed System is another type of custom setup scenario. This is also not covered in any
significant detail, but should be mentioned that the various components of MSP Server can be
distributed over several servers. Distributed systems provide the most benefit when used in very
large-scale enterprise deployments with a well-defined IT policy need. One could, for example,
dedicate one server to simply run the MSP web application, while the additional seven MSP
services could be spread out over two or more additional servers. Another prime example of a
distributed system occurs when the SQL Server running the Database Engine resides on a
different server than the SQL Server instance running the Analysis Services. Also, the SQL
instances may or may not be the same. While these types of installations are not common
installation scenarios, MSP is capable of utilizing such configurations and the powerful flexibility
they provide.
One of the standard benefits of using MSP is that it provides a relatively high degree of scalability
using only the minimum published hardware and software requirements. MSP achieves this from
a single management server by leveraging the multi-tiered architecture where Relay Servers are
used to transfer information to and from devices. Information about the scalability numbers are
published in Chapter 1 of the MSP 3.2.1 Users Guide. However, for very large deployments it is
also possible to further extend your enterprise scalability using a distributed system described
above. It is recommended that you contact Motorola Support in advance if you plan to implement
such systems.