The following is a sample portalapp.xml for an editor:
Syntax
<application> <application-config> <property name="releasable" value="false"/> <property name="Vendor" value="sap.com"/> <property name="SecurityArea" value="NetWeaver.Portal"/> <property name="SharingReference" value= "com.sap.portal.admin.wizardframework, com.sap.portal.admin.editorframework, com.sap.portal.htmlb" /> </application-config> <components> <component name="TrainEditor"> <component-config> <property name="ClassName" value="TrainEditor"/> <property name="SafetyLevel" value="low_safety"/> </component-config> <component-profile> <property name= "com.sap.portal.admin.editorframework.dataHandler" value="myEditor.myDataHandler"/> <property name="com.sap.portal.iview.ShowTray" value="false"/> <property name="com.sap.portal.reserved.iview.IsolationMode" value="URL"/> <property name="com.sap.portal.iview.HeightType" value="FULL_PAGE"/> <property name="isStateless" value="false" /> </component-profile> </component> </components> <services> <service name="myDataHandler"> <service-config> <property name="className" value="TrainDataHandler" /> <property name="SafetyLevel" value="medium_safety" /> <property name="startup" value="false" /> </service-config> </service> </services> </application>
In the <application-config> element, add a SharingReference for the following services:
Service/Component |
Sharing Reference |
---|---|
Wizard Framework |
com.sap.portal.admin.wizardframework |
Editor Framework |
com.sap.portal.admin.editorframework |
HTMLB |
com.sap.portal.htmlb |
Syntax
<application-config> <property name="releasable" value="false"/> <property name="Vendor" value="sap.com"/> <property name="SecurityArea" value="NetWeaver.Portal"/> <property name="SharingReference" value= "com.sap.portal.admin.wizardframework, com.sap.portal.admin.editorframework, com.sap.portal.htmlb" /> </application-config>
An editor contains one portal component, the editor component, which is based on a class that extends AbstractEditorComponent. For more information on creating the editor component's <component> element, see Step 2: Creating an Editor Component.
Syntax
<components> <component name="TrainEditor"> <component-config> <property name="ClassName" value="myPackage.TrainEditor"/> <property name="SafetyLevel" value="low_safety"/> </component-config> <component-profile> <property name= "com.sap.portal.admin.editorframework.dataHandler" value="myEditor.myDataHandler"/> <property name="com.sap.portal.iview.ShowTray" value="false"/> <property name="com.sap.portal.reserved.iview.IsolationMode" value="URL"/> <property name="com.sap.portal.iview.HeightType" value="FULL_PAGE"/> <property name="isStateless" value="false" /> </component-profile> </component> </components>
If you want the data handler to be available to editors in other portal applications (PARs), you must expose the data handler as a portal service and list it in the <services> element. The data handler class must implement IService.
If the data handler is exposed as a service, the name of the data handler service - instead of the class - is specified in the com.sap.portal.admin.editorframework.dataHandler property in the <config-profile> section for any editor component that wants to use it, as described in Component Element above.
Syntax
<services> <service name="myDataHandler"> <service-config> <property name="className" value="TrainDataHandler" /> <property name="SafetyLevel" value="medium_safety" /> <property name="startup" value="false" /> </service-config> </service> </services>