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

Questions for Consideration:

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

38 Mobility Services Platform 3.2.1 Software Installation Guide the data collection feature including analysis or neither of them. However, a major difference in MSP 3.2.1 is that you can now choose to utilize the data collection feature without using the analysis feature. This is a significant change and has important implications on your setup scenario decisions. It is now the case that you need NOT have SSAS installed on your SQL Server instance if you only want Data Collection without analysis. However, note that the SQL Server Express edition is still not supported for Data Collection in MSP 3.2.1. The third recommendation applies only if you have installed the MSP Package Builder 1.0 add-on for your previous MSP 3.2.0 installation. You must always make sure to uninstall the Package Builder application first and then uninstall the MSP application only after you have removed Package Builder. Beginning with MSP 3.2.1, if you attempt to remove MSP before Package Builder, it will not complete and will give a message indicating that you must remove Package Builder first. Motorola also strongly recommends that you plan your system so that it does not need to be modified in the future. While there will frequently be unknowns that cannot be avoided you should make every effort to account for future naming conventions of authentication users, connection strings, machine names, and the like. The MSP installer assumes that things like the connection users and computer names will NOT change some time in the future after MSP has been installed. This includes migrating the database. Once the MSP database has been installed it cannot be moved to another server or SQL instance. Modifying user permissions or other aspects of MSP that were configured during time of install will significantly increase the chances of negatively affecting the correct functionality of your MSP system. The final recommendation is that you should plan a regular backup procedure for you system once it is installed. Backup and failsafe preparations depend on your individual enterprise policies but should be comprehensive. Consider the vulnerability of each component involved and ensure regular backups or other failsafe precautions are in place. The following questions and fact statements will help you further understand your setup scenario needs. These are presented to introduce certain requirement criteria that affect your installation decisions. If you don't fully understand the significance of these questions and statements, they will be discussed in greater detail throughout this introductory chapter and in following chapters. For further clarification, you should consider these questions as you plan your specific installation scenario. Questions for Consideration: • Do you plan to use the Control Edition features of MSP 3.2.1? • Will you require the Data Collection feature? • Will you require the integrated Collection Analysis feature? • Will your MSP Web Application reside on the same machine as your SQL Server installation? • How many different servers will be used in your installation scenario? • Do you plan to use an existing SQL Server installation? • Do you currently use a dedicated machine or cluster for the SQL Server, or will you be installing SQL specifically for MSP to use? • Does your SQL Server installation currently have SQL Server Analysis Services (SSAS) installed? • If you require SSAS, will it be installed on the same machine as your SQL Database Engine?

  • 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
38
Mobility Services Platform 3.2.1 Software Installation Guide
the data collection feature including analysis or neither of them. However, a major difference in
MSP 3.2.1 is that you can now choose to utilize the data collection feature without using the
analysis feature. This is a significant change and has important implications on your setup
scenario decisions. It is now the case that you need NOT have SSAS installed on your SQL
Server instance if you only want Data Collection without analysis. However, note that the SQL
Server Express edition is still not supported for Data Collection in MSP 3.2.1.
The third recommendation applies only if you have installed the MSP Package Builder 1.0 add-on
for your previous MSP 3.2.0 installation. You must always make sure to uninstall the Package
Builder application first and then uninstall the MSP application only after you have removed
Package Builder. Beginning with MSP 3.2.1, if you attempt to remove MSP before Package
Builder, it will not complete and will give a message indicating that you must remove Package
Builder first.
Motorola also strongly recommends that you plan your system so that it does not need to be
modified in the future. While there will frequently be unknowns that cannot be avoided you should
make every effort to account for future naming conventions of authentication users, connection
strings, machine names, and the like. The MSP installer assumes that things like the connection
users and computer names will NOT change some time in the future after MSP has been
installed. This includes migrating the database. Once the MSP database has been installed it
cannot be moved to another server or SQL instance. Modifying user permissions or other aspects
of MSP that were configured during time of install will significantly increase the chances of
negatively affecting the correct functionality of your MSP system.
The final recommendation is that you should plan a regular backup procedure for you system
once it is installed. Backup and failsafe preparations depend on your individual enterprise policies
but should be comprehensive. Consider the vulnerability of each component involved and ensure
regular backups or other failsafe precautions are in place.
The following questions and fact statements will help you further understand your setup scenario
needs. These are presented to introduce certain requirement criteria that affect your installation
decisions. If you don’t fully understand the significance of these questions and statements, they
will be discussed in greater detail throughout this introductory chapter and in following chapters.
For further clarification, you should consider these questions as you plan your specific installation
scenario.
Questions for Consideration:
•
Do you plan to use the Control Edition features of MSP 3.2.1?
•
Will you require the Data Collection feature?
•
Will you require the integrated Collection Analysis feature?
•
Will your MSP Web Application reside on the same machine as your SQL Server
installation?
•
How many different servers will be used in your installation scenario?
•
Do you plan to use an existing SQL Server installation?
•
Do you currently use a dedicated machine or cluster for the SQL Server, or will you be
installing SQL specifically for MSP to use?
•
Does your SQL Server installation currently have SQL Server Analysis Services (SSAS)
installed?
•
If you require SSAS, will it be installed on the same machine as your SQL Database
Engine?