OpenEdge Pro2 is a lightweight, configurable tool that provides near real-time replication of an OpenEdge database to Microsoft SQL, Oracle, or another OpenEdge database.

Learn about

Pro2 supports enterprises in delivering the critical business data needed to support analytical and other business intelligence initiatives by replicating specific tables and fields, databases, or multiple databases. All replications facilitated by Pro2 can take place while your transactional database is up and running, removing connectivity limitations, disruptions, and risk to your normal business operations.

With Pro2's web UI you can intuitively configure and monitor your database replications, create new replication processes, and manage bulk loading. To deliver near real-time replication, Pro2 uses OpenEdge Change Data Capture (CDC) for optimal performance with your OpenEdge database.

How it works

Replication triggers or CDC automatically capture all data changes; this means minimal information is written to the queue to identify the updated record.

Next, the multi-threaded replication process retrieves the updated record and the queued data in the replication is moved to the target database. Done in near real-time, the I/O operation is optimized with the updated record residing in cache. Any analysis can be run against current data in a replicated database, leaving the transactional database resources to their normal activities, keeping your data is accurate and secure.

Replication

Pro2 Replication uses a replication table consisting of minimal data and indexing, and a single sequence for process control. No raw data is captured during database record, write, and delete events. However, the replication triggers fire and capture the updated record information to any database replication table as the events take place. A replication table can be in a standalone replication (repl) database or embedded into one of the source OpenEdge databases.

To replicate Pro2 uses a replication processor that cycles through replication records periodically, based on user configuration, and replicates the table data directly to the target database via the OpenEdge DataServer.

All replication data is captured and maintained in the following database tables:
  • ReplControl
  • ReplCustDefs
  • ReplCustFlds
  • ReplDBXRef
  • ReplFieldXref
  • ReplProperties
  • ReplQueue
  • ReplTableXRef
  • ReplThreadControl

Pro2 allows you to configure the time interval between the replication sweeping operations. You can customize the interval in real time according to your needs. For example, every “x” seconds, hourly, twice a day, or daily depending on your specific business problem.

Additionally, you can pause all replications or a specific table replication temporarily to reduce load on the production system during peak timings, such as end-of-quarter processing. You can restart the paused replication at any time. Keep in mind that, while the replication process is suspended, users of the target system do not have access to the records that have been updated in your source OpenEdge database until the replication process is restarted and the replication queue is completely swept.

Architecture

The basis of the replication functionality consists of five primary programs that generate the replication triggers, generate the replication processor functionality, and process the replication records, and a user interface program for monitoring and administering the replication processor and configuration.

LAN or WAN

Pro2 architecture varies over local area network (LAN) or wide area network (WAN). Each configuration, whether WAN or LAN, includes:
  • An OpenEdge source database. There is usually a user application tied to the source database.
  • A database with Pro2 database tables. This is known also known as a replication or repl database.
  • A target database which can be either MS SQL Server, Oracle or an OpeEdge database.

LAN

Pro2 architecture over LAN consists of the following components:
  • A source, OpenEdge, database with a user application is tied to it.
  • A repl database which stores Pro2 database tables.
  • A schema holder database which contains information about the data definitions for one or more databases.
  • A target database which can be either MS SQL Server, Oracle or an OpeEdge database.
Note: As an alternate setup, the repl tables can be embedded directly in the source database.


WAN

When the target database is in a different geographic location than the source OpenEdge database, configure Pro2 to include a Progress Application Server on the source database server in addition to the standard configuration on the Pro2 server.

Instead of running the replication procedures using typical client/server mode connections to the source and repl databases, Pro2 sends requests to PAS for OpenEdge on the database server which returns data to the calling procedure on the Pro2 server.

Note: The Pro2 server must be on the same local area network as the target database server.

The following figure describes how this topic refers to each component of the Pro2 replication configuration:



Pro2 setup process

  1. Installing Pro2 with OpenEdge on your machine
  2. Configuring and deploying the web UI
  3. Designating the source and target database
  4. Mapping and defining table and field relationships for replication