An application.properties file in the $THREEDS_HOME/3dss-transaction-cli-tool/conf directory is used to set configuration options for the 3DS Transaction CLI Tool.
The available configuration options are listed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 | ## Database connection properties## The datasource URL location. The JDBC connection string may differ depending on the database type, but we recommend# the specified formats defined below. Supported database types are PostgreSQL, MySQL, Oracle and Microsoft SQL Server.## Recommended JDBC connection strings:# PostgreSQL: jdbc:postgresql://<host>:<port>/<database-name># MySQL: jdbc:mysql://<host>:<port>/<database-name># Oracle: jdbc:oracle:<oracle-driver>:<host>:<port>:<SID># Microsoft SQL Server: jdbc:sqlserver://<host>:<port>;database=<database-name>#spring.datasource.url=## The SQL dialect of the underlying database. Supported database types are PostgreSQL, MySQL, Oracle and Microsoft SQL Server.# The value should be defined depending on the underlying database.## Accepted values are depending on the desired dialect, but it is recommended to use one of the following:## org.hibernate.dialect.PostgreSQL95Dialect - indicating PostgreSQL 9.5 Dialect will be used# org.hibernate.dialect.MySQL57Dialect - indicating MySQL 5.7 Dialect will be used# org.hibernate.dialect.Oracle12cDialect - indicating Oracle 12 c Dialect will be used# org.hibernate.dialect.SQLServer2012Dialect - indicating Microsoft SQL Server 2012 Dialect will be used#spring.jpa.properties.hibernate.dialect=## The datasource user used by the tool. This user needs to have read-write privileges on the database the tool is using.#spring.datasource.username=## The password of the datasource user used by the tool.#spring.datasource.password=### Processing transactions properties## The 3DSS Searchable Old Transactions Tool will iterate over the existing transaction log entries and will update each# transaction log entry by filling the new searchable columns. This property indicates the number of iterations that the# tool will make. Each iteration will process ${transactions.batch.size} number of transaction log entries.# The default values are 1 iteration with 5000 transaction log entries size.## In case of greater number of existing transaction log entries, we recommend processing them# in multiple iterations in order to prevent locking the transaction log table. There is also a possibility to run the# tool more than once at different time periods.#transactions.batch.iterations=1## The number of transactions processed in one iteration. The default value is 5000, meaning 5000 transaction log entries# processed in one iteration.#transactions.batch.size=5000 |