Creating Configuration Archive

Procedure

Place your configuration files in folders as follows:

·        Data files: <project root>/config/data/<plugin name>

·        Metafiles: <project root>/config/meta/<plugin name>

·        The plug-in name should be the name of the PAR file

·        The names of the directory must match properly under meta and data

·        From a configuration perspective, the plug-in name, more precisely the directory in which the configuration is stored (meta as well as data, in this case: com.sap.portal.prt.config.prototype), is called the Root-Plugin. This is import for ConfigRootFolder considerations.

Configuration Archive Properties File

CA Properties	Manifest	Mandatory	Default
ca.name	CA-Name	No	Project name
ca.version	CA-Version	Yes
ca.dependencies	CA-Dependencies	No
ca.creation.time	CA-Creation-Time	No	Time
ca.creation.date	CA-Creation-Date	No	Date
ca.creation.user	CA-Creation-User	No	User name
ca.creation.machine	CA-Creation-Machine	No	Machine name
cma.name	CMA-Name	No	Project name
cma.version	CMA-Version	Yes
cma.dependencies	CMA-Dependencies	No
cma.storage	CMA-Storage	Yes	The possible values are: ·        sfs ·        pcd
cma.creation.time	CMA-Creation-Time	No	Time
cma.creation.date	CMA-Creation-Date	No	Date
cma.creation.user	CMA-Creation-User	No	User name
cma.creation.machine	CMA-Creation-Machine	No	Machine name

 

The plug-in will automatically use the default value if non-mandatory values are specified as shown:

ca.name=com.sap.portal.prt.config.prototype ca.version=6.0.1.1   cma.name=com.sap.portal.prt.config.prototype.hello cma.version=6.0.1.1 cma.storage=pcd

You can display the configuration of a portal component by executing the component in config mode. This is achieved by adding /prtmode/config/ at the end of the prtroot URL. The system configuration delegate will open the configuration framework user interface. The user interface displays the configuration starting at the root folder of the component.