The FileOperation Configuration Service Provider manages files and directories on the device. Using the FileOperation Configuration Service Provider, an OEM or Mobile Operator can implement security for files.
Note This Configuration Service Provider is managed over the OMA Client Provisioning (formerly WAP) protocol.
Note Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Roles and Default Roles for Configuration Service Providers.
Characteristics or parameters for the FileOperation Configuration Service Provider contain an additional attribute called "translation" when specifying a parameter or characteristic that contains a file name or directory. The two values for this attribute are "filesystem" and "install". A translation of type "filesystem" causes all file paths to be canonicalized (that is, double backslashes are removed). A translation of type "install" includes all the translations done for "filesystem", but also translates all CE Strings (for example, %CE2%) into the correct file path for the device. Cabwiz will automatically add the appropriate translation to file operations and registry keys in an .inf file.
Note The correct way to help protect a file in the metabase is to use an asterisk (*) at the end of the file path, for example, FileOperation\FileCspRODir\FileCspReadOnlyFile\*. The use of the asterisk helps to apply protection to all nodes under the file name node, and therefore to all file operations.
The following table shows the default settings. The default security role maps to each subnode unless specific permission is granted to the subnode.
|Roles allowed to query and update setting||Manager
The security role for subnodes is implementation specific, and can be changed by OEMs and Mobile Operators. To see the permission granted to specifice subnodes, see Metabase Settings for FileOperation Configuration Service Provider.
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
As these figures show, the FileOperation Configuration node is the root node for all other nodes. This root node is followed by a directory characteristic and, in some cases, a file characteristic. The directory and file characteristic value is the directory or file to perform the action on. Action characteristics and parameters are listed as follows.
The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.
Use these elements to build standard OMA Client Provisioning (formerly WAP) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see Provisioning XML File Examples.
For information about OMA Client Provisioning, see OMA Client Provisioning Files.
Send Feedback on this topic to the authors