EPCF Configuration
To configure the EPCF service you have to be logged in as administrator.
Configuration steps:
...
1. Choose the command System Administration in the top level navigation.
2. Choose the commands System Configuration → Service Configuration
3. Choose the Browse tag and open the node Applications.
4. Open the node com.sap.portal.epcf.loader.
5. Open the subnode Services and you will see the entry epcfloader.
6. Click the epcfloader entry with the right mouse key and select Edit.
The property page is displayed and you can modify the values. To save the changes, choose the Save button.
If you are working in a cluster environment, you have to restart the EPCF service so that the changes take immediate effect on all cluster nodes.
If the EPCF property values are not set correctly, the EPCF service uses the default settings at runtime.
EPCF Properties
Property |
Description |
applet.archive = < on | off > |
Defines if the classes of the Java applet are transferred as single class files or in one Java archive (JAR). This setting has only an affect if the framework.level property is set to 2. on: All classes are loaded from the server to the client in one JAR file. off: Every class is loaded from the server to the client individually. For a productive system we recommend the value on. |
applet.trace.level = < 0 | 1 | 2 > |
This setting only has an affect if the framework.level property is set to 2. The applet.trace.level controls the level of error messages displayed. A higher applet.trace.level reduces the portal performance. 0: Display errors only. 1: Display errors and warnings. 2: Display errors, warnings and information. For a productive system we recommend the value 0. |
epcf.databag.enforce.cookie = <false | true> |
This marks the logon ticket as a secure cookie, to enforce that the client browser sends the cookie only when an SSL connection to the J2EE Engine or the reverse proxy is established. Default value: false |
framework.level = < 0 | 1 | 2 > |
Defines the EPCF service level in use. Please refer to section EPCF Level for more details. The default setting is 2. |
framework.level.debug = <on | off | *> |
Internal debugging only: when activated, extra HTML comments, containing the properties of the portal components used, are rendered Default value: off |
script.dynamic.top = < on | off | *> |
Internal fallback only: central switch to disable the computation of dynamic top frame references needed for nested portals Default value: on |
script.exception = < on | off | *> |
Internal debugging only: displays exceptions from the event delivery in the browser popup windows Default value: off |
script.set = <standard | optimize> |
Specifies which version of the script to use: standard (the more readable version) or optimize (the performance- optimized version) Defualt value: optimize |
script.trace = < on | off | *> |
Internal debugging only: activates tracing of the EPCF API calls Default value: off |
workprotect.mode.default = < 1 | 2 | 3 > |
The default WorkProtect mode set by administrator. Users can personalize it as required. ● 1: protect data, open new window ● 2: discard data ● 3: display decision popup Default value: 1 |
workprotect.mode.personalize = < on | off | *>
|
Specifies whether to enable/disable the personalization of WorkProtect Default value: on |
workprotect.mode.features |
Fallback only: Feature string for window.open. A comma-separated list of values that specify the properties of a new window in which a navigation target is opened. If not specified or empty, the new window inherits the properties of the original window |
workprotect.popup.mode.options |
Specifies which options are displayed in the dialog box. The valid values are: ● N: Continue with navigation and open new window ● D: Discard changes and open content in same window ● C: Go back to your page and save data You can use any combination of these values, for example, ND. Leave the value empty to display all options. |
See also