For the production environment, you need to tune Connect Server configuration to improve the performance. Change the value of the following parameters to the suggested value:
Location | Name | Suggested Value (Based on 8 GB RAM) |
|---|
|
launcher.properties available at …/<ConnectServerInstallFolder>/ ServerKernel/etc | Kernel: Xms* | 2 GB |
Kernel: Xmx** | 4 GB |
WebRunner: Xms | 256 MB |
WebRunner: Xmx | 512 MB |
|
server-configure.properties available at …/<ConnectServerInstallFolder>/ ServerKernel/etc | abpm.jdo.maxActive | 100 |
abpm.logdb.pool.maxActive | 200 |
abpm.archive.logdb.pool.maxActive | 50 |
abpm.queue.processor.concurrent.
processes | 20 |
abpm.queue.processor.reload.factor | 80 |
log4j.rootLogger | ERROR,console,jdbc |
log4j.logger.org.exolab.castor | ERROR |
log4j.logger.Event | ERROR |
|
log-cleanup.properties available at …/<ConnectServerInstallFolder>/ ServerKernel/etc | abpm.AU_LOG.logRetainTime | 2 |
abpm.AU_SAP_TID.logRetainTime | 2 |
abpm.AU_SAP_IDOC.logRetainTime | 2 |
abpm.AU_TRANSACTIONDATA.log
RetainTime | 2 |
abpm.AU_EVENTLOG.logRetainTime | 2 |
abpm.AU_TASKLOGS.logRetainTime | 2 |
abpm.AU_PROCESSVARIABLETRACKER.
logRetainTime | 2 |
abpm.AU_TRANSACTIONLOG.log
RetainTime | 2 |
abpm.AU_SPAZIOLOG.logRetainTime | 2 |
abpm.EDI.logRetainTime | 2 |
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
Nest step
Performance Tuning of Connect Portal
