Jump to: navigation, search

Orion/Documentation/Developer Guide/Configuration services

< Orion‎ | Documentation‎ | Developer Guide
Revision as of 15:21, 27 August 2012 by Mamacdon.ca.ibm.com (Talk | contribs) (Configuration management)


Orion provides a number of service APIs related to service configuration.

Managed Services

A service may need configuration information before it can perform its intended functionality. Such services are called Managed Services. A Managed Service implements a method, updated(), which is called by the Orion configuration framework to provide configuration data to the service. As with all service methods, updated() is called asynchronously. The configuration data takes the form of a dictionary of key-value pairs, called properties. If no configuration data exists for the Managed Service, null properties are passed.

A Managed Service needs to receive its configuration information before the service is invoked to perform other work. For example, a configurable validation service would want to receive any custom validation options (or null, if no custom options were configured) before actually performing any validation. For this reason, the framework guarantees that a Managed Service's updated() method will be called prior to any other service methods the service may implement.

Managed Services can be contributed by registering against the orion.cm.managedservice service name. Every Managed Service must provide a service property "pid" giving a PID (persistent identifier). The PID uniquely identifies the Managed Service, and serves as a primary key for its configuration information.

The Orion concept of a Managed Service is analogous to the OSGi Managed Service.

Meta Typing

A Metatype describes the shape of configuration data. In other words, it specifies what property names can appear in the properties dictionary, and what data types (string, boolean, number, etc) their values may have. Metatype information is defined in terms of Object Classes, which can be reused. Metatype information is associated with a Managed Service's PID. Metatype information is optional, so not every Managed Service need have Metatype information associated with it.

Metatype information can be contributed by registering a service with the orion.cm.metatype service name.

The Orion concept of a Metatype is analogous to the OSGi Metatype.

Configuration management

Configuration data is managed by a ConfigurationAdmin service, which maintains a database of Configuration objects. The ConfigurationAdmin monitors the service registry and provides configuration data to Managed Services that are registered. Orion's implementation of ConfigurationAdmin persists configuration data to a Preferences Service.

In JavaScript code, configuration information is represented as Configuration objects (refer to "orion.cm.Configuration" in the client API reference for details), which are returned by the ConfigurationAdmin's service methods. Because the ConfigurationAdmin service is currently only accessible to code running in the same window as the service registry, Configuration objects cannot be directly interacted with by external services. Managed Services can only receive configuration information via their updated() method.

Managed Services currently cannot interact with Configurations directly, and can only receive configuration information via their updated() method.

The Orion ConfigurationAdmin service is analogous to the OSGi ConfigurationAdmin.


On top of the basic configuration and metatype APIs, Orion also provides a higher-level Settings API.


The orion.cm.configadmin service, also called ConfigurationAdmin, provides management of configuration information. Internally, the ConfigurationAdmin service is used by the Plugin Settings page to manage the values of settings.

The service methods are:

Returns the Configuration with the given PID from the database. If no such Configuration exists, a new one is created and then returned.
Returns an array of all current Configuration objects from the database.

Refer to orion.cm.ConfigurationAdmin in the client API reference for a full description of this service's API methods.

Here is an example of how to use the ConfigurationAdmin service to print out all existing configurations and their property values:

var configurations = serviceRegistry.getService("orion.cm.configadmin").listConfigurations().then(function(configurations) {
        configurations.forEach(function(configuration) {
            var properties = configuration.getProperties();
            var propertyInfo = Object.keys(properties).map(function(propertyName) {
                if (propertyName !== "pid") {
                    return "\n        " + propertyName + ": " + JSON.stringify(properties[propertyName]) + "\n";
            console.log("Configuration pid: " + configuration.getPid() + "\n"
                      + "  properties: {" + propertyInfo + "\n"
                      + "  }");

The result might look something like this:

Configuration pid: nonnls.config
  properties: {
        enabled: false
Configuration pid: jslint.config
  properties: {
        options: "laxbreak:true, maxerr:50"


Contributes a Managed Service. A Managed Service is a service that can receive configuration data.

A Managed Service must implement the following method:

The ConfigurationAdmin invokes this method to provide configuration to this Managed Service. If no configuration exists for this Managed Service's PID, properties is null. Otherwise, properties is a dictionary containing the service's configuration data.


This minimal example shows the implementation of a plugin which registers a Managed Service under the PID "example.pid". When its updated() method is called, it simply prints out what it received:

define(["orion/plugin"], function(PluginProvider) {
    var provider = new PluginProvider();
        {  pid: "example.pid"
        {  updated: function(properties) {
               if (properties === null) {
                 console.log("We have no properties :(");
               } else {
                 console.log("We got properties!");

Here is a larger example, showing how a validation service (a spellchecker that checks for any occurrences of the misspelling "definately") might accept options through its configuration properties. The service implementation in this example is both a validator and a Managed Service.

define(["orion/plugin"], function(PluginProvider) {
    var provider = new PluginProvider();
    var options;
    provider.registerService(["orion.cm.managedservice", "orion.edit.validator"],
        {  pid: "example.validator",
           contentType: ["text/plain"]
        {  updated: function(properties) {
               if (properties === null) {
                   // No configuration, use default
                   options = { enabled: true };
               } else {
                   options = { enabled: !!properties.enabled };
           checkSyntax: function(title, contents) {
               if (!options.enabled) {
                   return { problems: [] };
               var problems = [];
               contents.split(/\r?\n/).forEach(function(line, i) {
                   var index;
                   if ((index = line.indexOf("definately") !== -1) {
                           reason: "Misspelled word",
                           line: i+1,
                           start: index,
                           end: index+10,
                           severity: "warning"
               return { problems: problems };

The updated() method here checks its configuration dictionary for a boolean enabled property that determines whether the validator is active. In the case of null properties, the service uses a reasonable default. (It's a best practice for configurable services to behave sanely when no configuration has been defined for them.)

Note that, by virtue of the configuration framework's guarantee that updated() is called before all other service methods, our checkSyntax() method can safely assume that the options variable has been set.


Contributes type definitions, which may be associated with a service's configuration.

See also

Plugging into the settings page