Configuration to allow posting to ADH cache for realtime record with additional fields.

II would like to post to an ADH cache to add additional fields to a record coming from an ELEKTRON feed. What configuration would be needed to allow me to do this? Ive tried however all I get is "A9: Service is unavailable."
Thank you for your help.
Best Answer
-
Hi @RN
According to the ADH installation guide, the key parameters for Publisher Augmentation are as follows:
*serviceName*enablePublisherAugmentation: Enables publisher augmentation for the service.
*serviceName*applyPostsToCache: Set to true if you want to let post providers augment items in the cache instead of sending the post to the interactive provider.
*serviceName*publisherAllowedFieldList: List of FIDs to which unmanaged publishers can augment. All other FIDs are dropped
*serviceName*augRemapRefreshUpdateType: If the incoming message from an unmanaged publisher is a refresh message and if the payload contains FIDs which already exist in the item cache, an update is sent. Use this parameter to configure the updateType on the update.
· *serviceName*augRemapUpdateType: If the incoming message from an unmanaged publisher is an update message and if the payload contains FIDs which already exist in the item cache, an update is sent. Use this parameter to configure the updateType on the update.Details of Update type can be found in the RDMUsageGuide for your API.
However, I suspect only the the first two params above would apply to your situation.
Hope this helps.
0
Answers
-
From your description It sounds like you want to do Publisher Augmentation - is that correct?
Have you referred to the ADH and ADS installation guides? They have details of the configuration parameters required to enable Augmentation.
Have you actually implemented the recommended config settings yet?
0 -
In addition to publisher augmentation, Interactive Source Blending within TREP is another option, as well as static record augmentation if all you are interested in is adding static field values to cache.
0
Categories
- All Categories
- 3 Polls
- 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
- 615 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
- 249 ETA
- 554 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
- 643 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
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛