Using the system_overrides.properties
file
The system_overrides.properties file is automatically created or updated when you update system settings. It is stored in the install_dir/properties directory along with other properties files.
system_overrides.properties
file stores information for these and other items:- Performance tuning wizard ( )
- Log screens in the user interface ( )
- QueueWatcher (http://host:port/queueWatch)
- (Windows only) Passphrase
This file is not manually created like the customer_overrides.properties
file.
However, it uses the same property naming conventions as the
customer_overrides.properties
file. These property names use prefixes that are
defined in the servers.properties
file. For example, the
jdbcService.oracleArchivePool.buffersize=500
property value indicates a value for
the oracleArchivePool.buffersize
property in the jdbc.properties
file.
The system_overrides.properties
file stores property values that are both
directly and indirectly affected by your changes to system settings.
system_overrides.properties
file in a Linux installation of Sterling B2B Integrator.jdbcService.oracleArchivePool.buffersize=500
jdbcService.oracleArchivePool.initsize=1
jdbcService.oracleArchivePool.maxsize=30
jdbcService.oraclePool_NoTrans.buffersize=500
jdbcService.oraclePool_NoTrans.initsize=1
jdbcService.oraclePool_NoTrans.maxsize=30
jdbcService.oraclePool_local.buffersize=500
jdbcService.oraclePool_local.initsize=1
jdbcService.oraclePool_local.maxsize=30
jdbcService.oraclePool.buffersize=500
jdbcService.oraclePool.initsize=1
jdbcService.oraclePool.maxsize=30
jdbcService.oracleUIPool.buffersize=500
jdbcService.oracleUIPool.initsize=1
jdbcService.oracleUIPool.maxsize=30
jdbcService.defaultDocumentStorageType=DB
logService.opslogger.loglevel=ALL
logService.opslogger.maxlogsize=50000
logService.httplogger.loglevel=ALL
logService.httplogger.maxlogsize=50000
noapp.queueWatcher=true
- The
jdbcService.*
values were added after the performance tuning wizard was used to change the values of the fields Physical memory (MB) allocated to Sterling B2B Integrator and Physical Memory Allocated to Server (MB).- The values that were manually changed were updated in the tuning.properties file.
- The
jdbcService.*
values were added to the system_overrides.properties file and the tuningPreviousSettings.properties file. These values affect the jdbc.properties file.
- The
logService.*
values were added after changes were made to the log settings of the Operations Server and the HTTP Server Adapter. - The
noapp.queueWatcher
value was added after changes to the AE_ExecuteCycle field on Queues 1 and 4.
Using system_overrides.properties
on Certified Container setup
You must use system_overrides.properties
packaged as a part of Helm charts to
update any property.
For more information, see Configuring system_overrides.properties
section in
Configuring property files.