The Progress OpenEdge Connector
Archive Progress OpenEdge databases at the point of application retirement or migration. Extract decades of transactional history from OpenEdge-backed ERP and vertical applications, in open format.
🌟 Featured in Gartner® Hype Cycle™ for Data Management
Connectors
Data Governance
Enterprise Clients
Talk to a Connector Expert
Progress OpenEdge Archiving, Done Right
Archon’s Progress OpenEdge Connector extracts tables, schemas, and historical data from Progress OpenEdge (formerly Progress 4GL/ABL) database environments, and archives them into open Parquet/Delta Lake format. Built for engineering and compliance teams retiring OpenEdge-backed ERP systems, vertical applications in healthcare and manufacturing, and legacy LOB platforms that have reached end-of-life.
Progress OpenEdge powers a significant number of legacy vertical applications, particularly in healthcare information systems, manufacturing ERP, and financial services platforms built in the 1990s and 2000s. When those applications are replaced, the underlying OpenEdge database carries years of transactional history with compliance obligations that persist well beyond the application lifecycle.
- JDBC (Progress DataDirect JDBC driver) extraction from Progress OpenEdge 10.x, 11.x, 12.x
- Tables, schemas, sequences, audit tables, transactional history, metadata captured with full schema metadata
- Schema structure, indexes, and stored procedure metadata preserved
- Cross-table query via Archon Analyzer, no Progress OpenEdge runtime post-archive
- HIPAA, FDA 21 CFR Part 11, SOX, GDPR retention policy support
Capabilities
Everything You Need for Progress OpenEdge Data Operations
Full Schema and Historical Data Extraction
Archon extracts all Progress OpenEdge tables, views, and schema structures, preserving relational integrity and column-level metadata. No custom extraction scripts or database administrator involvement required.
Application Retirement and License Cost Elimination
Progress OpenEdge instances retained solely for compliance data access are decommissioned after Archon archives the historical data. Licensing and infrastructure costs are eliminated while full regulatory compliance is maintained.
Database Migration Historical Data Preservation
Application migrations from Progress OpenEdge to modern databases use Archon to archive historical data before cutover, reducing migration scope and satisfying compliance retention on historical records independently.
Compliance Audit Trail Support
Audit tables, transaction logs, and schema-level metadata preserved in the Archon archive satisfy HIPAA, FDA 21 CFR Part 11, SOX, GDPR compliance requirements, accessible via Archon Analyzer without Progress OpenEdge infrastructure.
Use Cases
How Enterprises Use the Progress OpenEdge Connector
01 Application Retirement
Legacy applications built on Progress OpenEdge are retired when organizations modernize. Archon archives the underlying database: schema, data, and audit records, before shutdown, ensuring compliance access without the legacy infrastructure.
02 Database Migration Historical Archiving
Migrations from Progress OpenEdge to modern databases use Archon to archive complete historical data before cutover, preserving the full operational record in open Parquet format, independent of the migration.
03 License and Infrastructure Cost Elimination
Progress OpenEdge instances running solely for compliance access are decommissioned after Archon archives the data. Licensing, support, and infrastructure costs are eliminated while regulatory compliance is maintained.
04 Compliance Audit and eDiscovery Support
Compliance audits and legal proceedings requiring Progress OpenEdge records from prior years are fulfilled through Archon Analyzer, without database administrator involvement or a live Progress OpenEdge instance.
Technical Specifications
| Specification | Details |
|---|---|
| Connection Method | JDBC (Progress DataDirect JDBC driver) |
| Supported Versions | Progress OpenEdge 10.x, 11.x, 12.x |
| Data Scope | Tables, schemas, sequences, audit tables, transactional history, metadata |
| Output Format | Parquet, Delta Lake, Avro, XML, CSV, TXT, TSV, Excel |
| Metadata Handling | Schema structure, indexes, constraints, column definitions |
| Transformation Rules | 1,000+ built-in; Progress OpenEdge data type normalization supported |
| Retention Management | HIPAA, FDA 21 CFR Part 11, SOX, GDPR retention schedules |
| Legal Hold | Database and table-level hold orchestration with audit trail |
| Deployment | On-premises · Cloud (AWS, Azure, GCP) · Hybrid |
| Security & Compliance | TLS 1.3 in transit · AES-256 at rest · WORM |
How It Works
Up and Running in 4 Steps
01
Connect to Progress OpenEdge
Authenticate via JDBC (Progress DataDirect JDBC driver) to Progress OpenEdge 10.x, 11.x, 12.x. Archon auto-discovers all databases, schemas, tables, views, and stored procedure definitions. 02
Map & Configure
Define schema and table scope, data type normalization rules, and jurisdiction-specific retention schedules. Configure PII masking for GDPR compliance where applicable. 03
Validate & Preview
Run a dry-run against sample Progress OpenEdge databases. Quality report flags null primary keys, data type normalization issues, and schema anomalies before full extraction. 04
Archive & Monitor
Execute full extraction. Cryptographic hashes and trusted timestamps applied per table. Data searchable via Archon Analyzer immediately on ingestion.FAQ
Common Questions About the Progress OpenEdge Connector
- 1. Does Archon support Progress OpenEdge without requiring DBA involvement?
Yes. Archon uses read-only JDBC (Progress DataDirect JDBC driver) extraction, no DBA scripts, administrative privileges, or custom extraction code required.
- 2. Can Archon archive Progress OpenEdge without impacting live application performance?
Yes. Archon uses read-only connections with configurable parallelism and throttle settings with zero production impact during extraction.
- 3. How does Archon handle Progress OpenEdge-specific data types during archiving?
Archon applies 1,000+ built-in transformation rules to normalize Progress OpenEdge-specific data types into open Parquet-compatible formats with metadata preservation.
- 4. Is archived Progress OpenEdge data queryable without the Progress OpenEdge runtime?
Yes. Archon archives to open Parquet/Delta Lake format, queryable via Archon Analyzer, Apache Spark, Amazon Athena, or any Lakehouse query engine without Progress OpenEdge.
- 5. Does archived Progress OpenEdge data satisfy GDPR and compliance retention requirements?
Yes. Archon's WORM-immutable Progress OpenEdge archive satisfies GDPR Article 5, and applicable sector-specific retention mandates.
Ready to decommission Progress OpenEdge while keeping every record accessible and audit-ready?
Schedule a free consultation with an Archon specialist to evaluate your archiving and retirement strategy. No commitment. Expert response within 24 hours.
