Add new Session to FIXEdge.properties ( FIXEdge1\conf\FIXEdge.properties )
Add a session TestEchoAcceptor to the list of sessions (multiple sessions should be separated by a comma):
And configure session parameters:
Configure BL rules ( FIXEdge1\conf\BL_Config.xml )
E.g. via run script:
<FIXEdge installation dir>\FIXEdge\bin\FixEdge1.run.cmd
<FIXEdge installation dir>/FIXEdge/bin/FixEdge1.run.sh
Open FIX Client Simulator. (It can be found in the FIX Antenna .NET Wrapper package).
And create a new session (select Session menu -> Create New ...) as Initiator with the following parameters:Session type: Initiator
SenderCompID = FIXECHOCLIENT
TargetCompID = FIXEDGE
FIX Version = 4.4
Remote Port = 8901 ( ListenPort parameter in FIXEdge's engine.properties )
Remote Host = localhost (or IP address/hostname of the FIXEdge server)
Please note that SenderCompID on the FIX Client Simulator side should have the same value as TargetCompId on the FIXEdge side
And TargetCompId on the FCS side should be the same as SenderCompID on FIXEdge's side.
Send message from FIX Client Simulator ( Pipe character is used to represent SOH character )
The file with FIX message example and SOH delimiters: NewOrderEchoTestMessage.txt
Echo message from FIXEdge is received:
- FIXEdge should be up and running state after step 4.
- There are [ERROR] or [FATAL] error records in FIXEdge logs FIXEdge1\log\FIXEdge.log.
- The FCS and FIXEdge have up-to-date licenses.
- If a session can't be established due to sequence number issues this can be resolved by cleaning logs on both sides.