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

In <mulc3AA2YUvzEwLh@smooth1.demon.co.uk> David Williams <djw@smooth1.demon.co.uk> writes: >In article <5phpli$9d9$1@godzilla.zeta.org.au>, Bryan Tonnet ><batonnet@zeta.org.au> writes >>In <01bc8808$f78d9be0$d616a5ce@MSIPhxPaulM.minisoftinc.com> "Paul Mosser" >><pmosser@primenet.com> writes: >> >>>Is it possible to have multiple database servers on OWS (v7.22) on one NT >>>4.0 box?? If so, *HOW* do you add new server "instances"? >> >>I was told this was a definitive limitation of OWS for NT (one instance per >>box, that is). Even in the Unix version, which does support them, the >>documentation makes no mention of multiple instances. Once you claw your >>way through the setup-that-wont-let-you-use-raw-partitions, the multi >>instance part is pretty regular. The fun bit comes when you want to run >>multi sagents for your instances :) >> > The limitation is one SUPPORTED online instance on the machine. In > UNIX I have managed to create a second OWS instance completely my > hand and change the exisiting one to use raw disk. > However the second instance is NOT supported by Informix. > PS I managed to get the second sagent running, by playing about with > $INFORMIXSERVER and /etc/services. Not sure what sagent is used for > though..., I suspect it is used for talking to the GUI tools on a > PC... You are correct, although the GUI tool is hardly worth the effort. About the only thing it saves you is learning oninit, onmode and portions of onspaces. All this for the small risk of not being able to talk to your database at all if the network's down :| 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. 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? -- Bryan Tonnet batonnet@phase4.com.au