Creating a Config Archive 
1. Place your configuration files in folders:
¡ Data files: <project root>/src.config/install/data/<plugin name>
¡ Meta files: <project root>/src.config/install/meta/expanded/<plugin name>
¡ The plug-in name should be the name of your PAR file
¡ Make sure that the names of the directory match properly under meta/expanded 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
2. Use Export PAR File Wizard
The deployment unit of the configuration is called the Config Archive. It contains the configurables as they were on the file system and it gathers all the config in a Config Meta Archive.
The Export PAR File Wizard, enables you to build the Meta Config Archive and the Config Archive transparently. The Config Archive will be copied in <root project>/dist/PORTAL-INF/config folder. As a consequence it will be packaged automatically in the PAR file and it will be deployed when the PAR is uploaded by the PAR tool.
In order to build the Config Archive (and its Config Meta Archive) properly, you need to provide information in a specific file called configArchive.properties, placed at the root of the config folder.
3. Config Archive properties file
If you have not specified a non-mandatory value, the plug-in places automatically the default value.
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
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 Properties |
Manifest |
Mandatory |
Default |
cma.name |
CMA-Name |
No |
Project name |
cma.version |
CMA-Version |
Yes |
|
cma.dependencies |
CMA-Dependencies |
No |
|
cma.storage |
CMA-Storage |
Yes |
Possible values: 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 |
...
1. Mapping to force install value
If you want to force the update of your configurables when you export a PAR file, you can add this property in the configArchive.properties file:
force.install.value=true
2. Skip archive construction
If you do not want to create the Config archive each time you create a PAR file with the Export PAR File Wizard, you can add this property in the configArchive.properties file:
skip.archive.construction=true