Client is taking both product from us. Can they use the same SDK for both RT optimized and EaaS? SDK Real-Time-SDK-2.0.0.L1.java.zip.
If yes, my second question is that when their EaaS is via leased line, could you please provide sample code where this will be different from using RT optimized?
I understand that the EaaS is the RSSL connection, the RTSDK (Java and C++) support both RSSL and RT Optimized connections.
For the RSSL connection (EaaS) the client can use the example 100 Market Price o (ex100_MP_Streaming) as an example code.
For the RT Optimized connection, it uses the REST API (for RDP authentication and Service Discovery) and Encrypted RSSL connections. The API automatically handles those connections for the clients. The client can use the example ex450_MP_QueryServiceDiscovery as an example code
The client can find the EMA Java tutorials at this link.
Please refer to Refinitiv Real-Time SDK Java QuickStart pages.
For EMA connecting to an ADS (RTDS / TREP type connection), they can use the standard QuickStart. My understanding of EaaS is that the consuming applications connect to the ADS via Direct line, VPN, Cross connect etc - depending on the network option chosen by the customer.
For EMA connecting to RRTO they can use the RRTO QuickStart
As you will note from the above QuickStarts, the RTDS connection one uses example 100 from the EMA Java SDK and the RRTO version using example 450.
The majority of the examples that are provided with the EMA JAva SDK are designed for connecting directly to an ADS. Example 450 and example 113 in particular demonstrate the different ways of establishing an RRTO connection+login.
As you will observe by comparing the code of the examples, It is only the initial connection+login code that is different - once connected and logged in, the code required to request data and consume data remains the same.