The Data Replicator service requires a control database in which to store information about sources, destinations, and replication subscriptions.
The SQDR Configuration wizard application is used to
Specify the credentials and connection for the control database
Modify the Windows Service (if desired)
Enable and configure Role Based Access Control (RBAC) and logging
You can use either IBM Db2 for LUW or SQL Server for the control database, which can be local or remote to the service. and access it using either a connection string or an ODBC DSN.
We recommend using a connection string, as described in the Quick Start Guides for SQDR and SQDR Plus.
The choice of Db2 vs SQL Server is dependent on your environment and your goals. If SQDR is installed on the same system as SQDR Plus (combined tier scenario), we recommend using the local Db2 LUW that is installed for use by SQDR Plus.
SQDR Configuration can be used for configuring SQDR on a local or remote system. To configure the SQDR service on a Linux system, run SQDR Configuration on a Windows system.
To manage remote SQDR systems from a workstation that is not running the SQDR service, StarQuest supplies a special installer that contains only the management applications. Do not use this installer on a system where the full SQDR product is installed.
When configuring a remote system, the system running SQDR Configuration requires access to the control database system; after completing SQDR Configuration, the resulting sqdr.properties file is copied to the system running the SQDR service.
SQDR Configuration is typically used only during initial installation of SQDR and when needed to upgrade control tables after a major update. It may also be used to modify Role Based Access Control (RBAC) and logging settings.