Additional Configuration and Tuning Parameters 

Communication Between Applications and XML DAS

AS Java: HTTP Provider

As HTTP is used for the communication between an application system and the XML DAS (particularly for sending and receiving resources contained in the HTTP body) and because of the dispatcher/server communication within the AS Java, the properties of the HTTP Provider set some limits and influence the performance of XML-based archiving.

We recommend that you check especially the following properties of the HTTP Provider and adjust them to your needs using the AS Java Visual Administrator:

●      Dispatcher:

○       MaxRequestContentLength

●      Server:

○       ServletsLongDataTransferTimeout

○       ServletsLongDataTransferLimit

○       NeverCompressed

(If you want to prevent the XML DAS traffic from being compressed, enter application/octet-stream because this content type is used by both the XML DAS and its connectors.)

For a detailed explanation and default values, see HTTP Provider Service in the Administration Manual for the AS Java, and HTTP Provider Service in the Reference Manual for the AS Java.

Communication Between XML DAS and Archive Stores

WebDAV Communication Parameters

●      The default values are:

WEBDAVCONNECTIONTEMPLATELIMIT  =  5

Maximum number of concurrently open connections used per archive store residing on a WebDAV server.

 

WEBDAVCONNECTTIMEOUT  =  10000 (in milliseconds)

Timeout for opening connections (when XML DAS tries to open a socket to a WebDAV server).

 

WEBDAVEXPIRATIONTIMEOUT  =  10000 (in milliseconds)

Timeout interval after which the connection assumes that an open but unused socket has expired.

 

WEBDAVREADTIMEOUT  =  60000 (in milliseconds)

Timeout interval during which a connection waits for responses from a WebDAV server. This timeout is applied to blocking read operations.

File System Parameters

●      FILESYSTEMSYNC = Y

Forces all system buffers to synchronize with the underlying device, making sure that a resource is actually written to the file system and is not still only located in the cache.

The password and user for the WebDAV protocol (formerly WEBDAVCLIENTPWD  =  <for example sap630> and WEBDAVCLIENTUSR  =   <for example xmldas> are obsolete, because the credentials are taken from the WeDAV destination.

Using CA Wily Introscope

You can use the CA Wily Introscope functionality if you need to perform workload analyses for XML DAS or trace and profile XML DAS requests. As of CA Wily Introscope 8.0.2, the relevant parameters for XML DAS are provided in the profile sap.j2ee.pbd in section “ILM”. These parameters are not active by default. To use them they need to be activated.

For more information on CA Wily Introscope, refer to Performance Metrics Monitoring with Introscope by Wily.