How to read out users DACS configuration?

Hi all,
while requesting users sub service list using the OpenDACS interface
agent_->getUserSubServiceList( *handle, serviceName_, userSubServices )
we receive exchanges subservices never been setup in DACS.
For example the exchange subservice "CMECBOT" will appear as long as the user is allowed for "CME" and "CBT".
Same with exchange subservice "XCA01D" which have never been setup in DACS explicitly.
So how can I determine the users DACS configuration by request via OpenDACS interface?
It seems as if there might be some undocumented logic within DACS front-end.
Regards,
Thomas
Best Answer
-
This composite PDP is permissioned automatically when the underlying exchange PDPs have been permissioned
I found that:
- The required exchanges for CMECBOT are CBT and CME
- The required exchange for XCA01D is OSA
You can directly contact the DACS support team via Get Support for more information regarding composite PDPs.
0
Answers
-
Hello @Thomas Wolf,
I was not able to reproduce what you describe, getting "not-in-the-dacs" subservices by running setUserSubServiceList() call. Subservices that I get from setUserSubServiceList() were consistent with subservices defined in my DACS. I get products, exchanges, specialists data sets, not just one type of "subservice", perhaps this is what you are seeing?
Further thinking, perhaps call getPEList() would better converge with your requirements? It returns the PEs, or permission entities, assigned to the user, defining permissions assigned.
0 -
They are composite subservices.
CMECBOT- This is CME/CBOT COMPOSITE
PE ID code: 116
XCA01C - This is SEGMENT 3 (CROSS-MARKET CONSOLIDATED ASIA)- Equities
PE Code: 7150You can retrieve it via the getPeToSubServiceList() interface.
116 | E : CMECBOT
...
7150 | E : XCA01C0 -
Hi Zoya,
no those exchange subservices appear on getUserSubServiceList() although the DACS adminitrator have never permissioned those subservices for the user. Neither have those subservices ever been displayed at the DACS front-end. I think you will not been able to reproduce this feature by explicitly setting the permission using setUserSubServiceList(). It seems to be an front-end issue.
I have the need to read-out exactly what is displayed at the front-end for reporting and QS reason. And it works quite well beside the reported effects. I do not know where those subservices come from. Does the front-end suppress displaying some subservices or does it conditionally add some subservices depending on given user permissions.
For example the subservice "XCA01D" appear in getUserSubServiceList() as soon as OSA been permissioned at the front-end.
A QS-Reporting on PE list will be confusing for DACS adminitrators. They want to be sure that their current configuration have been applied correctly. Therefore it would be helpfull to generate from getUserSubServiceList a list they can easily compare with their settings.
If there are some special subservices a documentation of those subservices whould be helpful too.
Thanks,
Thomas
0 -
Hi zoya,
yes, jirapongses answer helps us. So we can display all pdp codes as delivered from the interface. Composite pdp codes will be displayed even if added automatically. Our customers can explain their present in our reports refering to a list of possible composite pdps in their setup.
Thanks a lot for your help!
Thomas
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 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.8K Refinitiv Data Platform
- 625 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛