Status: Verified
GOAL:
How to connect to a Progress database from Actuate Developer Workbench using SQL89
FACT(s) (Environment):
Actuate
FIX:
1. Prepare the Progress Environment:The Progress environment must be prepared before attempting to connect to the Developer Workbench.
For Windows Operating Systems environment variables must be specified in the following manner: Right-click on My Computer -> Choose Properties -> Choose the Environment tab. Define each environment variable in this screen.
a. On the CLIENT system set the following environment variables:
DLC=%Path to Progress Install
PROCFG=%DLC%\\progress.cfg
PROMSGS=%DLC%\\promsgs
PATH=C:\\DLC;C:\\DLC\\BIN;%PATH%
b. On the SERVER machine set the following environment variables:
Unix systems:
PROOIBRK=<complete path>/dlc/bin/_prooibk
PROOIDRV=<complete path>/dlc/bin/_prooidv
Windows systems:
PROOIBRK=C:\\DLC\\BIN\\OIBRKR32.EXE
PROOIDRV=C:\\DLC\\BIN\\OIDRVR32.EXE
VMS systems:
DEFINE PROOIBRK BIN:_PROOIBK.EXE
DEFINE PROOIDRV BIN:_PROOIDV.EXE
2. Ensure the file ESQL32.DLL is installed on the CLIENT machine in %DLC%\\bin directory.
3. Add a TCP entry in the SERVICES file for the OIB and Progress Database on both the CLIENT and SERVER machines.
4. Start the Progress Database and the Progress OIB:
Command-line parameters are for starting a Progress database and the Progress Open Interface Broker on the SERVER machine.
The -SV parameter must be the first parameter when starting the OI Broker. Verify the broker has started correctly by check the prooidrv.lg in the directory where the broker was started.
UNIX:
proserve -db <database-name> -S <db-port> -N <protocol> -H <hostname>
prooibrk -SV -S <broker-port> -N <protocol> -H <hostname>
Windows:
_proserve -db <database-name> -S <db-port> -N <protocol> -H <hostname>
oibrkr32.exe -SV -S <broker-port> -N <protocol> -H <broker-host>
VMS:
prog/multi=start/service=<db-port>
etwork=tcp/host=<hostname> -<database-name>
prog/oib=start/host=<db-host>
etwork=tcp/service=<broker-port>
5. Connect to a Progress DB from Developer Workbench:
When Client Networking is installed on the SERVER machine you can choose to use either the self-service client connection, or a network connection.
Self-Service client connection:
Example: Databaselist: -db <database-name>
N.etwork Client connection:
Example: Databaselist: -db <physical-database-name> -S <db-port> -N <protocol> -H <db-host>
As long as Client Networking is installed on the SERVER machine, the database(s) do not have to be located on the same machine as the broker.
6. To connect to more than one database:
Example: databaselist:-db <physical-database1-name> -S <db1-port> -N <protocol> -H <db1-host>
-db <physical-database2-name> -S <db2-port> -N <protocol>-H <db2-host> etc.
7. Database Security: Optionally, the following two parameters can be added to the DatabaseList if Progress security is in place:
-U <username> (user name registered to Progress Security)
-P <password> (password for aforementioned user) One can log into multiple databases (using different user name/password combinations if desired) and subsequently accomplish cross-database joins, select statements, etc. using multiple -db sections.
Example: -db sports -H ahost -S asvc -U aname -P apass -db inventory -S bsvc -U bname -P bpass If the Username or Password box is filled on the connection box, both the Username and Password will be attached to each -db in the Database List automatically, using the -U and -P parameters. For example, if one had the following defined:
DatabaseList: -db adb -H ahost -S asvc -db bdb -H bhost -S bsvc
Username: me
Password: apass
The DatabaseList internally will be sent as:
-db adb -H ahost -S asvc -U me -P apass -db bdb -H bhost -S bsvc -U me -P apass
8. OPTIONAL OTHER PARAMETERS:
Dllpath: ESQL32.DLLStartUpParameters: -SV -S <broker-port> -N <protocol> -H <broker-host> .