Enabling Access to the Database Servers v6.2

The following sections describe configuration steps required to use xDB Replication Server on various types of database servers.

The following section describes the steps to enable access to Oracle. See Section Enabling Access to SQL Server for enabling access to SQL Server.

No special steps are required to enable access to a Postgres database server.

Enabling Access to Oracle

An Oracle JDBC driver jar file such as, ojdbc7.jar, must be accessible to the Java virtual machine (JVM) on the host running the publication server and the subscription server. If the publication server and subscription server are running on separate hosts, the Oracle JDBC driver must be accessible to the JVM on each host. Oracle JDBC driver version ojdbc7 or later must be used.

Step 1: Download the Oracle JDBC driver, for example, ojdbc7.jar, from the Oracle download site to the host that will be running the publication server.

Step 2: Copy file ojdbc7.jar to the directory XDB_HOME/lib/jdbc.

$ su root
Password:
$ cd /usr/edb/xdb/lib/jdbc
$ cp /home/user/Downloads/ojdbc5.jar .
$ ls -l
total 4032
-rw-rw-r-- 1 root root  355655 Jan 25 02:38 edb-jdbc14.jar
-rw-rw-r-- 1 root root  716209 Jan 25 02:38 edb-jdbc17.jar
-rw-rw-r-- 1 root root  317816 Jan 25 02:38 jtds-1.3.1.jar
-rw-r--r-- 1 root root 2091137 Jan 28 16:45 ojdbc5.jar
-rw-rw-r-- 1 root root  642809 Jan 25 02:38 postgresql-9.4-1201.jdbc4.jar

Step 3: If the subscription server is running on a different host than the publication server, repeat steps 1 and 2 for the subscription server host.

Enabling Access to SQL Server

The jTDS JDBC driver jar file jtds-1.3.1.jar must be accessible to the Java virtual machine (JVM) on the host running the publication server and the subscription server. If the publication server and subscription server are running on separate hosts, the jTDS JDBC driver must be accessible to the JVM on each host.

When you install xDB Replication Server, the jtds-1.3.1.jar file is placed in the directory XDB_HOME/lib/jdbc so there is no manual configuration needed for this requirement.

Step 1: Be sure SQL Server Authentication mode is enabled on your SQL Server database engine. SQL Server Authentication mode allows the use of SQL Server logins such as the built-in system administrator login, sa.

Using the default settings for SQL Server installation, only Windows Authentication mode is enabled, which utilizes the accounts of the Windows operating system for authentication.

In order to permit SQL Server Authentication mode, you must change the authentication mode to Mixed Mode Authentication, which permits both Windows Authentication and SQL Server Authentication.

This can be done using SQL Server Management Studio. Refer to the appropriate SQL Server documentation for using SQL Server Management Studio.

Step 2: Be sure SQL Server is accepting TCP/IP connections. In the SQL Server Configuration Manager, under SQL Server Network Configuration, be sure the TCP/IP protocol for the SQL Server instance is set to Enabled. The typical, default SQL Server instance names are MSSQLSERVER or SQLEXPRESS.

Step 3 (Required only for a SQL Server publication database): Be sure SQL Server Agent is enabled and running. SQL Server Agent is a Windows service that controls job scheduling and execution with SQL Server.

xDB Replication Server uses SQL Server Agent for certain operations such as for scheduled shadow table history cleanup (see Section Scheduling Shadow Table History Cleanup).

SQL Server Agent can be started by using SQL Server Configuration Manager. Refer to the appropriate SQL Server documentation for using SQL Server Configuration Manager.

• On this page
• Enabling Access to Oracle
• Enabling Access to SQL Server