FileOperation Configuration Service Provider

  • Article

Send Feedback

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.

Permissions Read/Write
Data type String
Roles allowed to query and update setting Manager

Authenticated User

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.

Characteristics

  • Copy
    Copies one file to another file.
  • Delete
    Deletes a file.
  • Directory
    The directory in which to perform the action. For example, this would be the directory in which to make or remove a directory. It can also be the directory that holds the file on which to perform the action.
  • Extract
    Extracts the file specified by the Source parameter from the currently open .cab file. The extracted file is placed in the file name and directory specified by the previous characteristic. The Extract characteristic can only be used in conjunction with a .cab file.
  • File
    The file on which to perform the action. For example, the source file for a move or copy action
  • MakeDir
    This characteristic should appear under any characteristic where the type is a file path ("%CE2%\files", for example). If the directory does not exist, MakeDir ensures that the directory is created.
  • Move
    Moves one file to another name and/or location.
  • RemoveDir
    Removes a directory. This command is only successful if there are no files or subdirectories in this directory.
  • Shortcut
    Creates a shortcut to an executable on the device. Shortcuts should be placed in the appropriate directory in the Start Menu, under the Windows CE Directory Identifier (%CE17%).

Parameters

  • ForceDelete
    This parameter can be used in the Delete characteristic to delete the file even if the shared reference count is not zero.
  • NoOverwrite
    This parameter can be used in the Copy, Move, and Extract characteristics. If the destination file already exists, it is not replaced by this operation.
  • NoOverwriteIfnewer
    This parm can be used in the Copy, Move, and Extract characteristics. If the destination file already exists and is newer than the source file, the destination file is not replaced by this operation.
  • NoTransaction
    This parameter can be used in the MakeDir, RemoveDir, Copy, Move, Extract, and Delete characteristics. If this parameter is set, no backup file is created for this operation. If the operation fails, the original file is not restored. This will also prevent the entry from appearing in the recovery file
  • SelfRegister
    This parameter can be used in the Copy, Move, and Extract characteristics to indicate that this file is a self-registering COM server. The installation routine attempts to call DLLRegisterServer in that DLL. If this is used together with Delete, the DllUnregisterServer is called.
  • Shared
    This parameter can be used in the Copy, Move, and Extract characteristics to indicate that this file is a shared component and updates the reference count. On uninstall, the reference count is decremented, and the file is deleted only if the count is zero.
  • Source
    This parameter can be used in the Shortcut, Copy, Extract, and Move characteristics to indicate the file that action will be taken upon. For example, Source indicates the original file in a Copy operation.

Microsoft Custom Elements

The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.

Elements Available
parm-query No
noparm No
nocharacteristic No
characteristic-query No

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.

See Also

Configuration Service Provider Reference for Windows Mobile-Based Devices | FileOperation Configuration Service Provider Example for OMA Client Provisioning

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.