Progress® OpenEdge® Pro2™ is a data replication solution that provides easy access to data from your OpenEdge applications. OpenEdge Pro2 data replication solution removes connectivity limitations without disruption to normal business operations or risk to the transactional database.
With OpenEdge Pro2 data replication you create a channel for transferring Progress OpenEdge data into a Microsoft SQL Server, Oracle or a target OpenEdge database for efficient reporting and analysis. As your data is updated, it is replicated to your desired database in near real-time. With your Progress OpenEdge database and target databases virtually in sync, you can use your third-party reporting solutions for up-to-date reports and business intelligence.
By leveraging Progress OpenEdge Change Data Capture (CDC), OpenEdge customers and partners can deliver low-latency, near real-time replication of that data to support not just traditional descriptive analytics, but also predictive analytics, AI-driven decisions, and time-sensitive IoT events.
Pro2 offers a new, modern UX dashboard and new UX Replication Wizard, ensuring you’ll be prepared for increasing demands for data access with expanded functionality and scalability for future growth. The UX dashboard improves efficiency and productivity, and allows proactive monitoring of performance and analytics, all while delivering a beautiful and intuitive experience that expands the product’s functionality while representing the most evolved version to date.
Increase Efficiency With an Intuitive UI
Scale for Growth
Automated Migration Steps
Upgrade pathways from Pro2 5.x to 6.x versions are made easier in Pro2 6.4. This enables a successful migration to Pro2 6.x with minimal manual intervention. .
Create Better Queue and Thread Reports
In Pro2 6.4, administrators can better manage the replication environments with tables by thread, or by age of thread.
Replication triggers or Change Data Capture 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, all while feeling confident your data is accurate and secure.