Occurs when the FIX engine has been initialized.

Namespace: Teraspaces.QWFIX.Application
Assembly: Teraspaces.QWFIX.Application (in Teraspaces.QWFIX.Application.dll) Version: 2.5.0.0 (2.5.0.0)

Syntax


	C#			Visual Basic			Visual C++			J#

public event FIXEngineEventHandler FIXEngineInitialized

Public Event FIXEngineInitialized As FIXEngineEventHandler

public:
 event FIXEngineEventHandler^ FIXEngineInitialized {
	void add (FIXEngineEventHandler^ value);
	void remove (FIXEngineEventHandler^ value);
}

/** @event */
public void add_FIXEngineInitialized (FIXEngineEventHandler value)
/** @event */
public void remove_FIXEngineInitialized (FIXEngineEventHandler value)

Remarks

Settings()()() can be retrieved at this point.

Sessions can be retrieved from the engine at this time. Application should set the event handlers of each FIXSession in this event handler.

Additional IFIXEngineMessageHandler can be set by calling SetEngineMessageHandler()()().

The FIX engine recovery process will start after this event handler finishes. The recovery process will "replay" all historical FIX messages in the same order they are processed before.

The following is a typical example of sequence of events being triggered.
FIXEngineInitialized on FIXStandaloneApplication
FIXEngineRecovered on FIXStandaloneApplication
SessionStarting and SessionStarted on some FIXSession
FIXEngineStarted on FIXStandaloneApplication
SessionStarting and SessionStarted on some FIXSession
SessionResetting and SessionReseted on some FIXSession
FIXEngineStopping on FIXStandaloneApplication
SessionStopping and SessionStopped on eachFIXSession
FIXEngineStopped on FIXStandaloneApplication

Note:
A FIXSession defined in a FIXEngine may have a different scheduler than that of FIXEngine. A FIXSession may not be started when FIXEngine is started because the scheduler of the session may have not been "kicked up" yet. It is recommended that application hook up the FIXEngineStarted event and the SessionStarted of everyFIXSession and start the business logic after all required FIXSession has been started. SessionStarted has nothing to do with the status underlying TCP communication channel. It is controlled by the Scheduler only. Event if the underlying TCP channel is down, the session will still be started on time, and application can still send messages to the session by calling [M:Teraspaces.QWFIX.FIXSession.SendMessage(FIXMessage, bool)]. The messages will be queued and later sent to the recipient when the TCP channel is up.

Note:

A FIXSession defined in a FIXEngine may have a different scheduler than that of FIXEngine. A FIXSession may not be started when FIXEngine is started because the scheduler of the session may have not been "kicked up" yet.
It is recommended that application hook up the FIXEngineStarted event and the SessionStarted of everyFIXSession and start the business logic after all required FIXSession has been started.
SessionStarted has nothing to do with the status underlying TCP communication channel. It is controlled by the Scheduler only. Event if the underlying TCP channel is down, the session will still be started on time, and application can still send messages to the session by calling [M:Teraspaces.QWFIX.FIXSession.SendMessage(FIXMessage, bool)]. The messages will be queued and later sent to the recipient when the TCP channel is up.

Syntax

Remarks

See Also