Kbase 18051: Configuring OpenLink for use with Apptivity -debugging tips
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/24/1998 |
|
Configuring OpenLink for use with Apptivity -debugging tips
This kbase addresses various debugging techniques that can be used
when configuring the OpenLink multi-tiered driver to be used with
Apptivity
When you experience problem making a database connection, it
is a good idea to turn on the debug option. This can be done by
starting up the request broker at a command prompt (DOS box) by
issuing either of the following commands from the
<openlink-install-dir>/bin:
oplrqb -dv
or
oplrqb +debug
The broker will appear at the bottom of the screen as an icon.
Using this option will output the maximum amount of information to
the OpenLink Request Broker window.
If you have installed Progress on a network drive, or a drive other
than the C drive you may need to move the following files to a DLC
directory on the C drive:
c:\dlc\bin\progress.ini
c:\dlc\convmap.cp
c:\dlc\promsgs
c:\dlc\startup.pf
c:\dlc\progress.cfg
It is crucial that all Progress.ini files on your machine have the DLC
etc variables pointing to the location on the C drive. You would then
change your session rule book , the oplrqb.ini, to have the following:
[Environment PROGRESS82A]
DLC = C:\DLC
Path = C:\DLC\BIN;C:\WINNT\System32
PROCFG = C:\DLC\progress.cfg
PROMSGS = C:\DLC\promsgs
TABLEVIEW = C:\mydb\prgsdb.dat ;The location of the tableview .dat
;TABLEVIEW_QUALIFIER = Y
;DEADLOCK_TIMEOUT = 60 ; Seconds to wait for lock to release
;INSERT_LOGICAL = Y
;UPDATE_LOGICAL = Y
;MIN_FIELD_LEN =
Test the Progress-OpenLink connection using the C++ demo 32 bit
that is provided with the OpenLink driver. If you are able to connect
there you should be able to connect from Apptivity. When connecting
from Apptivity if you don't see any tables when you try try to create
a data source check the size of the tableview .dat file that you are
specifying in your oplrqb.ini file. There is currectly an issue with
the setup.p program that creates this file. If you specify a
directory other than the Progress working directory when you run
setup.p, the *.pf is created in the correct directory but two
copies of the *.dat file are created. The correct one is created in
the Progress working directory and not the directory that was
designated at run-time. The directory that was designated at runtime
contains a file of zero bytes. Copy the correct copy to the location
specified by the TABLEVIEW parameter in oplrqb.ini and then
you should be able to connect!
When even you make any changes to the oplrqb.ini file you need to
shut down and restart the Request Broker for those changes to
take effect.
PES 06/24/98