Why two Login responses for successful login
Hi I am using RFA to login and get market data.
In noticed that on login I get two login response messages
One with MsgType.REFRESH_RESP another with MsgType.STATUS_RESP
Both of these messages has "Login Accepted"
Why am I receiving another login successful message with message type as STATUS_RESP
Should I expect and handle abrupt login replies further on same stream?
Best Answer
-
Hello @ramesh.jitkar
What you see is from the Login Refactoring feature since RFA 7.0. Instead of receiving multiple login response messages per connection or service state change that provided mostly redundant information, the application will immediately get one Refresh response message with a stream state of OPEN and a data state of SUSPECT created by RFA as shown below:
Msg Type: MsgType.REFRESH_RESP
Msg Model Type: LOGIN
Indication Flags: REFRESH_COMPLETE
Hint Flags: HAS_ATTRIB_INFO | HAS_ITEM_GROUP | HAS_RESP_TYPE_NUM | HAS_STATE
State: OPEN, SUSPECT, NONE, "All connections pending"
Group: 0000
RespTypeNum: 0 (RespType.SOLICITED)
AttribInfo
Name: pimchaya
NameType: 1 (USER_NAME)
Attrib
ELEMENT_LIST
ELEMENT_ENTRY ApplicationId: 256
ELEMENT_ENTRY Position: 10.42.61.200/U8007607-TPL-A ELEMENT_ENTRY AllowSuspectData: 1
ELEMENT_ENTRY SingleOpen: 1
ELEMENT_ENTRY SupportBatchRequests: 7
ELEMENT_ENTRY SupportOptimizedPauseResume: 1
ELEMENT_ENTRY SupportPauseResume: 1
ELEMENT_ENTRY SupportViewRequests: 1
ELEMENT_ENTRY SupportEnhancedSymbolList: 1
ELEMENT_ENTRY SupportOMMPost: 1Payload: NoneWhen the login status has been changed later e.g. the server send a successful login response(a stream state of OPEN and a data state of OK) to RFA, RFA transforms this message as a Status message and send to the application. For example:
Msg Type: MsgType.STATUS_RESP
Msg Model Type: LOGIN
Indication Flags:
Hint Flags: HAS_ATTRIB_INFO | HAS_STATE
State: OPEN, OK, NONE, "Login accepted by host flix."
AttribInfo
Name: pimchaya
NameType: 1 (USER_NAME)
Attrib
ELEMENT_LIST
ELEMENT_ENTRY ApplicationId: 256
ELEMENT_ENTRY ApplicationName: ADS
ELEMENT_ENTRY Position: 10.42.61.200/U8007607-TPL-A
ELEMENT_ENTRY ProvidePermissionExpressions: 1 ELEMENT_ENTRY ProvidePermissionProfile: 0 ELEMENT_ENTRY AllowSuspectData: 1
ELEMENT_ENTRY SingleOpen: 1
ELEMENT_ENTRY SupportBatchRequests: 7
ELEMENT_ENTRY SupportOptimizedPauseResume: 1 ELEMENT_ENTRY SupportPauseResume: 1 ELEMENT_ENTRY SupportViewRequests: 1 ELEMENT_ENTRY SupportEnhancedSymbolList: 1 ELEMENT_ENTRY SupportOMMPost: 1
Payload: NoneThat's why your application gets 2 login response messages.
Therefore, to verify if the application logs in to the server successfully, the application should wait for a Status message on the Login stream that has a stream state of OPEN and a data state of OK before sending the item requests as the snipped example source code below:
if ((respMsg.getMsgType() == OMMMsg.MsgType.STATUS_RESP) &&
(respMsg.has(OMMMsg.HAS_STATE))&&
(respMsg.getState().getStreamState() == OMMState.Stream.OPEN) &&
(respMsg.getState().getDataState() == OMMState.Data.OK))
{
System.out.println(_className + ": Received Login OK Response");
//successfully login so send item request
…
}For the complete source code, please refer to the Tutorial 6 - RDM; Login and event registration
Please refer to API Migration from ,<RFA Package>\Docs\WebDocs\index.html, at section
From 6.5.0 to 7.0.0 or later which explains more details about this feature:
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛