As stated before, each provider comes with a configuration module, in the form of a Bonobo component, which is then loaded by the gnomedb-mgr application.
The features provided by these Bonobo components are specific to each implementation, so there is no assumption on what they do, and the gnomedb-mgr tool acts just as a container for them.
The only thing that is assumed about the Bonobo components, is the set of properties they export to the outside world. Thus, a client application (in this case, gnomedb-mgr) can easily affect the behavior of the components. The properties currently supported are:
DSN: specifies the data source string for opening a connection to the underlying database. Note that this string is NOT the GDA name of the data source, BUT the DSN entry in the libgda configuration. The provider, which may be on a different machine, might know nothing about the client's libgda local configuration.
user