Configuration File for Extended Services

Configuration information for extended services is stored in the services.properties file, located in MIDDLEWARE_HOME/user_projects/epmsystem1/config/ReportingAnalysis.

To help avoid name collisions with internal EPM Workspace commands or commands of other services, every extended service has a URL prefix; however, you do not need to specify a prefix in a services.properties entry. If an entry lacks a prefix, the default prefix ext is assigned to it.

Each extended service must have two entries in services.properties: one for each of the two properties, resource and resource type. The resource is the file or program that handles requests for the extended service. The resource may be, for example, an HTML or JSP file or a servlet. The resource type indicates whether the resource is represented by a path ($PATH$) or a name ($NAMED$).

If the resource is identified by a file or program path, the resource value should be the path. A path is typically an absolute path from the Web server context root, starting with the “/” (forward slash) character. If the resource is identified by a named resource such as a servlet, the resource value should be the name of the servlet (as known to the Web server).

You can add query parameters to the resource value if the resource is of the type $PATH$. This lets you pass parameters with static values to the resource.

Entries in services.properties should use this format:

[urlPrefix.]serviceCommandName.resource=PathOrName[?param1=value1&param2=value2] [urlPrefix.]serviceCommandName.type=$PATH$|$NAMED$ 

Examples of services.properties entries are shown in Examples Entries and URLs for Service Properties.