Motorola MC3090G Integration Guide - Page 119

Persistent Storage, Application Folder, Symbol Configuration Manager, File Types, User Interface

Page 119 highlights

Application Deployment for Mobile 6.1 5 - 9 Persistent Storage Windows Mobile 6.1 protects all data and applications from power-related loss. Because Windows Mobile 6.1 mounts the entire file system and registry in persistent storage (rather than using RAM), MC3000 devices provide a reliable storage platform even in the absence of battery power. Persistent storage provides application developers with a reliable storage system available through the standard file system and registry APIs. Persistent storage is optimized for large reads and writes; therefore, applications reading and writing data in large chunks tend to outperform those applications reading and writing small blocks of data. Data in persistent storage is lost upon a clean boot. Persistent storage contains all the directories under the root directory except for Application, Cache Disk, and Storage Card (if a storage card is installed). Persistent storage is approximately 60 MB (formatted). Application Folder The Application folder is a super-persistent storage that is persistent even after a clean boot. Accessing data in the Application folder is slower than accessing persistent storage. The Application folder is used for deployment and device-unique data. For example, network profiles can be stored in the Application folder so that connection to the network is available after a cold boot. The Application folder is approximately 20 MB (formatted). Symbol Configuration Manager Symbol Configuration Manager (SCM) is a utility that runs on the development computer and is used to create configuration files. These files, when deployed to an MC3000, set configuration parameters for that device. The configurable options for a MC3000 are defined in an XML file that is available on the Support Central ( http://www.motorola.com/enterprisemobility/support) for that MC3000. SCM is also available on Support Central. SCM eliminates the potential user errors that occur when manually editing registry settings. File Types SCM uses three types of files: • Symbol Configuration Template (.SCT) files are XML files that define the configurable parameters for a device. • Registry Configuration Service Provider XML files for device provisioning. • CAB Provisioning Format (.CPF) file which is a .CAB archive that contains the provisioning XML. This file is downloaded to the MC3000 and merged upon a cold boot. User Interface SCM's user interface consists of a tree control on the left side of the window which displays all the configuration categories, and a data grid table on the right which displays all the configurable controls for the selected category. Figure 5-1 shows the main window for a device's .sct file.

  • 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
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236

Application Deployment for Mobile 6.1
5 - 9
Persistent Storage
Windows Mobile 6.1 protects all data and applications from power-related loss. Because Windows Mobile 6.1
mounts the entire file system and registry in persistent storage (rather than using RAM), MC3000 devices provide a
reliable storage platform even in the absence of battery power.
Persistent storage provides application developers with a reliable storage system available through the standard
file system and registry APIs. Persistent storage is optimized for large reads and writes; therefore, applications
reading and writing data in large chunks tend to outperform those applications reading and writing small blocks of
data. Data in persistent storage is lost upon a clean boot.
Persistent storage contains all the directories under the root directory except for Application, Cache Disk, and
Storage Card (if a storage card is installed). Persistent storage is approximately 60 MB (formatted).
Application Folder
The Application folder is a super-persistent storage that is persistent even after a clean boot. Accessing data in the
Application folder is slower than accessing persistent storage. The Application folder is used for deployment and
device-unique data. For example, network profiles can be stored in the Application folder so that connection to the
network is available after a cold boot. The Application folder is approximately 20 MB (formatted).
Symbol Configuration Manager
Symbol Configuration Manager (SCM) is a utility that runs on the development computer and is used to create
configuration files. These files, when deployed to an MC3000, set configuration parameters for that device. The
configurable options for a MC3000 are defined in an XML file that is available on the Support Central (
) for that MC3000. SCM is also available on Support Central.
SCM eliminates the potential user errors that occur when manually editing registry settings.
File Types
SCM uses three types of files:
Symbol Configuration Template (.SCT) files are XML files that define the configurable parameters for a
device.
Registry Configuration Service Provider XML files for device provisioning.
CAB Provisioning Format (.CPF) file which is a .CAB archive that contains the provisioning XML. This file is
downloaded to the MC3000 and merged upon a cold boot.
User Interface
SCM's user interface consists of a tree control on the left side of the window which displays all the configuration
categories, and a data grid table on the right which displays all the configurable controls for the selected category.
Figure 5-1
shows the main window for a device’s .sct file.