Simple Diagnostics Agent - Advanced Configuration
Advanced SDA Configuration Properties
| Property | Purpose | Default | File to Configure |
|---|---|---|---|
| servlet-max-pending | Configuration property determining the maximal number of pending request executions. | 5 | .\SMDAgent\default\configuration\agent\<SID>\custom.properties |
| servlet-time-out | Configuration property determining the time limit for request executions, in seconds. | 60 | .\SMDAgent\default\configuration\agent\<SID>\custom.properties |
| max-hanging-threads | The value dictates the maximal allowed number of timed -out tasks. | 25 | .\SMDAgent\default\configuration\agent\<SID>\custom.properties |
| jco.client.pool.max.connections | Maximum number of active connections that can be created for a destination simultaneously (jco.destination.peak_limit) | 10 | .\SMDAgent\default\configuration\global.configuration\<SID>\custom.properties |
| jco.client.default.language | Logon language | EN | .\SMDAgent\default\configuration\global.configuration\<SID>\custom.properties |
| jco.client.trace | Enable/disable destination related RFC trace (0 or 1) | 0 | .\SMDAgent\default\configuration\global.configuration\<SID>\custom.properties |
| jco.destination.pool_capacity | Maximum number of idle connections kept open by the destination. A value of 0 has the effect that there is no connection pooling, i.e. connections will be closed after each request. Connections are only created if needed. | 3 | .\SMDAgent\default\configuration\global.configuration\<SID>\custom.properties |
| jco.destination.expiration_time | Time in ms after that the connections hold by the internal pool can be closed | 60000 (= 60 seconds) | .\SMDAgent\default\configuration\global.configuration\<SID>\custom.properties |
| jco.destination.expiration_check_period | Interval in ms with which the timeout checker thread checks the connections in the pool for expiration | 60000 (= 60 seconds) | .\SMDAgent\default\configuration\global.configuration\<SID>\custom.properties |
| jco.destination.max_get_client_time | Max time in ms to wait for a connection, if the max allowed number of connections is allocated by the application | 30000 (= 30 seconds) | .\SMDAgent\default\configuration\global.configuration\<SID>\custom.properties |
| jco.trace_level | Sets the trace level for JCo (Global, for all destinations) | 4 | .\SMDAgent\default\configuration\global.configuration\#\custom.properties |
| jco.session_timeout | The idle timeout for JCo session contexts in minutes. (Global, for all destinations) | 10 | .\SMDAgent\default\configuration\global.configuration\#\custom.properties |
| jco.cpic_maxconv | The maximum number of connections allowed by the CPIC layer. (Default: runtime environment dependent, min. 202) | 1000 | .\SMDAgent\default\configuration\global.configuration\#\custom.properties |
| jrfc.client_connect_timeout | The timeout for a logon or a ping attempt in seconds. (Default: 60, valid range is 1 [one second] to 3600 [one hour]) (Global, for all destinations) | 60 | .\SMDAgent\default\configuration\global.configuration\#\custom.properties |
| jrfc.trace | If set to 1, RFC trace is turned on for all connections within JCo. (Global, for all destinations) | 0 | .\SMDAgent\default\configuration\global.configuration\#\custom.properties |
| cpic.trace | The trace level for the CPIC layer. The valid value range is from 0 (trace is off) to 3 (most verbose trace) (Default: 0) (Global, for all destinations) | 0 | .\SMDAgent\default\configuration\global.configuration\#\custom.properties |
| dpc.timeout.enabled | The key for determining if the DPC connect and read timeout should be set in relation to the used push period | true | .\SMDAgent\default\configuration\ com.sap.smd.agent.application.e2emai\<SID>\custom.properties |
Extend File System Browser Default Whitelists
Per default, it is allowed to download and preview specific file types.
If you want to extend the white list of file type, you should follow the instructions described in SAP Note 2603369.
If you want to extend the white list of directories you should follow the instructions as described in SAP Note 2632477.