Skip to Content
0
Sep 26, 2005 at 12:27 PM

Creating a Config Archive

28 Views

In the sample project about implementing a Simple Repository Manager, the configurables and the configuration classes are respectively placed in the paths:

- SimpleRepositoryManager/src.config/install/data<b>/cm/repository_managers</b>/simple.co.xml

- SimpleRepositoryManager/src.config/install/meta/expanded<b>/cm/repository_managers</b>/com.sap.bc.rf.manager.SimpleRepositoryManager.cc.xml

Similarly, in the sample project about integrating a 3rd party search index into KM, they are in:

- SimpleRepositoryManager/src.config/install/data<b>/cm/services/index_services</b>/customer_search.co.xml

- SimpleRepositoryManager/src.config/install/meta/expanded<b>/cm/services/indexes</b>/CustomerSearchIndexService.cc.xml

- SimpleRepositoryManager/src.config/install/meta/expanded<b>/cm/services/index_services</b>/CustomerIndex.cc.xml

In <i>Creating a Config Archive</i> in the PDK documentation, I read that a path like <b>/cm/repository_managers</b>, <b>/cm/services/index_services</b> or <b>/cm/services/indexes</b> is called the <i>Root-Plugin</i> and represents the path <u>within the overall configuration structure</u> of a component's specific configuration.

Where can I learn more about this overall configuration structure of the Configuration Framework?

In the referenced doc, I also read that the <i>Config Meta Archive</i>'s <u>cma.storage</u> property can be set either to <u>pcd</u> or <u>sfs</u>. Ok, <u>pcd</u> stands for Portal Content Directory, but what is <u>sfs</u>, maybe the server file system?

Thanks a lot, Davide