Re: Configuring muti sagents <was Multiple servers on OWS for NT>

In article <5pso1a$2fr$1@godzilla.zeta.org.au>, Bryan Tonnet <batonnet@zeta.org.au> writes > >I'd be interested to find out how you did that with just these two (services >and INFORMIXSERVER, that is). Possibly, I got so caught up in trying to >get the thing sorted out, I couldn't see the wood for the trees. > >My steps were (approx.); > 1. Read all documentation the night before (handy that I can re the docs on my PC using Acrobat Reader). 2. Setup UNIX kernel parameters as required from readme file. 3. AS I have 14x2Gb to play with and only 1/2 of the first disk is used create 1Gb partition to fill the rest to the first disk. Then mkfs a new filesystem and mount it. 3. Install OWS as per instuctions into /.../informix605. telling it to used cooked files in an empty directory /opt/tmp. 4. Shutdown Online instance. 5. rm -rf /opt/tmp !! 6. Repartition raw disks (13 of them!) 7. Copy onconfig to onconfig.live. Change ROOTPATH and ROOSIZE in onconfig file + other parameters I don't like e.g. LOCKS,BUFFERS etc. Also rewrite sqlhosts to have two lines (one shared memory connection, one tcp sockets connection). Also change environment vars ONCONFIG,INFORMIXSERVER and INFORMIXSQLHOSTS as needed. 8. oninit -t to create new root dbspace 9. onspaces to add new chunks + dbspaces as needed. 10. Copy onconfig.live to onconfig.demo changing SERVERNUM, SERVENAME and SERVERALIASES. Copy sqlhosts to sqlhosts.demo and change service names + add new entries to /etc/services. 11. Change ONCONFIG, INFORMIXSERVER and INFORMIXSQLHOSTS environment variables as needed. 12. oninit -t to create root dbspace for second instance. 13. onspaces again to add new chunks + dbspaces as needed. 14. Change startup script /etc/rc.d/rc.M to contain INFORMIXDIR=...;export INFORMIXDIR INFORMIXSERVER=server1; export INFORMIXSERVER INFROMIXSQLHOSTS=... ONCONFIG=onconfig.live; export ONCONFIG $INFORMIXDIR/bin/sastart & INFORMIXSERVER=server2; export INFORMIXSERVER INFROMIXSQLHOSTS=... ONCONFIG=onconfig.demo; export ONCONFIG $INFORMIXDIR/bin/sastart & Two sagents are now running. netstat -a show they are both listening on the required ports. Of course I don't have any client software setup to test them with.. >My steps were (approx.); > >1. Setup OWS >2. Reconfigure OWS setup >3. Reinstall OWS >4. Reboot the machine from OWS setup problem >5. Swear, curse >6. Pull apart the OWS setup to try manual installation. >7. Get poo in a pile, have hot coffee, settle down. >8. Reinstall OWS (this is the AIX implementation by the way) >9. Once you get the default installation running, completely destroy it > and setup your multi instances to suit. > >10. OK here goes the sagent stuff. This assumes sqlhosts and services are > all OK for your already running multi instances. >11. Edit regkeys.txt to suit the first instance. >12. Copy regkeys.txt and reedit for each subsequent instance. >13. Edit startsa to use the INFORMIXSERVER et al for the first instance. > This one also uses the first regkeys.txt >14. Copy startsa and reedit for each subsequent instance. These obviously > use their corresponding regkeys.txt (or whatever they got renamed to). > [Thanks James Tilley for this step] >15. Remove the INFXsagent occurrence from inittab and replace it with > something that uses your changed startsa files. >16. Ignore references to an environment file called INFMXENV. This > doesn't seem to get used (but noone's all that sure) >17. Edit osahosts for the additional sagents. >18. Keep fingers crossed. >19. Worked, but still can't get stopsa to run. It just hangs. Anyone > have a similar problem, or is it just me? > >I think that was it. Did you find a shorter way? > > -- David Williams