Skip to main content
Version: 3

Performance Tuning of Connect Server

For production environment, you need to tune Connect Server configuration to improve the performance. Change the value of the following parameters to the suggested value:

LocationNameSuggested Value

(Based on 8 GB RAM)
launcher.properties available at …/<ConnectServerInstallFolder>/ ServerKernel/etcKernel: Xms*2 GB
Kernel: Xmx**4 GB
WebRunner: Xms256 MB
WebRunner: Xmx512 MB
server-configure.properties available at …/<ConnectServerInstallFolder>/ ServerKernel/etcabpm.jdo.maxActive100
abpm.logdb.pool.maxActive200
abpm.archive.logdb.pool.maxActive50
abpm.queue.processor.concurrent.
processes
20
abpm.queue.processor.reload.factor80
log4j.rootLoggerERROR,console,jdbc
log4j.logger.org.exolab.castorERROR
log4j.logger.EventERROR
log-cleanup.properties available at …/<ConnectServerInstallFolder>/ ServerKernel/etcabpm.AU_LOG.logRetainTime2
abpm.AU_SAP_TID.logRetainTime2
abpm.AU_SAP_IDOC.logRetainTime2
abpm.AU_TRANSACTIONDATA.log
RetainTime
2
abpm.AU_EVENTLOG.logRetainTime2
abpm.AU_TASKLOGS.logRetainTime2
abpm.AU_PROCESSVARIABLETRACKER.
logRetainTime
2
abpm.AU_TRANSACTIONLOG.log
RetainTime
2
abpm.AU_SPAZIOLOG.logRetainTime2
abpm.EDI.logRetainTime2

where,

*Xms is the minimum requirements **Xmx is the maximum requirements

As a best practice, it is recommended to use below settings for JVM:

Operating System and Java JRE: 64 bit Java heap size for Connect Server Kernel: 60% of the total memory Java heap size for Connect Server WebRunner: 20 % of the total memory

For Example:  For 8GB RAM - Kernel = 4.8GB; Webrunner = 1.6GB For 16GB RAM – Kernel = 10GB; WebRunner = 3.2GB