load balancing
Hi all, We are trying to create a process to eliminate failover and provide load balancing between two separate servers. JDBC call is generated on application level and accesses the primary machine via virtual IP, database name, and informix server name (name of the informix instance I believe). There will be an enterprise replication between two servers to maintain an integrity of the data. Question: would it be possible to name an informix instance on a second server by the same name as the primary server has, and give it a different SERVERNUM? The thing is, that we do not know of any hardware solution to trick the application call when our primary server is down. Unless someone can suggest some other way of dealing with this situation. Thank you in advance, Elena.
Elena Korol wrote: > > Hi all, > > We are trying to create a process to eliminate failover and provide load > balancing between two separate servers. > > JDBC call is generated on application level and accesses the primary machine > via virtual IP, database name, and informix server name (name of the > informix instance I believe). > There will be an enterprise replication between two servers to maintain an > integrity of the data. > Question: > would it be possible to name an informix instance on a second server by the > same name as the primary server has, and give it a different SERVERNUM? > > The thing is, that we do not know of any hardware solution to trick the > application call when our primary server is down. > Unless someone can suggest some other way of dealing with this situation. Set DBPATH=SecondaryServer If the application gets a connection lost error it should either exit and be restarted or reconnect itself. The DBPATH specifies what server to connect to if the default server ($INFORMIXSERVER) is down. This will work automatically if you use DATABASE databasename or CONNECT databasename without the @ServerName option. If you explicitely connect to a particular host by name you should getenv() to get the value of INFORMIXSERVER and DBPATH and parse them yourself for the sequence of hostnames to attempt connections to. Art S. Kagel
'single image cluster' like the one from SCO (to be Caldera): http://www.sco.com/2node can be a solution too. Thanh In article <39CA2B5A.24B455C4@bloomberg.net>, kagel@bloomberg.net wrote: > Elena Korol wrote: > > > > Hi all, > > > > We are trying to create a process to eliminate failover and provide load > > balancing between two separate servers. > > > > JDBC call is generated on application level and accesses the primary machine > > via virtual IP, database name, and informix server name (name of the > > informix instance I believe). > > There will be an enterprise replication between two servers to maintain an > > integrity of the data. > > Question: > > would it be possible to name an informix instance on a second server by the > > same name as the primary server has, and give it a different SERVERNUM? > > > > The thing is, that we do not know of any hardware solution to trick the > > application call when our primary server is down. > > Unless someone can suggest some other way of dealing with this situation. > > Set DBPATH=SecondaryServer > > If the application gets a connection lost error it should either exit and > be restarted or reconnect itself. The DBPATH specifies what server to > connect to if the default server ($INFORMIXSERVER) is down. This will > work automatically if you use DATABASE databasename or CONNECT > databasename without the @ServerName option. If you explicitely connect to > a particular host by name you should getenv() to get the value of > INFORMIXSERVER and DBPATH and parse them yourself for the sequence of > hostnames to attempt connections to. > > Art S. Kagel > Sent via Deja.com http://www.deja.com/ Before you buy.