Configmgr Refactoring/Design
Please view Configmgr Refactoring about analysis. This document explain configmgr new design and some discuss only .
Contents
Processing flow
[[Image:|thumb|===== processing flow =====]]
We can divid configuration data processing into two phases:
OOo Packaging
Using tools and scripts, merger configuration files from sources to default configuration files which will be instaled into “$BaseInstallation/share/registry/”(as admin configuration file). The result files can be XML file or binary file. Two tools (configmgr_tools /configmgr_converter ) and some scripts files be used in this phase .
Here have three steps:
(1) Merger .xcu files and .xcs files and .sdf into new schema configuration files.
(2) Replace some values in configuration files and do other procesings.
(3) Converter XML format configuration files in to binary configuration files.
OOo Running
Other module of OOo access and process the configuration data through the services of configmgr module.
The relationship of new schema nodes in OOo running
New schema use OOo schema as standard, and adjust some places .
Node
compoents:
component:
component-data:
templates:
set:
group :
prop:
user-value:
default-value:
Attribute
package:
component:
node-type:
inserted:
removed:
extensible:
name:
readlnly:
nillable:
separator:
type:
additional:
[[Image:]]
Please note the inserted/removed attributes and user-value/default-value nodes ; and it will be describe below.
The configuration files placement after OOo install
It is same as the currently OOo implementation, and has some adjustment in some places.
It has two main directories too :
Default configuration directory ($BaseInstallation/share/registry/) 。
User configuration directory ($UserInstallation/user/registry) 。