Two apps: a client (initiator) and a server (acceptor)
No special parameters. Just run it and leave it up.
cd Server
dotnet run ../../cfg/server.cfg
Takes one "scenario" parameter. The client will start, run the scenario, and shut down.
- It has
ResetOnLogon=Y
so it always starts at 1. (Same reasons as your app, of course.) HeartBtInt
is 10 seconds
cd Client
dotnet run ../../cfg/server.cfg scenario=1a
- "1a" - Login with expired password "LLL". Server will respond with appropriate logout.
- "1b" - Login with Password (554) and NewPassword (925). Server will respond with appropriate login.
- The counterparty docs treat these as a combined scenario, but they're functionally independent to each other.
- "3" - SeqNum reset scenario:
- Client logs on, waits for a few heartbeats to run the SeqNum up
- Client disconnects
- Client reconnects. Config
ResetOnLogon
means it will includeResetSeqNumFlag=Y
. - Client observes that the SeqNum was reset by Server and terminates.
- (NOTE: this scenario is a little redundant -- The client's default
ResetOnLogon=Y
config means that this behavior is demonstrated whenever this Client connects to Server for any reason!)