!--a11y-->
Modifying
portalapp.xmlThe configuration of an application can be administered via the general configuration user interface, or via the Config mode of the portal application. Configuration data for a service can be administered by using a virtual configuration component.
To access the Config framework APIs, the portal application needs to specify a private sharing reference in portalapp.xml:
<application-config> <property name="PrivateSharingReference value="com.sap.portal.runtime.config"/> </application-config> |

Although the Config mode will use the Config framework component to display the configuration, the application itself does not need a direct dependency on the Config component. It just needs the dependency on the configuration framework service in order to access the APIs.
A portal component can also specify a property called ConfigRootFolder. This represents the path within the overall configuration structure of your component-specific configuration. If no ConfigRootFolder info has been specified, the Config component will use the name of the application as a default (the name of the PAR file).
<component name="HelloWorld"> <component-config> <property name="ClassName" value="com.sap.portal.prt.config.HelloWorld"/> </component-config> <component-profile> <property name="ConfigRootFolder" value="/com.sap.portal.prt.config.prototype"/> </component-profile> </component> |
See also:
·
Structure of the
portalapp.xml
