Entering content frame

Procedure documentation Accessing Data Locate the document in its SAP Library structure

Procedure

...

       1.      Modify portalapp.xml

To access the Config Framework APIs you need to specify a Private Sharing Reference in portalapp.xml:

<application-config>
  <property name="PrivateSharingReference" value="com.sap.portal.runtime.config"/>
</application-config>

Note that 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. You just need the dependency on the Configuration Framework service in order to access the APIs.

For your component you can specify what is called the 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 take the name of the application by default.

<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>

       2.      Virtual components

If you want to configure a portal service, you can create a virtual portal component while giving it the right ConfigRootFolder.

The virtual portal component will use the delegate component to the config mode. In order to use it, you have to add the follow lines in the portalapp.xml:

<application-config>
  <property name="PrivateSharingReference" value="com.sap.portal.runtime.config,
    com.sap.portal.runtime.system.hooks"/>
</application-config>

Then you can easily create your virtual portal component. Note that here we specify the subfolder font of the plug-in com.sap.portal.runtime.config.prototype as ConfigRootFolder.

<component name="FontConfiguration">
  <component-config>
    <property name="ClassName" value="com.sapportals.portal.prt.component.ConfigComponent"/> 
  </component-config>
  <component-profile>
    <property name="ConfigRootFolder" value="/com.sap.portal.runtime.config.prototype/font"/>
  </component-profile>
</component>

This graphic is explained in the accompanying text

If the Root-Plugin name is not the same as the application name, the ConfigRootFolder has to match the Root-Plugin.

 

 

Leaving content frame