Preferences

Preferences are the standard mechanism for configuring applications. Use the Preferences option to manage operation-level configuration data such as timeouts, retries for communicating with other systems, and thread pool sizes.

You can add applications and preference nodes. You can import the node information from an XML file, which contains the application name, path of the node, and preference keys and values. When you import data, it is added to the node path that is defined in the XML file.

• Applications
  You can define preferences for multiple applications, each with a unique name and access rights. An application must have a unique name, and may optionally have a description. You can define read and write privileges for an application. If you do not define read or write privileges, any user who invokes the application services can retrieve or set preference values. You can edit or remove applications.
• Node and System Preferences
  Preference nodes store system preferences and configuration data. Each system preference contains a key-value pair that is associated with a preference path. You can add or remove a preference node, but you cannot edit them. You can export node information to an XML file, which includes the application name, path of the node, and preference keys and values.
• Adding a Preference Node
  You can add a preference node, which requires the application name and full node path. If the node does not exist, you must add it using the full node path and then add the configuration data. You can remove preference nodes, but you cannot edit them.