QuickFix/n多连接问题：如何无需配置多个SenderCompID实现批量登录？

To support hundreds of accounts without modifying your SenderCompID configuration, use standard FIX protocol fields that let you identify individual accounts alongside your fixed SenderCompID=TT. Here are practical, compliant solutions:

1. Authenticate with Username/Password Fields #

The FIX spec includes Username (Field 553) and Password (Field 554) for per-user/account authentication. These are sent in the Logon (MsgType=A) message, so you can keep SenderCompID=TT constant while passing unique credentials for each account.

Example Logon Message: #

8=FIX.4.4|9=120|35=A|49=TT|56=TSERVER|553=SIM_ACCT_001|554=MyStrongPass1|98=0|108=30|10=072|

• 49=TT: Your fixed initiator SenderCompID
• 553=SIM_ACCT_001: Unique account username
• 554=MyStrongPass1: Matching account password

Your acceptor (TSERVER) needs to be configured to check these fields for authentication instead of relying only on SenderCompID.

2. Use SenderSubID for Account Segmentation #

SenderSubID (Field 50) is designed to add sub-identification under a main SenderCompID. This is perfect for grouping multiple accounts under your terminal's TT identifier.

Example Logon Message: #

8=FIX.4.4|9=115|35=A|49=TT|50=LIVE_ACCT_123|56=TSERVER|98=0|108=30|10=099|

• 50=LIVE_ACCT_123: Unique ID for the individual account
• The acceptor can map the combination of SenderCompID=TT + SenderSubID=LIVE_ACCT_123 to the correct account.

This is a widely adopted approach in FIX implementations and avoids managing dozens of SenderCompID values.

3. Fallback: SenderLocationID #

If SenderSubID is already used for another purpose, SenderLocationID (Field 142) can be repurposed to carry the account identifier. While it's intended for geographic location, many systems allow using it for account segmentation (just confirm this with your acceptor's setup).

Critical Considerations: #

• All these methods require updates to your acceptor (TSERVER) to process and validate the additional fields. Without server-side support, you won't be able to distinguish between accounts.
• Prioritize standard FIX fields over custom ones to maintain compatibility with industry tools and practices.

内容的提问来源于stack exchange，提问作者PeteOnTheNet