Properties for EP 5.0 
The EPCF service for EP 5.0 is configured with the property file config.properties. You can find the file in the following directory:
<TOMCAT_HOME>/cluster/server/services/servlet_jsp/work/jspTemp/ irj/root/WEB-INF/portal/portalapps/com.sap.portal.epcf.loader/ config/config.properties
The EPCF service reads the property file at the Portal start up when the services are initialized. Therefore you have to restart the Portal so that the changes take affect, after you have changed the properties. If a property has an invalid value, the EPCF service uses the default value.
General Settings for EP 5.0
framework.level
Sets the EPCF level for the Portal. See chapter EPCF levels for more details.
Beginning with EP version 5.0.1.3 the client data bag and the session management has been implemented in JavaScript. If the Web client has no Java support, the EP switches automatically to this implementation.
# ----------------------------------------------------------------------
# Framework level
#
# framework.level=0 -> disabled EPCF
# framework.level=1 -> enable JavaScript
# framework.level=2 -> enable JavaScript & Java
# ----------------------------------------------------------------------
framework.level=2
script.set
If the EPCF service is running on the level 1 or 2, the appropriate JavaScript will be included automatically in every Portal page that is generated by the Portal page builder. The JavaScript code can be generated in two different ways:
...
1. Standard
The default value. The JavaScript code is generated in a user friendly form. The code contains comments and is formatted in a way, that it can easily be read, when you select the command View sourcein your browser.
2. Optimize
With this setting, the JavaScript code is generated without which discards all the comments and unnecessary white-space characters. The HTML code generated with the optimize option is about 30% smaller then generated with the standardversion. The optimize option is recommended for a productive system.
# ----------------------------------------------------------------------
# JavaScript settings. It has only effect with framework.level=1,2
#
# script.set=standard -> use standard JavaScript file set
# script.set=optimize -> use size-optimized JavaScript file set
# ----------------------------------------------------------------------
script.set=optimize
applet.trace.level
The ECPF service level 2 uses a Java applet that provides the client data bag, the data channel and the session management functionality. Log entries are written on the Java console of the Web client Java console to inform about errors. A high trace level generates many messages on the Java console which will slow down the Portal. The Portal administrator can disable messages by lowering the trace level. For a productive system we recommend the value 0.
# ----------------------------------------------------------------------
# Applet specific settings. It has affect with framework.level=2 only
#
# applet.trace.level=0 -> display error messages
# applet.trace.level=1 -> display error and warning messages
# applet.trace.level=2 -> display error, warning and information messages
# ----------------------------------------------------------------------
applet.trace.level=0
applet.archive
The Java applet for the EPCF service uses several Java classes. The classes can be loaded from the server in as one file, packed in a Java archive (JAR) file or as single class files. For a productive system, we recommend to set the applet.archive option to on.
#----------------------------------------------------------------------
# Applet specific settings. It has affect with framework.level=2 only
#
# applet.archive=on -> applet classes accessed via jar-file
# applet.archive=off -> applet classes accessed as singlefiles
# ----------------------------------------------------------------------
applet.archive=on
DSM Settings
Distributed session management requires the Terminator component to terminate the server sessions. The Terminator component processes the EPCF service request and sends the termination commands to the servers. To customize the Terminator component you have following properties:
dsm.term.mode
This property defines which Terminator component will be used. Following values are possible:
· internal
Uses the default Portal component DSMTerminator.default, supplied by the Portal.
· custcomp
Uses a Portal component specified with the property dsm.term.custcomp.
· custurl
Uses the component specified with the property dsm.term.custurl.
·
dsm.term.custcomp
The specified Portal component, for example, myTerminator.default, will be used as Terminatorcomponent. The parameter TermString is passed on to that component.
dsm.term.custurl
With this property you can specify any server side component (for example, servlet, JSP, Perl, ASP and so on), as Terminator component.
Example:
http://myserver/MyTerminator.asp
The component is started with the parameter TermString.
# ----------------------------------------------------------------------
# Distributed session management (DSM)
#
# dsm.term.mode=internal - predefined component DSMTerminator.default
#
# dsm.term.mode=custcomp - customer specific Portal component specified by
# dsm.term.custcomp = MyTerminator.default
#
# dsm.term.mode = custurl -> customer specific component, specified by
# dsm.term.custurl = http://myserver/MyTerminator.asp
# ----------------------------------------------------------------------