Configure back-end connection properties to ensure that adequate resources are allocated for SAP Mobile Platform Server connections to the data source back end.
The number of required connections varies, based on the maximum number of SAP Mobile Platform Server threads in use at any time and the length of time it takes for the back end to respond. If possible, allocate a connection for each thread.
Connection pools allow SAP Mobile Platform Server to reuse established connections to a back-end data source. If the number of connections in the pool is lower than the number of threads, you may experience timeouts. To avoid timeouts, you can adjust the connection timeout value. However, a higher connection timeout value will make it harder for other threads to get a back end connection.
| Property | Description | Default Value |
|---|---|---|
| -Dcom.sap.mobile.platform.server.connection.pool.idletimeout | The amount of time, in seconds, that a connection in the pool can be idle before it is removed. | 600 |
| -Dcom.sap.mobile.platform.server.maximum.connectionPoolSize | The maximum number of concurrent HTTP connections that the server can make to any URL. | 5000 |
| -Dcom.sap.mobile.platform.server.connection.timeout | The amount of time, in milliseconds, before a database connection operation will time out. | 60000 |
| -Dcom.sap.mobile.platform.server.connection.sotimeout | The amount of time, in milliseconds, that the socket will wait for data from the back-end data source before disconnecting. | 6000 |
| -Dcom.sap.mobile.platform.server.maximum.gzipPoolSize | The maximum number of concurrent GZIP
input streams
that
can be processed by
the
server. Using GZIP compression to compress the HTTP request body reduces network traffic and can improve performance. |
5000 |