For Oracle

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_URL	jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>
BACKEND_DB_DRIVER_CLASS	oracle.jdbc.OracleDriver
BACKEND_DB_TYPE	Oracle
BACKEND_DB_DIALECT	org.hibernate.dialect.OracleDialect
BACKEND_DB_TRANSACTION_ISOLATION	2
BACKEND_AUTHTYPE	Basic KerberosWithKeyTab KerberosWithServiceAccount
BACKEND_KERBEROS_DB_LOGIN_MODULE_NAME	Set its value to KerberosServer if you want to use Kerberos authentication for the Oracle database.
BACKEND_ KERBEROS_CONFIGURATION	This is applicable only when you're using Kerberos as the authentication type for the Oracle database. · -Kerberos authentication is not supported for AIMap microservice. Enter the required Kerberos parameters with their respective values in key-value pairs(comma separated)as shown in the example below: <keytab_file_path>"principal=HTTP/hostname.mydomain.</keytab_file_path> <keytab_file_path>com,</keytab_file_path><keytab_file_path>useKeyTab=</keytab_file_path>true,keytab<Keytab_ File_Path>,storeKey=true,isInitiator= true,debug=true,realm=MYDOMAIN. COM" <keytab_file_path>For the details of the Kerberos parameters, for example, principal, useKeytab, storeKey, and</keytab_file_path> <keytab_file_path>others, refer to this page.</keytab_file_path> To make the Kerberos configuration work, ensure that you: -Set the storeKey  and isInitiator parameters to true. -Add the parameter allow_weak_crypto under [realms] and [libdefaults] tags in krb5.conf file located at /shared) and set its value to true.
LOG_DB_DRIVER_CLASS	oracle.jdbc.OracleDriver
LOG_DB_URL	jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>
LOG_DB_TYPE	Oracle
LOG_DB_DIALECT	org.hibernate.dialect.OracleDialect
LOG_DB_TRANSACTION_ISOLATION	2
LOG_DB_AUTHTYPE	Basic KerberosWithKeyTab KerberosWithServiceAccount
LOG_DB_KERBEROS_DB_LOGIN_MODULE_NAME	Set its value to KerberosServer if you want to use Kerberos authentication for the Oracle database.
LOG_DB_KERBEROS_CONFIGURATION	-This is applicable only when you're using Kerberos as the authentication type for the Oracle database. -Kerberos authentication is not supported for AIMap microservice. Enter the required Kerberos parameters with their respective values in key-value pairs (comma separated) as shown in the example below: "principal=HTTP/hostname.mydomain. com,useKeyTab=true,keytab<keytab_file_path>,storeKey=</keytab_file_path> <keytab_file_path>true,isInitiator=</keytab_file_path>true,debug=true,realm= MYDOMAIN.COM" <keytab_file_path> For the details of the Kerberos parameters,</keytab_file_path> <keytab_file_path>for example, principal, useKeytab, storeKey,</keytab_file_path> <keytab_file_path>and others, refer to this page. </keytab_file_path> To make the Kerberos configuration work, ensure that you: -Set the storeKey and  isInitiator parameters to true. -Add the parameter  allow_weak_crypto  under  [realms] and [libdefaults] tags in krb5.conf file located at /shared)
LOG_ARCHIVE_DB_URL	jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>
LOG_ARCHIVE_DB_DRIVER_CLASS	oracle.jdbc.OracleDriver
LOG_ARCHIVE_DB_TYPE	Oracle
LOG_ARCHIVE_DB_DIALECT	org.hibernate.dialect.OracleDialect
LOG_ARCHIVE_DB_VALIDATION_QUERY	SELECT 1 from dual
LOG_ARCHIVE_DB_AUTHTYPE	Basic KerberosWithKeyTab KerberosWithServiceAccount
LOG_ARCHIVE_DB_KERBEROS_DB_LOGIN_MODULE_NAME	Set its value to KerberosServer if you want to use Kerberos authentication for the Oracle database.
LOG_ARCHIVE_DB_KERBEROS_CONFIGURATION	-This is applicable only when you're using Kerberos as the authentication type for the Oracle database. -Kerberos authentication is not supported for AIMap microservice. Enter the required Kerberos parameters with their respective values in key-value pairs (comma separated) as shown in the example below: "principal=HTTP/hostname.mydomain. com,useKeyTab=true,keytab<keytab_file_path>,storeKey=</keytab_file_path> <keytab_file_path>true,isInitiator=</keytab_file_path>true,debug=true,realm= MYDOMAIN.COM" <keytab_file_path> For the details of the Kerberos parameters,</keytab_file_path> <keytab_file_path>for example, principal, useKeytab, storeKey,</keytab_file_path> <keytab_file_path>and others, refer to this page. </keytab_file_path> To make the Kerberos configuration work, ensure that you: -Set the storeKey and isInitiator parameters to true. -Add the parameter allow_weak_crypto under  [realms] and [libdefaults] tags in krb5.conf file located at /shared) and set its value to true.
LOG_ARCHIVE_DB_TRANSACTION_ISOLATION	2
QUARTZ_DB_URL	jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>
QUARTZ_DB_DRIVER_CLASS	oracle.jdbc.OracleDriver
QUARTZ_DB_TYPE	Oracle
QUARTZ_DB_DIALECT	org.hibernate.dialect.OracleDialect
QUARTZ_DB_AUTHTYPE	Basic KerberosWithKeyTab KerberosWithServiceAccount
QUARTZ_DB_KERBEROS_DB_LOGIN_MODULE_NAME	Set its value to KerberosServer if you want to use Kerberos authentication for the Oracle database.
QUARTZ_DB_KERBEROS_CONFIGURATION	This is applicable only when you're using Kerberos as the authentication type for the Oracle database. · -Kerberos authentication is not supported for AIMap microservice. Enter the required Kerberos parameters with their respective values in key-value pairs(comma separated)as shown in the example below: <keytab_file_path>"principal=HTTP/hostname.mydomain.</keytab_file_path> <keytab_file_path>com,</keytab_file_path><keytab_file_path>useKeyTab=</keytab_file_path>true,keytab<Keytab_ File_Path>,storeKey=true,isInitiator= true,debug=true,realm=MYDOMAIN. COM" <keytab_file_path>For the details of the Kerberos parameters, for example, principal, useKeytab, storeKey, and</keytab_file_path> <keytab_file_path>others, refer to this page.</keytab_file_path> To make the Kerberos configuration work, ensure that you: -Set the storeKey  and isInitiator parameters to true. -Add the parameter allow_weak_crypto under [realms] and [libdefaults] tags in krb5.conf file located at /shared) and set its value to true.
BACKEND_DB_VALIDATION_QUERY	SELECT 1 from dual
LOG_DB_VALIDATION_QUERY	SELECT 1 from dual
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 from dual
QUARTZ_DRIVER_DELEGATE_CLASS	org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
SPRING_QUARTZ_PROPERTIES_ORG_QUARTZ_JOBSTORE_LOCKHANDLER_CLASS	org.quartz.impl.jdbcjobstore.UpdateLockRowSemaphore
QUARTZ_SELECT_WITH_LOCK_SQL	SELECT * FROM {0}LOCKS WHERE LOCK_NAME = ?
QUARTZ_DB_TRANSACTION_ISOLATION	2

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	oracle+cx_oracle://<host>:<port>/<Backend Database Name>

Static and migration job execution settings

Set the following parameters for static and migration job execution.

Section in the values.yaml	Parameter	Description
global > migration	EXECUTE_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.