FIXRemoteReplicatorApplication is the application framework that enables an application to remotely "replicate" the FIX message communications of a running remote FIXStandaloneApplication. The replicated remote FIX message communication will be "replayed" in the same order as they were sent and received in the remotely running process with FIXStandaloneApplication.
Application developer only need to write the application business logic handler once (by implementing an FIXEngineMessageHandler and assign it to a FIX session). The message handler will then be used by both the production system (with FIXStandaloneApplication) and the remote replicator application (with FIXRemoteReplicatorApplication).
FIXRemoteReplicatorApplication is useful for many applications such as real-time reporting, real-time monitoring and real-time risk management.
FIXRemoteReplicatorApplication is used in our GUI based remote monitoring and management tool, "QWRTAnalyzer".
Remotely replicating all FIX message communications may appear to bring a lot of overhead to the running production system. However as a matter of fact the additional overhead is negligible. The remote replicator thread is running at a lower priority. It will be preempted by application business logic threads at any time. Unless the system is running at 100% CPU load (which should not happen at any rate), it is safe to assume the remote replication has almost 0 overhead!
Only three types are used to implement a FIXRemoteReplicatorApplication enabled application: FIXRemoteReplicatorEngineCallBack, FIXRemoteReplicatorSessionSettings and FIXRemoteReplicatorApplication. Read the class documentation of all those three types to learn how to build a remote replicator application.
See RemoteOrderMon sample for more details.