Entering content frame

Component documentation Portal Runtime Core Locate the document in its SAP Library structure

Purpose

The PRT core offers an implementation of the API. It also manages the portal application life cycle and isolates the portal applications between them by implementing the class loader separation.

Implementation Consideration

The core implementation is delivered in a set of JAR files packaged in the WEB-INF/portal/lib directory:

JAR

Description

prtcore.jar

The PRT core

prtdeployment.jar

Helper class implementation to handle the format of PAR files and the deployment descriptor

prtgluer.jar

Utility classes of the PRT

prtlogger.jar

Default logger implementation

concurrency.jar

Concurrent thread access

This graphic is explained in the accompanying text

Changing the files located in the WEB-INF/portal/system/properties can change the functionality of the PRT core.

File

Description

prtDefault.properties

Default value for the properties of the PRT

prtCentral.properties

This file contains properties that are to be stored in the portal registry. During its first start up, the PRT reads this file and stores the corresponding objects in the registry. When this operation finishes successfully, the file is renamed with a .BAK extension

prtUpdate.properties

Internal PRT file, used to manage the upgrade of the runtime version

prtDelete.properties

Internal PRT file, used to manage the upgrade of the runtime version

You can change the following properties to customize the PRT behavior:

Property

Default Value

Description

runtime.doubleByteSupport

 

true

Shows if the runtime supports double byte encoding in the request and the response

runtime.doubleByteSupport.encoding

UTF-8

The type of encoding to be used when double byte support is activated in the PRT

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

default.component.timeout

10000

Timeout for the components of the asynchronous response

request.defaultlanguage

 

En

Default language to be used when none is specified

request.defaultcountry

Us

Default country to be used when none is specified

personalization.defaultDelegate

StandardEditDialog

 

Default delegate for the personalization of a component

caching.off

false

If the PRT cache must be turned off by default

caching.persistency

false

Activates the persistence layer of the PRT cache. If false, PRT uses a memory cache

This graphic is explained in the accompanying text

See caching.cluster.notification property

caching.cluster.notification

false

Uses the notification service to invalidate cached objects in a cluster configuration.

This graphic is explained in the accompanying text

Set to true when the caching.persistency is set to true

caching.maxsize

5000

The maximum size of the cache in KO before starting pre-emption

Monitor.off

true

If set to true, monitoring is switched off

connection.defaultcomponent

PortalAnywhere.default

The default portal component to start when none is specified

jsp.addclasspath

 

Classpath element to be added when a JSP is compiled in the portal runtime

loadlimit.requests

-1

Number of maximum concurrent requests managed by the PRT

portal.runtime.permission.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

 

See also:

 

·        Portal Runtime Cache

 

 

Leaving content frame