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

MSP 3.2.1Facts:, High Availability and Distributed System Configurations

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

Chapter 6 - Architecture Overview and Custom Installation Planning 39 • Will all of the machines involved in your MSP system reside on the same Active Directory domain? • Do you intend to use SQL Authentication or Windows Authentication for your installation connection to the Database Engine? • Do you intend to use SQL Authentication or Windows Authentication for your runtime connection to the Database Engine? • Will the server acting as the MSP Application server be a dedicated machine, or will it be running other applications as well? MSP 3.2.1Facts: • Once MSP has been installed, the database cannot be migrated to another server without re-installation. Also, 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 change 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. • SQL Server 2005 Analysis Services (SSAS) IS required if you ever plan to use integrated Collection Analysis. Alternatively, if you will never need the integrated Analysis feature provided by MSP, SSAS is not required. If you choose not to use SSAS and Analysis but later change your mind and decide you will, you will have to reinstall MSP. • If you will be using the Analysis Services component and it will be installed on a different server than the MSP Web App component, you must use Windows Authentication which requires both machines to be on the same domain. • If you require both data collection and analysis, and your SSAS instance resides on a different server than your SQL Database Engine instance, the two servers will need to be on the same domain. This will also require a special custom setup that is not explicitly described in this document. • If your installation scenario involves more than one server, you will need to run the installer on each separate server. The one exception to this is if you are installing to a remote SQL Database Engine and you are NOT using Analysis. The Common Installation Scenarios section that follows discusses different potential installation scenarios. While there are many possible variations, a few of the most common types are highlighted. It's critical that you decide upon the required MSP components needed for the features you intend to use and that you have a clear understanding of the installation scenario you plan to use. To help facilitate the setup process that takes place as the installer application is run, we have split the common setup scenarios into two types, the Typical (or Simple) setup type and the Custom (or Complex) setup type. It is imperative that the decision on setup type that you intend to use is made long before the installation program is run. High Availability and Distributed System Configurations It is also important to mention that MSP provides the ability to create systems configured in High Availability (H.A.) type setup and other complex Distributed installations. The setup and configuration details of these types of systems are not covered by this document but it is worth noting the reasons and benefits for creating such systems. It will have to suffice that such methods exist and that extensive knowledge of the installation environment and each component would be required to attempt such an installation.

  • 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
Chapter 6 – Architecture Overview and Custom Installation Planning
39
•
Will all of the machines involved in your MSP system reside on the same Active Directory
domain?
•
Do you intend to use SQL Authentication or Windows Authentication for your installation
connection to the Database Engine?
•
Do you intend to use SQL Authentication or Windows Authentication for your runtime
connection to the Database Engine?
•
Will the server acting as the MSP Application server be a dedicated machine, or will it be
running other applications as well?
MSP 3.2.1Facts:
•
Once MSP has been installed, the database cannot be migrated to another server
without re-installation. Also, 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 change 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.
•
SQL Server 2005 Analysis Services (SSAS) IS required if you ever plan to use integrated
Collection Analysis. Alternatively, if you will never need the integrated Analysis feature
provided by MSP, SSAS is not required. If you choose not to use SSAS and Analysis but
later change your mind and decide you will, you will have to reinstall MSP.
•
If you will be using the Analysis Services component and it will be installed on a different
server than the MSP Web App component, you must use Windows Authentication which
requires both machines to be on the same domain.
•
If you require both data collection and analysis, and your SSAS instance resides on a
different server than your SQL Database Engine instance, the two servers will need to be
on the same domain. This will also require a special custom setup that is not explicitly
described in this document.
•
If your installation scenario involves more than one server, you will need to run the
installer on each separate server. The one exception to this is if you are installing to a
remote SQL Database Engine and you are NOT using Analysis.
The Common Installation Scenarios section that follows discusses different potential installation
scenarios. While there are many possible variations, a few of the most common types are
highlighted. It’s critical that you decide upon the required MSP components needed for the
features you intend to use and that you have a clear understanding of the installation scenario
you plan to use. To help facilitate the setup process that takes place as the installer application is
run, we have split the common setup scenarios into two types, the Typical (or Simple) setup type
and the Custom (or Complex) setup type. It is imperative that the decision on setup type that you
intend to use is made long before the installation program is run.
High Availability and Distributed System Configurations
It is also important to mention that MSP provides the ability to create systems configured in High
Availability (H.A.) type setup and other complex Distributed installations. The setup and
configuration details of these types of systems are not covered by this document but it is worth
noting the reasons and benefits for creating such systems. It will have to suffice that such
methods exist and that extensive knowledge of the installation environment and each component
would be required to attempt such an installation.