Higgins Configuration Management

Configuration Management

Applications need the ability to manage the run time configuration and persisted configuration files of various Higgins components. This example will focus on IdAS Registry as the use case, but applies to any IConfigurableComponent.

The IdAS registry can be initialized from an XML file through the configuration APIs. The 'IdentityAttributeService' section in the configuration XML file that corresponds to the IdAS registry typically contains the following information:

A section of settings for' . context factories, for e.g.

<Setting Name="ContextFactoryInstancesList" Type="htf:list"> <Setting Name="JNDIContextFactory" Type="htf:map"> <Setting Name="Instance" Type="xsd:string">JNDIContextFactory</Setting> <Setting Name="ContextTypes" Type="htf:list"> <Setting Name="JNDIContextType" Type="xsd:string">$context+ldap</Setting> </Setting> </Setting> </Setting>

A section of settings fhinor the context IDs, for e.g.

<Setting Name="ContextIdsList" Type="htf:list"> <Setting Name="urn:ldap@ltoyota" Type="htf:map"> <Setting Name="ContextId" Type="xsd:string">urn:ldap@ltoyota</Setting> <Setting Name="ContextTypes" Type="htf:list"> <Setting Name="JNDIContextType" Type="xsd:string">$context+ldap</Setting> </Setting> <Setting Name="Connection" Type="htf:map"> <Setting Name="Address" Type="xsd:string">ldap://ltoyota:389</Setting> <Setting Name="SearchBase" Type="xsd:string">o=Higgins</Setting> </Setting> </Setting> </Setting> </Setting>

Following APIs exist to update the IdASRegistry: registerContextFactory removeContextFactory registerContextId removeContextId

All the above APIs currently update only the in-memory data-structures corresponding to the list of context factories and contextIds. There is no mechanism to persist updates through these APIs to the configuration XML file.

Proposal 1: ISettingDescriptors

Add description

Proposal 2: ISetting

The other desription