RE: [Quickfix-users] Failover.

[Juergen J. <je...@gm...>]

Hello all, 
 
we are using quickfix with failover in a production environment : 
 
BUT currently quickfix is a library that implements the FIX standards.
NOT a full featured production system . 
 
We put the quickfix lib in a J2EE environment with already build-in
clustering on a high level. 
 
Regards, 
Juergen jetm
 
-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of Oren
Miller
Sent: Freitag, 9. Mai 2003 13:25
To: Jim Morgan; qui...@li...
Subject: Re: [Quickfix-users] Failover.
 
The SocketConnectHost<n> and SocketConnectPort<n> allows you to set up a
round robbin connection from your initiator to several acceptors that
already exist in a failover system.  This doesn't sound like what you
are looking for, at least not entirely.
 
QuickFIX is currently distributed as a development library instead of a
standalone server, which allows for a lot of flexibility, but lacks many
of the built in admin features some of the commercial vendors have.  The
advantage is you can integrate QF with third party or proprietary
failover systems.
 
Setting up a single location from which sequence numbers and the message
store is received is easy if you use a database or an NFS drive.
QuickFIX comes with a FileStore, so NFS should be easy to setup.  It
also comes with a MySQL store, but people have also written Oracle and
MSSQL adapters as well.
 
So what you are missing is something that can start and stop the
appropriate servers as needed.  For this you need to currently use a
third party system (which would a product that focuses on failover and
would likely be superior in that respect anyway).  Or you can create
something yourself, which has the advantage of you having total control.
 
If you must have an engine that has failover built in, then
unfortunately QuickFIX will not be the best choice for you at this time.

Jim Morgan <per...@my...> wrote:
I'm evaluating FIX systems for a client. QuickFIX is obviously very 
attractive because of its Open Source nature. However there is little to
be 
seen in the documentation about how to set it up to allow for failover.
Am 
I missing something, or could someone point me towards any resources on
the 
subject.

I'm planning to run QuickFIX on Linux, on two servers. If the primary 
server goes down, the secondary server should cut in, and instantly be
able 
to pick up where the primary left off, using the same message sequence 
numbers and message store location. The only information I've found so
far 
relevant to failover is the SocketConnectHost and SocketConnectPort 
settings in the configuration file, and its not clear to me how the 
machines should be set up, either physically, or in terms of software 
configuration.

Has anyone set up this kind of arrangement already, and would you be 
prepared to share your experiences?

Jim



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Quickfix-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-users
  _____  

Do you Yahoo!?
The New <http://us.rd.yahoo.com/search/mailsig/*http:/search.yahoo.com>
Yahoo! Search - Faster. Easier. Bingo.