Code and tools for creating a connection between ABL applications and other language systems or databases
An experiment with Apache MQ
Often I have needed to integrate Progress Databases with other applications. These applications have a horrible time talking to Progress. Yes, I know, “But, but, but there is the ODBC and JDBC connections!”
Well, that is nice if you are on Windows. I am on UNIX or some non-Progress supported operating system or using some form of middle-ware (read that as PHP, Perl, etc.) to make the integration with. Sometimes it has ODBC, sometimes it doesn't.
Sometimes it is a device that needs to interact with Progress DBs and the infrastructure just is not there.
Use of CLI tools for exporting of Progress schema and data to MySQL with Amduus modifications to Mark Newnham's Pro2myv2 Open Source tool.
The open source tool pro2myv2 has been modified by Amduus to be more UNIX oriented. (It originally was GUI oriented and can still be used in a GUI environment.) This way it can be used from a non-GUI environment and from cron for automatic data exporting and loading from Progress to MySQL.
Attn: This tool requires a developers or query license for the version of Progress it is being used on.
Pro2My is a simple group of PROGRESS source code routines that can be run against any PROGRESS database greater than version 6 to produce a series of files containing MySQL format SQL statements. These files can be used to produce a MySQL database that is a mirror of the PROGRESS database. The routines provide a method of:
Interface for Progress 4GL to query mysql databases.
Functions work like they do in php.
code: browse the code in the Subversion repository http://www.oehive.org/amduus/pro2mysql/
contributed by Matthew Lang
pro2jdbc - Progress to JDBC interface
A set of 4Gl routines to migrate schema and data from a Progress DB to a PostgreSQL database.
This project is for the maintenance and support of John Green's "jpjvm" DLL, which loads a JVM into a Progress/OpenEdge session.
This zip file contains utilities and documents to aid the transformation form the V9.1C Progress/400 DataServer to the OpenEdge DataServer for ODBC. The OpenEdge DataServer for ODBC is not a direct product replacement for the Progress/400 DataServer, which retired in September 2004. The OpenEdge DataServer for ODBC provides generic connectivity to various data sources (including DB2 for Windows and the AS/400) via the ODBC open standard protocol. Although the ODBC protocol is in alignment with IBMs UDB2 RDBMS strategy (SQL only access) the generic nature of the OpenEdge DataServer for ODBC means that that specific RDBMS features related to functionality and performance can not be utilized and therefore performance (as compared to the Progress/400 DataServer) is going to be an area of the transformation process that will require special attention. The embedded whitepaper titled DB2 Accessibility Whitepaper May 2006 is currently a draft edition and will be updated overtime.