Show TOC

Background documentationServices Locate this document in the navigation structure

 

The <services> element defines the portal services that are part of this application, and includes configuration information for each. The element includes one or more <service> elements, each of which defines one portal service.

The following is an example of a <services> element that defines one service.

Syntax Syntax

  1. <services>
  2.   <service name="ContentProvider" alias="MyServiceAlias">
  3.     <service-config>
  4.       <property name="className" value="com.sap.portal.MyService"/>
  5.       <property name="startup" value="false"/>
  6.     </service-config>
  7.     <service-profile>
  8.       <property name="MyProperty " value="true"/>
  9.     </service-profile>
  10.   </service>
  11. </services>
End of the code.

Each <service> element can contain the following attributes:

  • Name: The name of the service

  • Alias: An alias for the service that can be used instead of the fully qualified name. This attribute is optional.

Each <service> element contains a <service-config> element that provides configuration for the service.

The following are standard properties for service configuration.

Name

Description

ClassName

The name of the implementation class of the portal service. This class must implement the IService interface.

startup

If set to true, the service is started at when the portal is started. If set to false or left blank, the service is started on demand.

Each <service> element can also contain a <service-profile> element that provides custom properties that can be modified by the system administrator.

There is only one set of values for these properties of a service.