Configuring Portal Runtime
Settings
You can configure the portal by modifying portal properties in the NetWeaver Administrator.
The properties can be modified in the by navigating to the Java System Properties window of NetWeaver Administrator with the following URL:
http:/<server>:<port>/irj/sys-config.
In the Details area, select the Services tab, and then select the Portal Runtime Container Extension (tc~epbc~prtc~core) service.
For more information on the NetWeaver Administrator, see Working with SAP NetWeaver Administrator.
The following are the configurable portal properties:
Property |
Default |
Description |
async.response.pool.size |
40
|
The pool size for the asynchronous response mechanism |
async.response.timeout.pool.size |
40
|
The thread pool size for managing the timeout when the asynchronous response mechanism is used |
cache_type |
jcache |
Indicates the cache to use for portal caching, either jcache or CML |
caching.maxsize |
5000
|
The maximum size of the cache, in kilobytes, before clearing the cache to make room for new items for the cache. Only relevant when the cache is stored in memory. |
caching.off |
false
|
Indicates whether portal caching is on. |
caching.persistency |
true
|
Enables persistency caching for all caches. |
caching.persistency.clean.period |
5 |
The interval, in minutes, for cleaning the cache |
caching.persistency.infinite.validity |
144 |
Helps determine the validity period for items with infinite validity. The validity period
is (caching.persistency |
caching.portalcomponent.persistency |
true |
Enables persistency caching for the portal component cache. |
connection.defaultcomponent |
PortalAnywhere.Go
|
The default portal component to start when one is not specified |
false |
Indicates whether basic HTML tags, such as <html> and <head>, are automatically added to the response. |
|
default.component.timeout |
10000
|
Timeout for the components of the asynchronous response |
dispatcher.contactinfo |
If this situation persists, please contact your system administrator. |
A string to display if an error occurs in the dispatcher |
dispatcher.version |
The value is dynamically generated. |
The dispatcher version number |
enable.http.conditional.request |
true
|
Indicates whether the cache handles the HTTP conditional request. |
jsp.addclasspath |
|
Classpath element to be added when a JSP is compiled in the portal runtime. |
jsp.bigmode.delimit.size |
10000 |
Specifies to use code optimization for JSP files larger than the specified number of bytes. |
monitor.off |
true |
If true, monitoring is off. |
personalization.defaultDelegate |
com.sapportals |
The default delegate component for the personalization of a component |
portal.html.head.title |
SAP NetWeaver Portal |
The HTML title for all portal pages |
portal.runtime.security.mode |
production
|
If set to development, prtroot access is allowed for every component. If set to test, prtroot access is allowed for every component that does not belong to a specified zone. If set to production, prtroot access is not allowed unless the component belongs to a security zone. Access to the security zone is tested here. |
portal.service.twophaseinit |
true |
Indicates whether the afterInit() method is called during startup of portal services. |
request.defaultcountry |
us
|
The default country, when one is not specified |
request.defaultlanguage |
en
|
The default language, when one is not specified |
runtime.doubleByteSupport |
true
|
Indicates whether double-byte encoding in the request and response is supported. |
runtime.doubleByteSupport.encoding |
UTF-8
|
The encoding when double-byte support is activated |
session.ensurestickiness |
true
|
If set to true or yes, ensures sticky sessions for each request. |
workplace.version |
The value is dynamically generated. |
The portal version number |
You can also use
the Config Tool to change properties, which are listed under Services →
tc~epbc~prtc~core. For more information,
see
Config
Tool.