Show TOC

System TemplateLocate this document in the navigation structure

Use

In addition to the Java implementation tasks for writing a connector, a system template for the specific EIS must be defined in a portalapp.xml file and deployed as a portal archive in the SAP NetWeaver Portal.

To create a portalapp.xml, create a portal application without components or services in Java. The application will contain only one portal component, which will represent a portal system object whose properties represent a the connection specification to the EIS.

Within the portalapp.xml, the system definition must include the properties in the following illustration:

            <?xml version="1.0" encoding="ISO-8859-1"?>
<application>
   <application-config>
       <property name="Vendor" value="my.company"/>
       <property name="SecurityArea" value="NetWeaver.Portal"/>
   </application-config>
   <components>
       <component name="my_eis_system">
          <component-config>
              <property name="ClassName" value=""/>
              <property name="SafetyLevel" value="medium_safety"/>
          </component-config>
          <component-profile>
              <property name="com.sap.portal.pcm.Title" value="My EIS system"/>
              <!-- value of the following property must match the value of RAR file -> connector-j2ee-engine.xml -> 'jndi-name'
              <property name="com.sap.portal.reserved.system.ConnectionFactoryClass" value="MyEisJNDIname">
                 <property name="plainDescription" value="Connection Factory Class"/>
              </property>
              <property name="ComponentType" value="com.sapportals.portal.system">
                 <property name="plainDescription" value="Component Type"/>
                 <property name="administration" value="DIALOG-READ-ONLY"/>
              </property>
              <property name="myStringConnectionSpecKey1" value="">
                 <property name="personalization" value="Dialog"/>
                 <property name="type" value="String"/>
                 <property name="category" value="Connection Properties"/>
                 <property name="plainDescription" value="Property 1"/>
                 <property name="longDescription" value="Property 1 long desc"/>
              </property>
              <property name="myBooleanConnectionSpecKey2" value="false">
                 <property name="category" value="Connection Properties"/>
                 <property name="personalization" value="Dialog"/>
                 <property name="type" value="boolean"/>
                 <property name="plainDescription" value="Property 2"/>
                 <property name="longDescription" value="Property 2 long desc"/>
              </property>
              <property name="myFixedValuesConnectionSpecKey3" value="value1">
                 <property name="category" value="Connection Properties"/>
                 <property name="personalization" value="Non-Dialog"/>
                 <property name="type" value="select[value1,value2]"/>
                 <property name="plainDescription" value="Property 3"/>
                 <property name="longDescription" value="Property 3 long desc"/>
              </property>
              <property name="com.sap.portal.reserved.system.category" value="Non SAP">
                 <property name="personalization" value="NONE"/>
                 <property name="type" value="String"/>
                 <property name="plainDescription" value="System category"/>
                 <property name="longDescription" value="the system category used for grouping systems"/>
                 <property name="administration" value="DIALOG-READ-ONLY"/>
              </property>
          </component-profile>
       </component>
   </components>
   <services/>
</application>

Once the system template has been defined and packaged, it can be deployed to the portal.

More Information