Write-behind configuration guide
This guide shows you how to configure write-behind target connections.
Write-behind target connections are the connections established between the RDI instance and the target database in a write-behind scenario. They replicate the changes captured in an RDI-enabled Redis Enterprise database to the target database.
The connections must be configured in the
config.yaml before deploying any jobs and must follow one of the formats shown below. Multiple connections can be specified in the
connections section at the same time.
For relational datastores:
connections: my-sql-datastore: type: <db-type> # mysql | oracle | postgresql | sqlserver host: <db-host> # IP address or FQDN of a database host and instance port: <db-port> # database port database: <db-name> # name of the database user: <db-user> # database user password: <db-password> # database password # connect_args: # optional connection parameters passed to the driver - these are driver specific # query_args: # optional parameters for SQL query execution - typically not required for RDI operation
For non-relational datastores:
connections: my-nosql-datastore: type: <db-type> # cassandra hosts: <db-hosts> # array of IP addresses or host names of a datastore nodes port: <db-port> # database port database: <db-name> # name of the database user: <db-user> # database user password: <db-password> # database password
Microsoft SQL Server
Microsoft SQL Server supports different authentication mechanisms (SQL Server Authentication, Integrated Windows Authentication) and protocols (NTLM, Kerberos). RDI can use all of them; however, systems that use Kerberos may require some additional configuration.
To enable RDI to work with a SQL Server database, check that the account you specify was assigned at least the
SQL Server authentication
To use SQL Authentication mode, create a SQL user with login credentials and then assign the necessary permissions for the target database to that user.
connections: mssql2019-sqlauth: type: sqlserver host: ip-10-0-0-5.internal port: 1433 database: rdi_wb_database user: rdi_user password: secret
To use Windows Authentication mode, you need to create a Windows or AD account that has the necessary permissions to access the target database and is able to log into SQL Server. The Linux machine hosting RDI can be configured to support the NTLM authentication protocol.
connections: mssql2019-ntlm: type: sqlserver host: ip-10-0-0-5.internal port: 1433 database: rdi_wb_database user: MYDOMAIN\rdi_service_account # company-domain\service-account password: secret # NTLM requires to provide a password
Note: User must be specified with the domain name for Windows Authentication to work
After you configure the RDI connection and deploy the write-behind job, run the following SQL query to have the operator check if RDI is using the expected authentication mechanism and protocol. Note: This operation may require
SELECT session_id, auth_scheme FROM sys.dm_exec_connections;
The results indicate which
auth_scheme is used by each session and may take values