Welcome to your guide!

Real-Time Data Replication Test Drive

Defining Locations (Connections)

You will be replicating data between three systems:

1. A remote Oracle system is the source

2. A remote MariaDB database on a different server as a target

3. A local PostgreSQL database

Let’s start with the connection to the Oracle Database that you will use as the source during this trial.

Location Configuration for Remote Oracle Database

1. Locate the node Location Configuration in the tree on the left-hand side of the window.

2. Right click on Location Configuration to see the context menu (pop-up box) then select New Location.

Right mouse click (Control + click on a Mac, Mac users may need secondary right click enabled in their mouse settings).

3. In the Location field and as a name for this location, enter orcl

4. In the Description field: enter sourcedatabase

5. Check the box Connect to HVR on remote machine.

6. For Node enter ec2-source

7. Port can be left as the default 4343

8. Login should be sourceuser

9. Password is SourceSecret

10. Check the box for /SslRemoteCertificate.

11. Using the box next to the blank field by /SslRemoteCertifidate, click on it to browse for the local certificate source.pub_cert.

12. Select source.pub_cert.

The agent on the source is configured to use encryption and without the unique certificate there is no way to communicate with the listener.

More on this topic

HVR uses the concept of Location Configuration to define the connection to the technologies you replicate data between. Types of locations include databases, file systems, Software as a Service (SaaS) packages, and data streaming technologies like Kafka. The Location Configuration contains the connection credentials regardless whether the location will be used as a source, as a target, or both.

The list of technologies under Class shows all technologies supported directly by HVR as a destination for data replication. The database technologies at the top of the list until and including HANA, are also supported as a source for log-based Change Data Capture (CDC).

File systems like S3, HDFS or the Azure file systems, as well as Kafka, support multiple different formats for integration including Parquet, Avro, JSON and CSV, and file systems can also be used as a source for moving files around or loading CSV files into database tables. HVR also supports plugins that can be customized for any destination technology, some of which are provided out-of-the-box as examples.

13. Select Oracle from the Class list. This is to define the Database Connection information for the Oracle Database.

14. Use the Browse button to the right of ORACLE_HOME to browse for the location of the ORACLE_HOME on the remote system. ORACLE_HOME on the source is in /u01/app/oracle/product/11.2.0/xe
For ORACLE_SID, use XE. (you will need to click through several folders) Once you get to XE, click open to select this file.

(Using this button is also a good validation for the connect information to the HVR agent at the top of the dialog.)

15. Enter tpcc in the  User field box.

16. Password is hvr.

17. Click Test Connection to ensure the connection works and go back to correct any information in case it does not.

18. Click OK on the New Location dialog if the connection to the Oracle Database succeeds.

More on this topic

HVR provides a lot of flexibility for connectivity to the Oracle Database:

  • For an Oracle RAC Database, HVR can connect to an agent through the SCAN listener which allows for high availability in case a node fails.
  • Instead of reading directly from the primary database HVR can perform its Log-Based CDC from a physical standby database, either an Active Data Guard target, or a read-only physical standby database.

Log-Based CDC can also be performed using a so-called Archive Log Only approach that only mines archived redo logs. Such Log-Based CDC can be performed on a different server that is not the primary and not even a standby database server, but of course there is extra latency waiting for the redo log to be archived.

2. Location Configuration for Remote MariaDB Database

To connect to MariaDB running on server ec2-target you will use similar steps to the ones you performed for the connection to the Oracle Database.

1. Right click on the node Location Configuration in the tree, to select New Location.

2. Use mdb for Location and provide a description.

3. Check the box to Connect to HVR on remote machine.

4. Enter ec2-target for Node.

5. Port is 4345.

6. Login is targetuser.

7. Password is TargetSecret.

8. Check the box for /SslRemoteCertificate.

9. Use the browse button on the right to select the certificate target.pub_cert.

10. To define the connection to MariaDB on the server ec2-target select the MySQL/MariaDB/Aurora in the Class list. Then specify:

11. Node is localhost.

12. Port is MariaDB’s default port, 3306.

13. Database is mdbtgt.

14. User is targetuser.

15. Password is TargetSecret.

16. Use the button to Test Connection

17. With a successful connection click OK to continue. Should the connection fail, go back to correct any mistakes.

More on this topic

The connectivity between HVR installations is configured using a remote listener process. The connection uses TCP/IP, optionally encrypted, and can run on any port that is not in use on the server and opened up in the firewall for a remote connection from the hub.

3. Location Configuration for Local PostgreSQL Database

The Location Configuration for the PostgreSQL Database that will be used as a target requires relatively little information.

1. Right click on the node Location Configuration in the tree, to select New Location.

2. Use pg for Location, and enter a description.

3. Database is set to pgtgt.

4. Click Test Connection to ensure the connection is successful.

5. Click OK to continue.

More on this topic

In this test drive scenario, we do not provide any information to connect to an HVR agent since the connection to PostgreSQL is local from the perspective of the hub. With the hub local on this server and a PostgreSQL repository database, the Class selection defaults to PostgreSQL/Aurora.

Test drive
Contact us