This section describes the different properties that you can use in the STR to configure ECs.
...
Database Properties
Property | Description | ||
|---|---|---|---|
max.cached.prepared.statements | Default value: If you want to change the number of preparedStatements that are cached between connections, you can use this property to specify a different number than the default.
| ||
connectionpool.strict.pool.size | Default value: If you enable this property, the database pool enables the Blocking Queue implementation where there is a strict restriction to the maximum number of connections.
This property is general for all supported databases. It is enabled per each EC separately. If enabled the connection pool for the particular EC have a strict maximum limit. The maximum limit can be set in the Database profile agents Properties tab. For more information on this tab, refer to the Database Profile. | ||
connectionpool.wait.timeout.milliseconds | Default value:
This property is used to configure the amount of time a thread should remain in the blocked queue until it tries for a new connection. If a connection is made available before this time, the thread's waiting time is interrupted. |
...
Property | Description |
|---|---|
rest.client.idleTimeout | Default value: "200s" This property specifies the time a connection stays idle before it is eligible to be disconnected. If there is no traffic during the specified time, the REST Client agent will remove the session once the timeout is reached. You can also set this property on the container level, where the value is only applied to all ECs under a particular container. You can refer to Container Properties for more information. |
rest.client.max.chunk.size | Default value: "8m" This property specifies the maximum chunk size of the HTTP response that the REST Client agent should receive from the server. The agent will reject data with sizes that are larger than the value defined by this property. You can also set this property on the container level, where the value is only applied to all ECs under a particular container. You can refer to Container Properties for more information. |
rest.client.max.content.length | Default value: "64m" This property specifies the maximum length of the HTTP content received by the REST Client agent. The agent will reject content that is longer than the specified value defined by this property. Although it is also possible to set the value of this property to infinite, there will be a possibility that the EC will crash from an out-of-memory error. So do consider setting the memory size of the EC to be higher than the expected size of the HTTP content that the agent will be receiving. You can also set this property on the container level, where the value is only applied to all ECs under a particular container. You can refer to Container Properties for more information. |
rest.client.max.strict.bytes | Default value: "8m" This property specifies the maximum memory bytes size when loading an entire entity to the memory. The agent will reject response that is larger than the specified value defined by this property. Although it is also possible to set the value of this property to infinite, there will be a possibility where the EC will crash from an out of memory error. So do consider setting the memory size of the EC to be higher than the expected size of the HTTP content that the agent will be receiving. You can also set this property on the container level, where the value is only applied to all ECs under a particular container. You can refer to Container Properties for more information. |
SAP RFC Properties
Property | Description |
|---|---|
saprfc.bcd.double | Default value: This property determines whether the double data type is used when converting for mapping to SAP JCo ABAP Type P (Binary Coded Decimal). The possible values are:
|
SNMP Properties
Property | Description | ||
|---|---|---|---|
snmp.auth.proto.maxCompatibility | Default value: Due to security risks, SHA-1 and MD5 are by default disabled for SNMPv3. To enable them, set this property to true. This allows compatibility for all authentication algorithms, including SHA-1 and MD5.
|
...