Can we validate LPC functionality for a client now that RTDS 3.8 and DACS 7.12 have been set up?

Question

We would like to validate the LPC functionality for our clients. We have recently set up RTDS version 3.8 and DACS version 7.12 on our new infrastructure.

Can this environment be configured to support the LPC setup? If so, how should it be configured? If not, what additional setup would be required to perform LPC validation?

wasin.w V3 · Answer

Hello @chetna_arora

Please be informed that the RTDS (ADS and ADH) can also setup to connect to the RTO as the upstream data source.

However, that RTO service data access permissions controlled by the RTO credentials configured in RTDS.

Jirapongse · Answer

@chetna_arora

Thank you for reaching out to us.

As far as I know, LPC (Legacy Protocol Converter) was designed to enable legacy SSL (Source-Sink Library) APIs to retrieve real-time data from the Real-Time Optimized (RTO) feed hosted in the cloud. However, according to PCN206364, all legacy SSL APIs reached end-of-support on February 28, 2026. LPC will continue to provide session management and cloud connectivity support for RFA 8.x applications.

Therefore, it is acceptable to install LPC if you need to enable RFA 8.x applications to retrieve data from RTO.

Please note that RTO is a separate platform from RTDS. For more information, please refer to the following resources:

* The Real-Time Legacy Protocol Converter (LPC) 1.4.0 Installation Guide (Video)
* Migrating an application from Elektron Connect to Refinitiv Real-Time Optimized

In short, LPC is typically used by customers who have RFA 8.x applications and RTO credentials and want their RFA 8.x applications to retrieve real-time data from RTO. Since RFA 8.x applications cannot connect directly to RTO, LPC is required as a middleware component. (RTSK APIs (EMA and ETA) can directly connect to RTO so LPC is not required for RTSDK APIs).

LPC establishes the connection to RTO using the RTO credentials, while the RFA 8.x applications connect to LPC. LPC then bridges the communication between the applications and RTO, enabling the applications to retrieve real-time data from the RTO service.

Please note that data access permissions are controlled by the RTO credentials. Therefore, the data that an application can access through LPC is determined by the permissions associated with the RTO account used by LPC to establish the connection.

EXPLORE OUR SITES