You are currently reviewing an older revision of this page.
the listeners have not been started
Make sure Exor listeners are not running. Start GRI9998 form, enter Repeat Count = 3 and Sleep Time 3, and
run this form. On Spooled Output tab you will see an output. If it is like ‘GRI9998 : Testing GRI Server / Listener # ’ , it means that Exor listeners are running otherwise (you will get “Highways by exor listener processes are not currently running” message) you need to start the listeners.
Before Exor listeners are started on server you need to set up some OS system variables and Exor User Option parameters according your Exor configuration. In Exor , you need to set up :
REPCLIPATH the location of your exor\reports directory , e.g. x:\exor\reports\
It is vital that the directory separator (‘\’ in NT, ‘/’ in UNIX) is included at the end of this directory path.
REPOUTPATH $PROD_REPORTS
The value of the REPOUTPATH environment variable must point to
the same physical location as the REPCLIPATH variable.
REPSQLPLUS sqlplus
REPVEWTOOL write
On your server you need to set up:
PROD_HOME This needs to point to the location of all the server based software and should include the bin portion of the path. Examples of typical values for this are : UNIX : /usr2/exor/bin
Windows : x:\exor\bin
PROD_REPORTS This needs to point to the location on the server which has been shared and mounted
on each client PC to enable clients to view the server based output. Examples of typical values for this are :
UNIX : /share/reports/
Windows : x:\exor\reports\
DB_ALIAS This variable should only be set if the server based modules will run on a different machine to
that where the database resides. If this is the case, it should be set to the Database Connect
string specified in SQL*NET for the connection from the machine holding the server based
modules to the server where the database instance resides.
If the server based modules and database server reside on the same machine, this variable
should not be set. Examples of typical values for this are: exor
It is recommended to write start/stop Exor listeners scripts and run it to start them in OS background.
For Windows server Exor start listeners script content could be following:
cd \exor\bin
REM Set up environment & start listeners
set PROD_HOME=x:\exor\bin
set PROD_REPORTS=x:\reports\
start /wait x:\exor\bin\exorlsnr highways/<password> start
If all parameters were set correctly, the 3 listener programs (GRI0205, GRI0206, GRI0207) will start running in server OS background.
You need to run this script each time your server is rebooted.