I've got an old 9.1e instance that was never intended to be used with SQL. I've successfully got the JDBC driver talking with Squirrel SQL but I wanted to verify with some experts that I've set this up properly. I do NOT want to impact any of the 4GL clients.
I've used the following two URLs as reference for what I've done so far (I don't think I can post links yet...).
knowledgebase.progress...How-to-set-up-a-secondary-login-broker-for-SQL-92-connections-for-Progress-OpenEdge-database
knowledgebase.progress...How-to-connect-SQuirreL-SQL-Client-to-Progress-OpenEdge-DB
To create the secondary login broker:
Thanks for taking the time to read this! Stay safe out there...
I've used the following two URLs as reference for what I've done so far (I don't think I can post links yet...).
knowledgebase.progress...How-to-set-up-a-secondary-login-broker-for-SQL-92-connections-for-Progress-OpenEdge-database
knowledgebase.progress...How-to-connect-SQuirreL-SQL-Client-to-Progress-OpenEdge-DB
To create the secondary login broker:
- Connected to the AdminServ with Progress Explorer
- Created a new Database (DBName_SQL) alongside of my existing database (DBName)
- Edited the defaultConfig on the new database to add the -m3 server argument.
- Edited the defaultServerGroup under the defaultConfig to be: SQL only, listening on port 8000, 5 servers, 5 clients per server max, 5 clients per server min, 8001 min port, and 8005 max port.
Thanks for taking the time to read this! Stay safe out there...