Table of Contents
Advertisement
4 - 2
SB1 Integrator Guide
Installation
To install the MSP 4.2 Supplement for SB1 Kit:
NOTE For use only with an MSP Server.
Download the MSP 4.2 Supplement for SB1 Kit from the link provided in the order fulfillment email.
1.
Unzip the file to a location on a host computer.
2.
Install all extracted ZIP files using the MSP Admin Tool.
3.
Template Files
The kit contains template files that are used when creating SB1 application packages using the MSP
Package Builder. SB1 application packages created using the MSP Package Builder and the template files
could then be uploaded to either an MSP 4.2 Server or to RDT, from which they could then be deployed to
SB1 devices. The templates files must be extracted from the kit, copied, and registered with the MSP
Package Builder before they can be used within the MSP Package Builder to create SB1 application
packages. The MSP Package Builder must be installed before the template files can be copied or
registered with the MSP Package Builder. See
Staging Using Rapid Deployment Tool on page 4-20
Key SB1 Differences
The following lists key differences between the SB1 and other Motorola Solutions devices that impacts how
MSP operates on the SB1.
Persistent Storage - The SB1 contains a UserDrive folder to store customer-specific content.
Customers can develop Rho-Based applications and deploy them to the UserDrive folder. Customers
can return the behavior of the SB1 Shell to the default state by erasing the content previously deployed
to the UserDrive folder. A cold boot is required after UserDrive folder changes at the end of a bundle.
Reboots - The SB1 supports program-initiated or user-initiated cold boot. Warm boots are not
•
supported. Cold boots cause loss of all content not intentionally stored persistently. An MSP-initiated cold
boot is automatically performed at the end of every update to protect against data loss.
Persistence - Persistence is critical due to automatic cold boot. Content that is part of an update and is
•
not stored persistently is lost when the cold boot is performed at the end of an update. System content is
automatically stored persistently as part of OS Update. User content stored in the UserDrive folder is
persistent. Touch Panel Calibration can be stored persistently using the SB1SaveCalibration package.
Application Support - Only Rho-based applications are supported on the SB1.
•
User Interface - The Rho-based SB1 Shell is the user interface of the SB1.
•
Staging Using Mobility Services Platform on page 4-13
for more information.
and
Advertisement
Table of Contents
