What kind of Status will send back by RFA ? If service get down ?

Best Answer
-
Hi @jessie.lin,
Referring to RFAJ_RDMUsageGuide.pdf (in <RFA Java Package>/Docs> folder), it uses ‘UPDATE’ message type to convey any changes information (e.g. service status in this case).
To demonstrate the example from the scenario that you mentioned in the question, we’ve performed the test as depicted in Figure 1.
Regarding the image above Connection A (between the feed and ADS/POP) is unstable, but it doesn’t affect to Connection B. However, a service status will change depending on Connection A.
In that case, ADS/POP will send directory ‘UPDATE’ message type to inform changes occurred to the consumer application (see Figure 2, and the message log attached).
Note: To check the change of service, the application needs to check Filter: STATE, Element: ServiceState (0: Service is Down, 1: Service is UP).
If you want to test
DIRECTORY message type behavior, I recommend you try RFA Java’s example named
DictionaryDemo program. You can modify just a few files a little bit as shown below:- In
DirectoryDemo.java
// Import ConfigDb to make the program to use hardcode configuration settings
import com.reuters.rfa.config.ConfigDb;
// At the init() method, make the application uses hardcode settings
public void init()
{
// Create a programmatic configuration object.
ConfigDb configDb = new ConfigDb();
configDb.addVariable("myNamespace.Sessions.mySession.connectionList", "myConnection");
configDb.addVariable("myNamespace.Connections.myConnection.connectionType", "RSSL");
configDb.addVariable("myNamespace.Connections.myConnection.serverList", "172.20.33.43");
configDb.addVariable("myNamespace.Connections.myConnection.portNumber", "14002");
configDb.addVariable("myNamespace.Connections.myConnection.logFileName", "console");
configDb.addVariable("myNamespace.Connections.myConnection.ipcTraceFlags", "31");
// Make the application use the object created previously.
Context.initialize(getConfigDb());
System.out.println(getConfigDb());
...- In
DirectoryClient.java
// At encodeSrcDirReqMsg(), make the example remove NONSTREAMING flag.
private OMMMsg encodeSrcDirReqMsg()
{
...
msg.setIndicationFlags(OMMMsg.Indication.REFRESH
/*| OMMMsg.Indication.NONSTREAMING*/);
...
// At processEvent(Event event), comment two statements, and add a logic to support UPDATE_RESP message type.
if (respMsg.isSet(OMMMsg.Indication.REFRESH_COMPLETE))
{
// Receive all dictionary names from all source directory
// Notify application to download dictionary
// Comment these line.
// _mainApp.processDirectoryInfo();
// _dirHandle = null; // Because the request is NON-Streaming
}
}
}
// Add this condition
else if (respMsg.getMsgType() == OMMMsg.MsgType.UPDATE_RESP)
{
System.out.println("Received update message type, there should be some changes regarding service directory ");
}Hope this helps.
0 - In
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 629 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 86 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛