The client platform includes an implementation of the OSGi ConfigurationAdmin service. The ConfigurationAdmin service provides a mechanism for configuration information for a service.
The ConfigurationAdmin service uses the OSGi Preferences mechanism for storage of this information. Because the OSGi Preferences mechanism uses the bundle number of the ConfigurationAdmin service to store user information, if the bundle number changes, the ConfigurationAdmin definitions will no longer be accessible. Operations such as starting the platform with the –clean
option can cause bundles to be re-numbered.
How are user definitions created?
ConfigurationAdmin settings are primarily created through code. In addition, you can use the Admin Utility for OSGi to create user definitions.
How can ConfigurationAdmin settings be changed after deployment?
You can query ConfigurationAdmin settings after deployment using the preferences jobs supplied by the Client Management server. Configuration settings are located at /configuration/org.eclipse.core.runtime.preferences.OSGiPreferences.xx
is the bundle number of the ConfigurationAdmin bundle (com.ibm.osg.service.cm). See Getting an inventory of Eclipse preferences
for more information.
Use the following mechanisms to add, update, or delete user settings
Since the storage mechanism contains some referential aspects, if the ConfigurationAdmin bundle has not already created any settings, it is not recommended that you create a new ConfigurationAdmin preferences tree for the plug-in, but that you only modify values for the existing tree. Changes to ConfigurationAdmin settings may not be available until the next platform restart.
Parent topic: Managing client configurations