Configuring the Portal Runtime

You configure the Portal Runtime by defining a set of properties in the Property Editor of the Portal Runtime, in the dispatcher.properties file and in the SAP NetWeaver Administrator.

Portal Runtime Properties

In the portal, navigate to System Administration → System Configuration → Service Configuration.
In the Portal Catalog, navigate to Portal Runtime → Central Configuration and open the Property Editor.
Change the properties listed below as required.

Restart the portal irj application for the changes to take effect.

For more information, see Starting and Stopping Portal Services .

Property	Default Value	Description
caching.cluster.notification	`true`	Enables the use of the notification service to invalidate cached objects in a cluster configuration. Set this property to `true` when the caching.persistency property is set to `true` .
caching.off	`false`	If set to `false` , enables portal caching
caching.persistency	`true`	Enables persistency caching for all caches
connection.defaultcomponent	`PortalAnywhere.default`	The default portal component to start when no one is specified
default.component.timeout	`10000`	The timeout of the asynchronous response for the components, in milliseconds
enable.http.conditional.request	`true`	Enables the handling of the HTTP conditional request by the cache
js.SupportVersion	`false`	Set to `true` to update, in the client browser cache, static content files of an application, such as `JS` , `CSS` or `JPEG` files, each time a new version of the application is deployed.
jsp.addclasspath		The `classpath` element to be added when a JSP is compiled in the portal runtime
monitor.off	`true`	Enables monitoring
personalization.defaultDelegate	`com.sapportals .portal.prt.util .StandardEditDialog`	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.exception.errorcomponent		An error component with a customized message in a portal application that is displayed instead of the standard portal runtime error message Set to`<portal application name>.<[application component name]>` More information: Displaying a Customized Error Message
portal.runtime.security.mode	`production`	If set to `development` , access to the root component (prtroot) is allowed for every component. If set to `test` , access to to the root component is allowed for every component that does not belong to a specified zone. If set to `production` , access to to the root component is not allowed unless the component belongs to a security zone. Access to the security zone is tested here.
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`	Enables support of double-byte encoding in the request and response.
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.
caching.portalcomponent .persistency	`true`	Enables persistency caching for the portal component cache.
connection.setbase	`false`	Enables the automatic addition of basic HTML tags, such as`<html>` and`<head>` , to the response.
jsp.bigmode.delimit.size	`10000`	Specifies to use code optimization for JSP files larger than the specified number of bytes.
workplace.version	The value is dynamically generated.	The portal version number

To set the following property, modify the dispatcher.properties file, located in the/root/ WEB - INF /conf folderof the portal irj application.

dispatcher.contactinfo

If this situation persists, please contact your system administrator.

The string to display if an error occurs in the dispatcher

J2EE Properties

In the SAP NetWeaver Administrator, modify the properties for the com.sap.portal.prt.sapj2ee service J2EE service, and restart the service.

Navigate to System Management → Configuration → System Properties.
Under Configurations, choose the appropriate system ID, instance ID and server ID.
Under Details, go to the Services tab and choose com.sap.portal.prt.sapj2ee .

Under Extended Details, modify the properties as required.

Property	Default Value	Description
EnableLogging	`false`	Enables logging of information messages to the `com.sap.portal.sapj2ee .infoWarning` location. To enable logging, also configure the `infoWarning` location.
PortalApplicationName	`sap.com/irj`	The portal application name (provider name and application context name)
PortalStartupTimeout	`420000`	The timeout for starting up the portal, in milliseconds
async.response.pool.size	`100`	The pool size for the asynchronous response mechanism
async.response.timeout.pool.size	`100`	The thread pool size for managing the timeout when the asynchronous response mechanism is used
caching.persistency.clean.period	`5`	The interval, in minutes, for cleaning the cache
caching.persistency.infinite.validity .clean.period.factor	`144`	Helps determine the validity period for items with infinite validity. The validity period is (caching.persistency .clean.period) * (this property)
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.
pooling.string.buffer.maxsizebytes	`20000000`	The maximum size, in bytes, for each VM for string buffer pools. Special values: 0: No pool -1: Infinite pool
portal.navigation.cache.enable portal.navigation.cache.lifetime portal.navigation.cache.maxsize		Deprecated properties for configuring the overall navigation cache. The navigation cache is now configured per connector, as described in Caching Navigation Nodes .

More information: System Landscape Administration with SAP NetWeaver Administrator