A FIX session configuration can be shared. For example, the FIX session configuration can be used by both a client process and a server process, as long as both the client and server are implemented with QWFIX SDK.
In the "General" tab of the FIX session editor, user must fill in all apecified parameters. Because a session configuration can be share by both a client and a server, we don't use the terms such as "SenderCompID" or "TargetCompID". Instead, we use "Initiator CompID" and "Acceptor CompID". If the FIX session is used in a client process, it is usually used in "initiator" mode. So the "Initiator CompID" will become "SenderCompID" in the client process.
A FIX Session must be associated with a FIX schema. The schema will be used to encode, decode and verify the FIX message communicated in the FIX session.
A FIX Session must be associated with a FIX schedule. A FIX engine may contain multiple different FIX sessions with different schedulers. Once the engine is started, the FIX sessions will be automatically started and stopped by the FIX engine according to the specific scheduler associated with the session.
Other parameters involve the support for "NextExpectedMsgSeqNum" and "24 hour session". For more information please refer to the "FIX Protocol Specification".
If 24 hour session is enabled, a reset time must be specified.
If "Initiator reset" is checked, the session initiator (usually the client) will also initiate the 24 hour session sequence number reset; otherwise, the acceptor will initiate the reset.