Versions Compared

Version Old Version 11 New Version Current
Changes made by

Ashhad Alam

Ashhad Alam

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can install Adeptia Connect microservices using Helm Charts. A Helm Chart is a collection of files and templates that describe Kubernetes resources governing the deployment of microservices.

...

Enabling OCI support in the Helm 3 client

Helm 3 supports Open Container Initiative (OCI) for package distribution. Set the HELM_EXPERIMENTAL_OCI in the environment to enable OCI support in the Helm 3 client by running the following command on the Helm CLI.

Code Block
languagecss
themeMidnight
export HELM_EXPERIMENTAL_OCI=1

...

PropertyValue for Azure SQL DatabaseValue for Oracle DatabaseValue for Azure MySQL DatabaseDescription
BACKEND_DB_USERNAME<User defined><User defined><User defined>

Username for your backend database.

If you're using external Secrets, you need not provide a value for this property.

BACKEND_DB_PASSWORD<User defined><User defined><User defined>

Password for your backend database.

If you're using external Secrets, you need not provide a value for this property.

BACKEND_AUTHTYPEBasic
  • Basic
  • Kerberos
Basic

Authentication type for your backend database.

If you're using Kerberos as the authentication type forOracle database, you also need to configure the BACKEND_KERBEROS_DB_LOGIN_MODULE_NAME environment variable.

BACKEND_KERBEROS_DB_LOGIN_MODULE_NAMENot applicable<User defined>Not applicable

Name of the login module.

This is applicable only when you're using Kerberos as the authentication type forOracle database.

This login module name is passed to the jass.config file containing the Kerberos login module parameters that you need to configure. Expand the section below to know how you can configure the login module.

Expand
titleConfiguring the login module
  • Navigate to /shared folder.
  • Open the jaas.config file.
  • Enter the required values for the Kerberos parameters as shown in the example below.
    Image Modified

    Where,
    KerberosServer is the login module name.

    For the details of the Kerberos parameters, for example, principal, useKeytab, storeKey, and others., refer to /wiki/spaces/AC41/pages/15993667.


LOG_DB_USERNAME<User defined><User defined><User defined>

Username for your log database.

If you're using external Secrets, you need not provide a value for this property.

LOG_DB_PASSWORD<User defined><User defined><User defined>

Password for your log database.

If you're using external Secrets, you need not provide a value for this property.

LOG_DB_AUTHTYPEBasic
  • Basic
  • Kerberos
Basic

Authentication type for your log database.

If you're using Kerberos as the authentication type forOracle database, you also need to configure the LOG_DB_KERBEROS_DB_LOGIN_MODULE_NAMEenvironment variable.

LOG_DB_KERBEROS_DB_LOGIN_MODULE_NAMENot applicable<User defined>Not applicable

Name of the login module.

This is applicable only when you're using Kerberos as the authentication type forOracle database.

This login module name is passed to the jass.config file containing the Kerberos login module parameters that you need to configure. Expand the section below to know how you can configure the login module.

Expand
titleConfiguring the login module
  • Navigate to <Adeptia-Installation-Folder >/AdeptiaServer/ServerKernel/etc/shared folder.
  • Open the jaas.config file.
  • Enter the required values for the Kerberos parameters as shown in the example below.
    Image Modified

    Where,
    KerberosServer is the login module name.

    For the details of the Kerberos parameters, for example, principal, useKeytab, storeKey, and others., refer to /wiki/spaces/AC41/pages/15993667.


LOG_ARCHIVE_DB_PASSWORD<User defined><User defined><User defined>

Password for your log archive database.

If you're using external Secrets, you need not provide a value for this property.

LOG_ARCHIVE_DB_USERNAME<User defined><User defined><User defined>

Username for your log archive database.

If you're using external Secrets, you need not provide a value for this property.

LOG_ARCHIVE_DB_AUTHTYPEBasic
  • Basic
  • Kerberos
Basic

Authentication type for your log archive database.

If you're using Kerberos as the authentication type forOracle database, you also need to configure the LOG_ARCHIVE_DB_KERBEROS_DB_LOGIN_MODULE_NAME environment variable.

LOG_ARCHIVE_DB_KERBEROS_DB_LOGIN_MODULE_NAMENot applicable<User defined>Not applicable

Name of the login module.

This is applicable only when you're using Kerberos as the authentication type forOracle database.

This login module name is passed to the jass.config file containing the Kerberos login module parameters that you need to configure. Expand the section below to know how you can configure the login module.

Expand
titleConfiguring the login module
  • Navigate to <Adeptia-Installation-Folder >/AdeptiaServer/ServerKernel/etc/shared folder.
  • Open the jaas.config file.
  • Enter the required values for the Kerberos parameters as shown in the example below.

    Image Modified

    Where,
    KerberosServer is the login module name.

    For the details of the Kerberos parameters, for example, principal, useKeytab, storeKey, and others., refer to /wiki/spaces/AC41/pages/15993667.


QUARTZ_DB_USERNAME<User defined><User defined><User defined>

Username for your quartz database. This value will be the same as that for the backend database.

If you're using external Secrets, you need not provide a value for this property.

QUARTZ_DB_PASSWORD<User defined><User defined><User defined>

Password for your quartz database. This value will be the same as that for the backend database.

If you're using external Secrets, you need not provide a value for this property.

QUARTZ_DB_AUTHTYPEBasic
  • Basic
  • Kerberos
Basic

Authentication type for your quartz database.

If you're using Kerberos as the authentication type forOracle database, you also need to configure the QUARTZ_DB_KERBEROS_DB_LOGIN_MODULE_NAMEenvironment variable.

QUARTZ_DB_KERBEROS_DB_LOGIN_MODULE_NAMENot applicable<User defined>Not applicable

Name of the login module.

This is applicable only when you're using Kerberos as the authentication type forOracle database.

This login module name is passed to the jass.config file containing the Kerberos login module parameters that you need to configure. Expand the section below to know how you can configure the login module.

Expand
titleConfiguring the login module
  • Navigate to <Adeptia-Installation-Folder >/AdeptiaServer/ServerKernel/etc/shared folder.
  • Open the jaas.config file.
  • Enter the required values for the Kerberos parameters as shown in the example below.
    Image Modified

    Where,
    KerberosServer is the login module name.

    For the details of the Kerberos parameters, for example, principal, useKeytab, storeKey, and others., refer to /wiki/spaces/AC41/pages/15993667.


BACKEND_DB_URL

jdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Backend Database Name>

jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>

jdbc:mysql://<hostName>:<portNumber>/<DBName>?useSSL=trueBackend database name and its URL. Currently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified.

BACKEND_DB_DRIVER_CLASS

com.microsoft.sqlserver.jdbc.SQLServerDriver

oracle.jdbc.OracleDriver

com.mysql.cj.jdbc.DriverDriver class name based on the backend db. Do not change the value for this pre-defined property.
BACKEND_DB_TYPE

SQL-Server

Oracle MySQLCurrently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. Do not change the value for this pre-defined property.
BACKEND_DB_DIALECT

org.hibernate.dialect.SQLServer2008Dialect

org.hibernate.dialect.Oracle12cDialectorg.hibernate.dialect.MySQLDialectCurrently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. Do not change the value for this pre-defined property.
BACKEND_DB_TRANSACTION_ISOLATION

1

81Transaction isolation level in database.
BACKEND_DB_VALIDATION_QUERYSELECT 1SELECT 1 from dualSELECT 1Query that can be used by the pool to validate connections before they are returned to the application.
LOG_DB_DRIVER_CLASS

com.microsoft.sqlserver.jdbc.SQLServerDriver

oracle.jdbc.OracleDriver

com.mysql.cj.jdbc.DriverDriver class name based on the log db. Do not change the value for this pre-defined property.
LOG_DB_URL

jdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Log Database Name>

jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>

jdbc:mysql://<hostName>:<portNumber>/<DBName>?useSSL=trueLog database name and its URL. Currently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified.
LOG_DB_TYPE

SQL-Server

OracleMySQLCurrently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. Do not change the value for this pre-defined property.
LOG_DB_DIALECT

org.hibernate.dialect.SQLServer2008Dialect

org.hibernate.dialect.Oracle12cDialect

org.hibernate.dialect.MySQLDialectCurrently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. Do not change the value for this pre-defined property.
LOG_DB_TRANSACTION_ISOLATION

1


81Transaction isolation level in database.
LOG_DB_VALIDATION_QUERYSELECT 1SELECT 1 from dualSELECT 1Query that can be used by the pool to validate connections before they are returned to the application.
LOG_ARCHIVE_DB_URL

jdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Log Archive Database Name>

jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>

jdbc:mysql://<hostName>:<portNumber>/<DBName>?useSSL=trueLog archive database name and its URL. Currently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified.

LOG_ARCHIVE_DB_DRIVER_CLASS

com.microsoft.sqlserver.jdbc.SQLServerDriver

oracle.jdbc.OracleDriver

com.mysql.cj.jdbc.DriverDriver class name based on the log archive db. Do not change the value for this pre-defined property.
LOG_ARCHIVE_DB_TYPE

SQL-Server

OracleMySQLCurrently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. Do not change the value for this pre-defined property.
LOG_ARCHIVE_DB_DIALECT

org.hibernate.dialect.SQLServer2008Dialect

org.hibernate.dialect.Oracle12cDialect

org.hibernate.dialect.MySQLDialectCurrently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. Do not change the value for this pre-defined property.
LOG_ARCHIVE_DB_TRANSACTION_ISOLATION

1


81Transaction isolation level in database.
LOG_ARCHIVE_DB_VALIDATION_QUERYSELECT 1SELECT 1 from dualSELECT 1Query that can be used by the pool to validate connections before they are returned to the application.

QUARTZ_DB_URL

jdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Backend Database Name>

jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>

jdbc:mysql://<hostName>:<portNumber>/<DBName>?useSSL=trueQuartz database name and its URL. Currently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. This value will be the same as that for the backend database.
QUARTZ_DB_DRIVER_CLASS

com.microsoft.sqlserver.jdbc.SQLServerDriver

oracle.jdbc.OracleDriver

com.mysql.cj.jdbc.DriverDriver class name based on the quartz db. This value will be the same as that for the backend database.
QUARTZ_DB_TYPE

SQL-Server

OracleMySQLCurrently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. Do not change the value for this pre-defined property.
QUARTZ_DB_DIALECT

org.hibernate.dialect.SQLServer2008Dialect

org.hibernate.dialect.Oracle12cDialect

org.hibernate.dialect.MySQLDialectCurrently, the MS Azure SQL, Oracle, and Azure MySQL databases are certified. Do not change the value for this pre-defined property. This value will be the same as that for the backend database.
QUARTZ_DB_TRANSACTION_ISOLATION

1


81Transaction isolation level in database.
QUARTZ_DB_VALIDATION_QUERYSELECT 1SELECT 1 from dualSELECT 1Query that can be used by the pool to validate connections before they are returned to the application.

...

Uninstalling Adeptia Connect

If you wish to uninstall the application, run the following command.

Code Block
languagecss
themeMidnight
helm uninstall <adeptia-connect>

...

Info
If you've configured external Secrets, you need to manually delete the Secrets and its deployment after you uninstall the application.