You can configure the portal runtime properties using two different tools:
Config Tool for offline configuration
You can configure all properties, but you need to restart the AS Java server for the changes to take effect.
SAP NetWeaver Administrator for online configuration
You can configure the properties that can be modified online, and the changes take effect immediately without restarting the AS Java server.
To configure properties in the Config Tool:
Start the Config Tool by double-clicking the configtool script file in the <SAP_install_dir>/<system_name>/<instance_name/j2ee/configtool directory on the server.
In the tree, navigate to
.Configure the properties as required. Note that you make the changes at the template level, so all service instances are updated with the same values.
Save your changes and restart the AS Java server.
For more information, see Modifying Service, Manager, or Application Properties .
To configure the online modifiable properties in SAP NetWeaver Administrator:
Start SAP NetWeaver Administrator at http://<server>:<port>/nwa .
Navigate to
.Choose Portal Runtime Container Extension (service component name tc~epbc~prtc~core ).
In the Properties table, configure the online modifiable properties as described below.
For more information, see Java System Properties and SAP NetWeaver Administrator .
The following table lists the portal runtime properties that you can configure as described above.
Property |
Default |
Description |
Online Modifiable |
---|---|---|---|
async.maxQueueSize |
10 |
Default queue size for asynchronous response threads |
No |
cache_type |
jcache |
Defines which cache implementation to use for portal caching: either jcache or CML (Cache Management Library). For more information about CML, see Cache Management System . |
No |
caching.maxsize |
5000 |
Maximum size of the cache in kilobytes, at which the cache is cleared to make room for new items. Only relevant when the cache is stored in memory. |
No |
caching.off |
false |
When set to false , enables portal caching. |
No |
caching.persistency |
true |
When set to true , enables persistency caching for all caches. |
No |
caching.persistency.clean.period |
5 |
The interval, in minutes, for clearing the cache. |
No |
caching.persistency.infinite.validity.clean.period.factor |
144 |
Factor by which the caching.persistency.clean.period property is multiplied to calculate the validity period for items with infinite validity. |
No |
caching.portalcomponent.persistency |
true |
When set to true , enables persistency caching for the portal component cache. |
No |
connection.defaultcomponent |
PortalAnywhere.Go |
The default portal component to start when none is specified. |
Yes |
connection.setbase |
false |
Defines whether the HTML <base> tags are automatically added to the response. |
No |
deployment.enableParallelDescriptorParsing |
true |
Defines whether parallel processing of portal application deployment descriptors is enabled. |
Yes |
deployment.supportedProviders |
A semicolon-separated list of the provider names that can be used when adding references from Portal Applications to J2EE Applications. To reference J2EE applications that are not portal applications, you use the format: SAPJ2EE::<provider name/application name> . When the provider is not SAP ( sap.com ), then you must add the provider name to this property, for the reference to work. |
Yes |
|
dispatcher.contactinfo |
If this situation persists, please contact your system administrator. |
The string to display if an error occurs in the dispatcher. |
Yes |
dispatcher.version |
The value is dynamically generated. |
The version number of the dispatcher |
No |
enable.http.conditional.request |
true |
Defines whether the HTTP conditional request is handled by the cache. |
Yes |
excludePrtBridgeMismatchVersion |
true |
Defines whether to ignore a version mismatch between the prt bridges over cluster nodes. |
Yes |
js.SupportVersion |
true |
When set to true , application static content files, such as js, css or jpeg files, are updated in the client browser cache each time a new version of the application is deployed. |
Yes |
personalization.defaultDelegate |
com.sapportals.portal.prt.util.StandardEditDialog |
The default delegate component for the personalization of a component |
No |
portal.html.head.title |
SAP NetWeaver Portal |
The HTML title for all portal pages |
Yes |
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>] For more information, see Displaying a Customized Error Message . |
Yes |
|
portal.runtime.security.mode |
production |
If set to development , access to prtroot is allowed for every component. If set to production , access to prtroot is not allowed unless the component belongs to a security zone. The component's security zone is checked when the component is loaded. |
No |
portal.service.twophaseinit |
true |
Defines whether initialization of the portal services is performed in two phases (the afterInit() method is called during startup). |
No |
repository.deployment |
true |
If set to true , invokes deployment of archive files, stored in the deployment/pcd folder, on server startup. Used for backward compatibility. |
No |
request.defaultcountry |
us |
The default country, when none is specified |
Yes |
request.defaultlanguage |
en |
The default language, when none is specified |
Yes |
runtime.doubleByteSupport |
true |
Defines whether support of double-byte encoding in the request and response is enabled. |
No |
runtime.doubleByteSupport.encoding |
UTF-8 |
The encoding when double-byte support is activated. |
No |
session.ensurestickiness |
true |
If set to true or yes , ensures sticky sessions for each request. |
Yes |
workplace.version |
The value is dynamically generated |
The portal version number |
No |
xhtml.compliant |
no |
Defines compliance of the PRT HTML output with the XHTML standard:
|