The business layer uses this message to send a fix message out to the counterparty.
The business layer uses this message to send a fix message out to the counterparty. It should be sent as an akka message to the sfSessionActor.
With SackFix all TCP is ACK'ed, so you will recieve back the BusinessFixMsgOutAck when the message has been sent.
The message to be sent out
The other side rejected a message - either a session level or a business level message.
The other side rejected a message - either a session level or a business level message. You should think about what to do - humans should go have a look at the very least, or maybe disconnect and wait for humans?
Holds details of the comp id's and so on
If you want to send the session a message you use ! BusinessFixMsgOut()
- the body will be a reject ie message.body match{ case rj:RejectMessage => }
You can send this to the session Actor to tell it to close the session
You can send this to the session Actor to tell it to close the session
This will be sent in the logout message to the counterparty, so make it polite!
You may receive this more than once during close down.
You may receive this more than once during close down.
Holds details of the comp id's and so on
Holds details of the comp id's and so on
If you want to send the session a message you use ! BusinessFixMsgOut()
Created by Jonathan during 2017.
Created by Jonathan during 2017.
When you create the session hub actor you must inject your own businessmessage handler. This is only called when the message has been fully validated and determined not to be a session level message.
I would suggest that this class has a reference to your business Actor, and forwards teh fix message to the actor. You can look after your own ActorRef and lifecycle.
This will be sent up to your gardian actor if there is a problem.
Created by Jonathan during 2017.
Holds details of the comp id's and so on
If you want to send the session a message you use ! BusinessFixMsgOut()
Has .header, .body and tail