Re: Problems installing OpenLink on the server side

jason@cimedia.com (Jason Bodnar) wrote: :After digging through the newsgroup and seeing that almost everybody :recommended OpenLinks ODBC stuff I was already to try it out and to be :amazed. I installed the client without a problem and set up a new data :source. I then moved on to the server stuff. I was a little :disappointed with the docs but I think I got the request broker :installed and started. But then what? Do I have to start the db agent? No. The db agent is started automatically when an application opens a connection to the database. To do the installation you should have copied the following files to the install directory (typically /usr/openlink - but any directory will do): inf7xxx.taz rqbxxx.taz register.ini install.sh where xxx is a code for your Unix OS. Check that the register.ini file is a text file with proper line endings (line feed only). If you transfered this via MS Windows you easily get cr/lf in it and will have to get rid of the cr's. You either use ftp to transfer in text mode or simply use vi or another Unix editor to remove the cr's. Check the same for install.sh Then make sure you are in the install directory and run install.sh (type ./install.sh). This script unfortunately is a little too simple, so it doesn't report on some simple errors. Look at it an check that the basic things have been done (ownership have been set and the register.ini file have been copied to the ./bin directory). Now you have to edit the oplrqb.ini file a little. It's well documented in the file what you have to change. Change nothing else for your initial test. The [Environement...] refers to [Environement INFORMIX7] for any 7.x engine or [Environement INFORMIX5] for any 5.x engine INFORMIXDIR is there in both cases and must be set correctly. For 7.x engines you must also set INFORMIXSERVER correctly. You don't need to touch any [Environement...] section that you don't use. The appropriate section to use is selected when you set up each client on MS Windows. If everything is installed properly it's easiest to start the request broker from root, at least for the initial testing. (You don't have to be root for any part of the installation or startup though.) Just make sure that all the usual Informix environement variables are set first (INFORMIXDIR, INFORMIXSERVER, ONCONFIG, DBDATE, PATH includes $INFORMIXDIR/bin and what else might be required). You shouldn't need all these if they are set in the oplrqb.ini file, but I set them anyway. Then just type the name of the request broker (/usr/openlink/bin/oplrqb or just ./oplrqb if you are in the directory where it's installed). Check that the request broker is started (ps -e | grep opl and see that oplrqb is running). Now you should be able to connect. Later you will probably want to put the startup of the request broker into an rc-script to make it start automatically when you boot your Unix server (it can be started before or after the engine). Just make sure you do it via a shellscript where you set all the appropriate environement variables as above. :I tried that and got an RPC failed error (bad file number). I haven't ever seen "bad file number". You might want to look at the oplrqb.log file in the ./bin directory under your OpenLink install directory. It may contain some further information on what the problem is. :Or maybe I don't even need to mess with this. All I want to do is :provide our maketing people with access to a database via MS Access. :Is there an even easier way to go than OpenLink ODBC (assuming I can :get it running)? I know of nothing easier then the OpenLink ODBC driver. I have tested several, but not all. : : :-- :Jason C. Bodnar :jason@cimedia.com :Internet Programmer :Cox Interactive Media Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org