
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
Richard, What I did here was create a single installation of Ingres on one CITRIX server box using the II_HOSTNAME facility. The hostname I used here was WINPC so it was independant of the server name. I only then had to install Ingres once, on the master installation node. Our CITRIX people then cloned the disk to the other 20 servers in the farm and renamed the node names (hence the use of the II_HOSTNAME to keep Ingres independant of the actual node name). This setup is useful when a node needs rebuilding or additional nodes are to be added, the Ingres administrator is not involved !! Also because the configuration on every box is the same and the underlying files are named identically (e.g. Names area) files can be copied at will (who would do such a thing ?). Gotcha's are the symbol.tbl file going walkies on reboot (use SRVANY.EXE off the W2K resource kit to create an automatic recovery service that starts before Ingres does and puts the SYMBOL.JIC into action !) and GCC's deregistering themselves (run more than one and the problem will go away...). As for configuration, use the netuil -file scripts. I'm pretty sure IngresII 2.0 is NOT supported under CITRIX (terminal services), you'll have to install 2.6 + Patches ! Hope this all helps (Is Ingres actually in use in NZ ?) Cheers Gary
| <-- __Chronological__ --> | <-- __Thread__ --> |