EZD username configuration in EMA (Java) when using Channel Sets
By creating an EmaConfig.xml file and
setting multiple channels (one per server) it will automatically connect to the
second channel if the first channel fails.
However I can't work out how to set the ezd
username in the code.
Normally (no EmaConfig.xml file) I would do
the following...
OmmConsumerConfig config = EmaFactory.createOmmConsumerConfig();
consumer = EmaFactory.createOmmConsumer(config.host("ezd-a:14002").username(ezdUsername));
However when an EmaConfig.xml file is used
I am supposed to specify the Consumer name from the EmaConfig.xml file as per
below.... But I can't find where to specify the ezd username in this approach.
Specifying a config.host(....) will override the multi channel config, and
trying to set the username directly against the config (as per below) does not
work either...
OmmConsumerConfig
config = EmaFactory.createOmmConsumerConfig().consumerName("Consumer_2");consumer
= EmaFactory.createOmmConsumer(config.username(ezdUsername));
Best Answer
-
Hello @Tokyo Nick,
OmmConsumerConfig.consumerName(String) returns OmmConsumerConfig so you can call OmmConsumerConfig.username(String) in the same line as shown below:
consumer = EmaFactory.createOmmConsumer(EmaFactory.createOmmConsumerConfig().consumerName("Consumer_2").username(ezdUsername));
Please try this.
0
Answers
-
Hello @Tokyo Nick.
The
code above is to use configuration in "Consumer_2" node with username
is ezdUsername. It should not interfere multi channel configuration
specified in "Consumer_2" node.Another possible way is to set default consumer to be "Consumer_2"(Default is Consumer_1" in EmaConfig.xml file:
<DefaultConsumer value="Consumer_2"/>
Then, the source code does not need to specify the consumer node, just specify the user name as shown below:
consumer = EmaFactory.createOmmConsumer(EmaFactory.createOmmConsumerConfig().username(ezdUsername));
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
- 685 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
- 251 ETA
- 556 WebSocket API
- 38 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
- 650 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 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 中文论坛