This is an old revision of the document!
TraderLogout
Logging out Traders
Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User.
A trader that has been successfully authenticated with a Trader Logon can be logged out by the Master User with the Trader Logout message.
Identifying the Trader
The Trader Logout identifies the target trader with the UserName tag (Tag 553). No password is required.
| Tag Name | Tag Number | Description |
|---|---|---|
| UserName | 553 | T4 User |
A successful attempt to log out a trader is acknowledged with a Trader Logout Response message that contains a Success description in the `Text` tag (Tag 58).
Failure to logout a trader will result in a failed Trader Logout Response message sent to the client. The Trader Logout Response message may contain a short description of the failure in its `Text` tag (Tag 58).
A failed Trader Logout does not result in a physical disconnection. The FIX Session continues with the participation of the Master User and other traders that were previously authenticated and remained logged in. The FIX Session can only be terminated by a FIX Logout message.
Message Dictionary
| Tag | Field Name | Req'd | Comments |
|---|---|---|---|
| Standard Header | Y | MsgType = UCH | |
| 49 | SenderCompID | Y | T4 Application Name (inbound), T4 Firm Name (outbound) |
| 56 | TargetCompID | Y | T4 Firm Name (inbound), T4 Application Name (outbound) |
| Body | Y | ||
| 109 | ClientID | N | ID of organization the Trader/User pertains to |
| 553 | UserName | Y | T4 User to be logged out |
| Standard Trailer | Y |
Sample
In this example, the T4 FIX API client requests the start of a FIX Session. The client enables the Multi-Trader mode (with Tag 372=UCG). The login request's success is signaled by a Login message response from the T4 FIX API. This establishes the FIX Session with the Master User. Subsequently, the client sends a Trader Logon to authenticate a new Trader/User under the current FIX Session. The success of the Trader Logon is responded by the FIX API with a Success Trader Logon Response. An attempt to logout this trader is requested by the FIX API client with the Trader Logout message. The FIX API responds with Success as the FIX client correctly identified the logged-in trader. Finally, the client requests the termination of the FIX Session with a FIX Logout message. The FIX API responds with a FIX Logout indicating the end of the FIX session.
Login Request from T4 FIX API Client
34=1|49=T4Example|56=ctsdev|52=20160930-16:33:21.227|91=112A04B0-5AAF-42F4-994E-FA7CB959C60B|90=36|98=None|108=25|553=MasterUser|554=***|1407=58BD-B00F-5805-98AA-BD46-0417-C2B8-9C5F|384=1|372=UCG|
Successful Login Response from T4 FIX API
34=1|49=ctsdev|56=T4Example|50=T4FIX|52=20160930-16:33:26.714|98=0|108=30|553=MasterUser|554=***|1408=4.3.62.0|
Trader Logon Request from T4 FIX API Client
34=2|49=T4Example|56=ctsdev|50=Trader1|52=20160930-16:33:41.989|91=112A04B0-5AAF-42F4-994E-FA7CB959C60B|90=36|109=CTS|553=Trader1|554=***|
Successful Trader Logon Response from T4 FIX API
34=57|49=ctsdev|56=T4Example|50=T4FIX|52=20160930-16:33:47.460|553=Trader1|58=Success|
Trader Logout Request from T4 FIX API Client
34=3|49=T4Example|56=ctsdev|50=Trader1|52=20160930-16:33:44.181|109=CTS|553=Trader1|
Successful Trader Logout Response from T4 FIX API
34=58|49=ctsdev|56=T4Example|50=T4FIX|52=20160930-16:33:49.605|553=Trader1|58=Success|
Logout Request from T4 FIX API Client
34=4|49=T4Example|56=ctsdev|52=20160930-16:33:49.444|
Successful Logout Response from T4 FIX API
34=59|49=ctsdev|56=T4Example|50=T4FIX|52=20160930-16:33:54.851|58=Successful logout upon request|