Working on local environment but not working .Bat File
After i complete development and its running on local side
also builded successfully, when i run it on prod session.
Is there any connection needed as well like ip or Proxy after all ?
Ezd running on prod environment as well and i reach it from java it Works on local. But .bat file seems cannot connect at all.
Best Answer
-
Typically, to connect to the server and retrieve data, you need to have the following information.
- The connection type or channel type. The possible values are:
<!-- ChannelType::RSSL_SOCKET - TCP IP connection type -->
For EZD, the value should be ChannelType::RSSL_SOCKET.
<!-- ChannelType::RSSL_HTTP - Http tunnel connection type -->
<!-- ChannelType::RSSL_ENCRYPTED - Https tunnel connection type --> - The IP address or host name of the EZD server
- The TCP port listening on the EZD server to accept the connection. The default port for the socket connection type is 14002
- The user name used to connect to the EZD server
- The service name available on the EZD server
Then, you need to set these values in the API through application code or the configuration file.
For EMA, the connection type, IP address, and TCP port can be set in the EMA configuration file (EmaConfig.xml).
<ConsumerGroup>
<DefaultConsumer value="Consumer_1"/>
<ConsumerList>
<Consumer>
<Name value="Consumer_1"/>
<Channel value="Channel_1"/>
<Dictionary value="Dictionary_1"/>
<XmlTraceToStdout value="0"/>
</Consumer>
...
<ChannelGroup>
<ChannelList>
<Channel>
<Name value="Channel_1"/>
<ChannelType value="ChannelType::RSSL_SOCKET"/>
<CompressionType value="CompressionType::None"/>
<GuaranteedOutputBuffers value="5000"/>
<ConnectionPingTimeout value="30000"/>
<TcpNodelay value="1"/>
<Host value="localhost"/>
<Port value="14002"/>
</Channel>The above configuration indicates that the default consumer is Consumer_1 which uses the Channel_1 for the connection. The channel type of the Channel_1 is RSSL_SOCKET and it connects to the localhost on TCP port 14002.
However, the hostname and TCP port can be overridden in the application code or the application can create configurations programmatically. Therefore, you also need to verify the application code.
Then, the username and service name can be set in the application code.
OmmConsumerConfig config = EmaFactory.createOmmConsumerConfig();
consumer = EmaFactory.createOmmConsumer(config.username("user01"), new AppErrorClient());
ReqMsg reqMsg = EmaFactory.createReqMsg();
consumer.registerClient(reqMsg.serviceName("ELEKTRON_DD").name("IBM.N"), appClient);0 - The connection type or channel type. The possible values are:
Answers
-
Hello @mkasim
Could you please give more detail regarding the issue? You develop the ESDK Java application (EMA or ETA?) to consume data from EZD.
- Your application can connect and consume data from Production EZD in Dev environment successfully
- The application on Production environment cannot connect to same EZD.
- You run the application via a bat file script?
Can you share your .bat file in this post? What is the API you are using? (EMA or ETA?)
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
- 614 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
- 639 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
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛