Skip to main content
Version: 4

For SQL

This document discusses the parameters you need to set in the global values.yaml before deploying the application.

Cluster selection parameter​

In the global > config > autoscaling section of the values.yaml file, set the cluster on which you want to deploy the application. 

Parameter
Possible value
Description
clusterType
  • AKS
  • ARO
  • EKS

Set to:

  • AKS to deploy the application on AKS cluster
  • ARO to deploy the application on ARO cluster
  • EKS to deploy the application on EKS cluster

DB secrets​

 In the the global > envSecret section of the values.yaml file, set the following variables to your database credentials. 

To authenticate using these credentials, ensure that global > dbPullSecrets > create is set to true. If you do not want to specify credentials in the values.yaml file, refer to this section.

Parameter
Description
BACKEND_DB_USERNAME
Username for your Backend Database.
BACKEND_DB_PASSWORD
Password for your Backend Database. 
LOG_DB_USERNAME
Username for your Log Database. 
LOG_DB_PASSWORD
Password for your Log Database. 
LOG_ARCHIVE_DB_USERNAME
Username for your Log Archive Database. 
LOG_ARCHIVE_DB_PASSWORD
Password for your Log Archive Database.
QUARTZ_DB_USERNAME
Username for your Quartz database. This value will be the same as that for the Backend Database.
QUARTZ_DB_PASSWORD
Password for your Quartz database. This value will be the same as that for the Backend Database.

Other DB parameters​

In the global > environmentVariables section of the values.yaml file, set the values for the following DB parameters.

Variable
Value
BACKEND_DB_URLjdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Backend Database Name>;sendStringParametersAsUnicode=false;
BACKEND_DB_DRIVER_CLASScom.microsoft.sqlserver.jdbc.SQLServerDriver
BACKEND_DB_TYPESQL-Server
BACKEND_DB_DIALECTorg.hibernate.dialect.SQLServerDialect
BACKEND_DB_TRANSACTION_ISOLATION1
BACKEND_AUTHTYPE
Basic
LOG_DB_DRIVER_CLASS

com.microsoft.sqlserver.jdbc.SQLServerDriver

LOG_DB_URL

jdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Log Database Name>;sendStringParametersAsUnicode=false;
LOG_DB_TYPESQL-Server
LOG_DB_DIALECTorg.hibernate.dialect.SQLServerDialect
LOG_DB_TRANSACTION_ISOLATION1
LOG_DB_AUTHTYPEBasic
LOG_ARCHIVE_DB_URLjdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Log Archive Database Name>;sendStringParametersAsUnicode=false;
LOG_ARCHIVE_DB_DRIVER_CLASScom.microsoft.sqlserver.jdbc.SQLServerDriver
LOG_ARCHIVE_DB_TYPESQL-Server
LOG_ARCHIVE_DB_DIALECTorg.hibernate.dialect.SQLServerDialect
LOG_ARCHIVE_DB_VALIDATION_QUERYSELECT 1
LOG_ARCHIVE_DB_AUTHTYPEBasic
LOG_ARCHIVE_DB_TRANSACTION_ISOLATION1
QUARTZ_DB_URLjdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Backend Database Name>;sendStringParametersAsUnicode=false;
QUARTZ_DB_DRIVER_CLASScom.microsoft.sqlserver.jdbc.SQLServerDriver
QUARTZ_DB_TYPESQL-Server
QUARTZ_DB_DIALECTorg.hibernate.dialect.SQLServerDialect
QUARTZ_DB_AUTHTYPEBasic
BACKEND_DB_VALIDATION_QUERY
SELECT 1
LOG_DB_VALIDATION_QUERYSELECT 1

LOG_ARCHIVE_DB_SEPARATE

Defines whether archived logs use the same database as logs or a separate database. If set to true, archived logs must be stored in a separate database. 

  • false (default)
  • true

QUARTZ_DB_VALIDATION_QUERY

SELECT 1
QUARTZ_DRIVER_DELEGATE_CLASS

org.quartz.impl.jdbcjobstore.MSSQLDelegate

SPRING_QUARTZ_PROPERTIES_ORG_QUARTZ_JOBSTORE_LOCKHANDLER_CLASS

org.quartz.impl.jdbcjobstore.UpdateLockRowSemaphore

QUARTZ_SELECT_WITH_LOCK_SQL

SELECT * FROM {0}LOCKS WITH (UPDLOCK,ROWLOCK) WHERE SCHED_NAME = {1} AND LOCK_NAME = ?

QUARTZ_DB_TRANSACTION_ISOLATION1

Backend DB for AIMap​

In the global > aimap > environmentVariables section of the values.yaml file, set the value for the following Backend DB parameter for AIMap.

Variable
Value
AIMAP_BACKEND_URL
mssql+pyodbc://<host>:<port>/<Backend Database Name>?driver=ODBC+Driver+17+for+SQL+Server

Static and migration job execution settings​

Set the following parameters for static and migration job execution.

Section in the values.yaml
Parameter 
Description
global > migrationEXECUTE_MIGRATION_JOB
Set to true to ensure that all the accelerators are deployed with Adeptia Connect.
global > static
EXECUTE_STATIC_JOB
Set to true to ensure that all the static files (In the /shared directory in Adeptia Connect) are included in the deployment.

For optional parameters, refer to this page.

After configuring the parameters, refer to this page to continue with the application deployment steps.