Configuration in an iView

 

This describes how to use the Configuration Framework to handle the configuration of a portal application.

The Configuration Framework provides API to read and write your configuration, as well as a dedicated user interface to maintain this configuration.

The Configuration Framework also provides an event mechanism so that the application can be notified when the configuration has changed.

The configuration of an application can be administered via the general Configuration iView or via the iViews of the portal application. If you wish to have some configuration data for a service, you can administer it by using a virtual configuration component (we will come back to that later).

Once an iView has been defined for your portal application, you can configure it by switching to the config mode. Either there is a specific button for that (directly in the portal) or you can add "/prtmode/config/" at the end of the page URL.

Applications com.sap.portal.runtime.config and com.sap.portal.runtime.config.component must have been deployed in the portal. But as they are part of the irj.ear this should be the case all the time so you should not worry about that.

You should have a complete structure of Configuration Framework (config class, configurable, bundles and properties files).

For more information, see the document on meta-data from the Configuration Framework.