Working on local environment but not working .Bat File

mkasim

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.

aaa.png

Jirapongse

@mkasim

Typically, to connect to the server and retrieve data, you need to have the following information.

1. The connection type or channel type. The possible values are:

    <!-- ChannelType::RSSL_SOCKET - TCP IP connection type --> 
   <!-- ChannelType::RSSL_HTTP - Http tunnel connection type --> 
   <!-- ChannelType::RSSL_ENCRYPTED - Https tunnel connection type --> 

   For EZD, the value should be ChannelType::RSSL_SOCKET.
2. The IP address or host name of the EZD server
3. The TCP port listening on the EZD server to accept the connection. The default port for the socket connection type is 14002
4. The user name used to connect to the EZD server
5. 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);