# Configuration of Server parameter

## 1. Server parameter configuration

The parameters used by the ProSync Manager server can be set in the prosyncmanager.properties file.

Each parameter is separated by a newline, and only one equals sign (=) is entered between the parameter name and the value, with no spaces.

```editorconfig
# LOG
LOG_LEVEL=INFO
LOG_DIR=${PRSMGR_HOME}/logs
LOG_COMPRESS=Y
LOG_MAX_FILE_SIZE=1GB
LOG_MAX_HISTORY=30
LOG_TOTAL_SIZE_CAP=30GB

# INTEGRITY CHECK
## parallel used in SELECT during check operation
IC_SELECT_THREAD_COUNT=8
## parallel used by DML during calibration operation
IC_APPLY_THREAD_COUNT=8
IC_QUEUE_SIZE=128
IC_DOWNLOAD_PATH=${PRSMGR_HOME}/verify
IC_CONNECTION_TIMEOUT=300
IC_READ_TIMEOUT=1800
## Thread pool size for verification tasks
## Occupy maximum number of equal SRC/TAR DB connections
IC_SERVICE_THREAD_CNT=10
## Thread pool size used for downloading the result after scan
IC_SERVICE_DOWNLOAD_THREAD_CNT=5
## Thread pool size used for calibration work
## Occupy TAR DB connection up to the value * 5
IC_SERVICE_APPLY_THREAD_CNT=5
## Sorting for non-UTF DBs
IC_USE_UNICODE_ORDER=false

# INITIAL LOAD
IL_EXTRACT_PARALLEL=N
IL_INSERT_PARALLEL=N
IL_LOCK_TIMEOUT=10
IL_LOG_PATH=${PRSMGR_HOME}/etl

# REPO DB
REPODB_USERNAME=repo_user
REPODB_PASSWORD=password
REPODB_IP=localhost
REPODB_PORT=13852
REPODB_DBNAME=prosyncmanager

# JWT 90days - 360days
JWT_VALID_TIME_MILLIS=7776000000
JWT_REFRESH_TIME_MILLIS=31104000000

# DB
DB_TIMEOUT_SECONDS=5

# TOMCAT LOG
TOMCAT_LOG_LEVEL=INFO
TOMCAT_LOG_DIR=${PRSMGR_HOME}/tomcat_logs
TOMCAT_LOG_COMPRESS=Y
TOMCAT_LOG_MAX_FILE_SIZE=1GB
TOMCAT_LOG_MAX_HISTORY=30
TOMCAT_LOG_TOTAL_SIZE_CAP=30GB

# HIST RETENTION
RETENTION_JOB_TIME=1
RETENTION_EVENT=30
RETENTION_ERROR=30
RETENTION_LONG_TX=30
RETENTION_RESOURCE=30
RETENTION_STATISTICS=30
RETENTION_TSN_DIFF=30

# TSN TIME MAP RETENTION
RETENTION_SRC_TIME_MAP=30
```

The following describes each parameter.

<table><thead><tr><th>Parameters</th><th width="383">Description</th><th>Default value</th></tr></thead><tbody><tr><td>LOG_LEVEL</td><td><p>The level of logs to be left by ProSyncManager, which can be changed dynamically.</p><p>(ERROR, WARN, INFO, DEBUG, TRACE)</p></td><td>INFO</td></tr><tr><td>LOG_DIR</td><td>The directory where ProSyncManager will leave logs.</td><td>${PRSMGR_HOME}/logs</td></tr><tr><td>LOG_COMPRESS</td><td>Determines whether to compress previous logs (Y, N)</td><td>Y</td></tr><tr><td>LOG_MAX_FILE_SIZE</td><td><p>The maximum size of individual log files. </p><p>It is in bytes and can be set using GB/MB/KB.</p></td><td>1GB</td></tr><tr><td>LOG_MAX_HISTORY</td><td>The number of days between log files to keep, with older files deleted.</td><td>30</td></tr><tr><td>LOG_TOTAL_SIZE_CAP</td><td>The upper limit for the sum of the total size of all log files, with older files deleted. It is in bytes and can be set using GB/MB/KB.</td><td>30GB</td></tr><tr><td>IC_SELECT_THREAD_COUNT</td><td>The number of threads used for data comparison during the consistency check operation.</td><td>8</td></tr><tr><td>IC_APPLY_THREAD_COUNT</td><td>The number of threads used for data correction during the consistency check operation.</td><td>8</td></tr><tr><td>IC_QUEUE_SIZE</td><td>The parameter for memory management of the consistency check and means the maximum value of statements to be held in the stream that reads/writes the sql file. If the users allow a value that is too large, it will affect the performance (resources) of the ProSync Manager by increasing the number of statements accumulated in memory when SQL file creation is slow, so set the appropriate value according to the environment. (1 - 2147483647)</td><td>128</td></tr><tr><td>IC_DOWNLOAD_PATH</td><td>The parameter of the verification function, where the sql file of the verification result will be saved.</td><td>${PRSMGR_HOME]/verify</td></tr><tr><td>IC_CONNECTION_TIMEOUT</td><td>The connection timeout for trying to connect to JDBC.(0 - 2147483647 seconds) If set to 0 seconds, the connection wait is performed without timeout.</td><td>300</td></tr><tr><td>IC_READ_TIMEOUT</td><td>Query Timeout to wait for a response when a query is sent to the server. (-1 - 2147483647 seconds) If set to a positive integer, it will wait for timeout (seconds). If it is 0 or a negative value, it will wait indefinitely for the query response.</td><td>1800</td></tr><tr><td>IC_SERVICE_THREAD_CNT</td><td>The number of threads to perform consistency checks simultaneously. All values greater than 0 are allowed, but allowing too many threads affects the performance (speed and resources) of the ProSync Manager, so set the appropriate value according to the users environment.</td><td>10</td></tr><tr><td>IC_SERVICE_DOWNLOAD_THREAD_CNT</td><td>The thread pool size used for downloading SQL files after the consistency result.0All larger values are allowed, but allowing too many threads affects the performance (speed and resources) of the ProSync Manager, so set the appropriate value according to the environment.</td><td>5</td></tr><tr><td>IC_SERVICE_APPLY_THREAD_CNT</td><td>The thread pool size used for the matching correction operation.Maximum {setting value} * 5 occupies the TAR DB Connection. All values greater than 0 are allowed, but allowing too many threads may affect the performance (speed and resources) of the ProSync Manager, so set the appropriate value according to the users environment.</td><td>5</td></tr><tr><td>IC_USE_UNICODE_ORDER</td><td>If the charset is not UTF, the sort order of special characters such as Chinese characters may be different. If this option is true, it changes the sort order to unicode when sorting by columns that are interpreted as Strings, such as char/varchar, in non-UTF environments.(This has an effect if the KEY contains a char/varchar column or if the table contains such a column without a KEY)</td><td>false</td></tr><tr><td>IL_EXTRACT_PARALLEL</td><td>The Parameter of the initial load function, which determines whether to parallelize extraction.(Y|N)</td><td>N</td></tr><tr><td>IL_INSERT_PARALLEL</td><td>The parameter of the initial load function, which determines whether to parallelize insertion.(Y|N)</td><td>N</td></tr><tr><td>IL_LOCK_TIMEOUT</td><td>The parameter of the initialization function, the time to try to lock the table in srcDB during initialization.(1 - 2147483647 seconds)</td><td>10</td></tr><tr><td>IL_LOG_PATH</td><td>The parameter of the initialization function, the location to save the log file of the initialization.(1 - 2147483644 seconds)</td><td>${PRSMGR_HOME}/etl</td></tr><tr><td>PEPODB_USERNAME</td><td>The user name to connect to repoDB </td><td>repo_user</td></tr><tr><td>REPODB_PASSWORD</td><td>The password of PEPODB_USERNAME to connect to repoDB.</td><td>password</td></tr><tr><td>REPODB_IP</td><td>The iP to connect to repoDB.</td><td>localhost</td></tr><tr><td>REPODB_PORT</td><td>The port to connect to repoDB. (0 - 65535)</td><td>13852</td></tr><tr><td>REPODB_DBNAME</td><td>The DB name to connect to repoDB.</td><td>prosyncmanager</td></tr><tr><td>JWT_VALID_TIME_MILLIS</td><td>jwt Token-related parameter, the valid time of the token. (1 - 9223372036854775807 milliseconds)</td><td>7776000000</td></tr><tr><td>JWT_REFRESH_TIME_MILLIS</td><td>jwt Token-specific parameter, the validity time of the refresh token. (1 - 9223372036854775807 milliseconds)</td><td>31104000000</td></tr><tr><td>DB_TIMEOUT_SECONDS</td><td>Timeout setting for query response to the control DB.(0:Infinite wait, 0 - 2147483647 seconds)</td><td>5</td></tr><tr><td>TOMCAT_LOG_LEVEL</td><td>Level of tomcat logs to deploy ProSyncManager.(ERROR, WARN, INFO, DEBUG, TRACE)</td><td>INFO</td></tr><tr><td>TOMCAT_LOG_DIR</td><td>Directory where tomcat logs will be located.</td><td>${PRSMGR_HOME}/tomcat_logs</td></tr><tr><td>TOMCAT_LOG_COMPRESS</td><td>COMPRESSDetermines whether to compress old tomcat logs.(Y, N)</td><td>Y</td></tr><tr><td>TOMCAT_LOG_MAX_FILE_SIZE</td><td>Maximum size of individual tomcat log files in bytes and can be set using GB/MB/KB.</td><td>1GB</td></tr><tr><td>TOMCAT_LOG_MAX_HISTORY</td><td>The number of days between tomcat log files to be retained. Older files will be deleted.</td><td>30</td></tr><tr><td>TOMCAT_LOG_TOTAL_SIZE_CAP</td><td>The upper limit for the total size of all tomcat log files. Older files will be deleted.</td><td>30GB</td></tr><tr><td>RETENTION_JOB_TIME</td><td>Time to execute to remove the partition saving log data. (0 - 23)</td><td>1</td></tr><tr><td>RETENTION_EVENT</td><td>The event information to store for a period of time (-1: never, 0: only store information for the day, max 365)</td><td>30</td></tr><tr><td>RETENTION_ERROR</td><td>The error information to store for a period of time (-1: Never, 0: Save only today's information, max 365)</td><td>30</td></tr><tr><td>RETENTION_LONG_TX</td><td>The long tx Information to save (-1: Never, 0: Save only today's information, max 365)</td><td>30</td></tr><tr><td>RETENTION_RESOURCE</td><td>cpu/mem Usage information to save (-1: Disabled, 0: Saves only the current day's information, max 365)</td><td>30</td></tr><tr><td>RETENTION_STATISTICS</td><td>The number of synchronized dml/ddl information (-1: Disabled, 0: Saves only the current day's information, max 365)</td><td>30</td></tr><tr><td>RETENTION_TSN_DIFF</td><td><p>Time information to save the tsn Diff information. </p><p>(-1: Disabled, 0: Saves only the current day's information, max 365)</p></td><td>30</td></tr><tr><td>RETENTION_SRC_TIME_MAP</td><td><p>Time information mapped to the tns.</p><p>(-1: Disabled, 0: Saves only the current day's information, max 365)</p></td><td>30</td></tr></tbody></table>

###


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tibero.com/prosyncmanager.en/prosync-manager-manual/installation-guide/installation/server-parametersettings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
