The following configuration items control how the TREP Adapter connects to RTDS and RTO (Real-Time — Optimized).

Configure a connection to either RTDS or RTO — not both.

Do not set upa-priority-groups if you have configured an RTO connection.


To connect to RTO, use one of the methods below:


A space-separated list of location names, which should be obtained from LSEG. These locations will be the most suitable for the geographic location of the deployed TREP Adapter.

When specifying multiple locations, you can separate locations by spaces or use multiple instances of rto-discovery-locations for each location.

If rto-endpoint is configured then service discovery is not done.

Type: String array

Syntax: rto-discovery-locations location …​

Default: none

Previously: upa-rto-discovery-locations (TREP Adapter 7.1.5)

Since: TREP Adapter 7.1.6

Example 1. A server deployed in Europe

For a server deployed in Europe, the locations might be eu-west-1a and eu-west-1b:

Single line configuration
rto-discovery-locations eu-west-1a eu-west-1b
Multiple line configuration
rto-discovery-locations eu-west-1a
rto-discovery-locations eu-west-1b
Service discovery

If you configure rto-discovery-locations then the TREP Adapter performs service discovery to select an RTO endpoint.

Service discovery works as follows. Firstly, the TREP Adapter queries LSEG service discovery for a list of RTO endpoints that you are allowed to connect to. Once it has this list it will take the first configured rto-discovery-locations location and check the endpoint list for an entry that

  • is in the current rto-discovery-locations location

  • has a failover endpoint

If it finds a match then that endpoint is selected and used for all channel connections and re-connections.

If no match is found then the list is checked again using the next rto-discovery-locations location and so on until an endpoint is found or all rto-discovery-locations locations have been checked.

If no endpoint is found in the list then the TREP Adapter exits.


Specifies the URL of a single RTO endpoint. If you configure an rto-endpoint then no service discovery is attempted i.e. any rto-discovery-locations configuration is ignored.

If rto-endpoint is configured then service discovery is disabled.

Type: String

Syntax: rto-endpoint url

Default: none

Since: TREP Adapter 7.1.5


rto-endpoint  tcps://


Connection scheme for RTO

Type: String

Syntax: rto-scheme scheme

RTO schemes
Scheme Description




Secure TCPS


Web socket


Secure Web socket

Default: tcps

Previously: upa-rto-scheme (TREP Adapter 7.1.5)

Since: TREP Adapter 7.1.6


RTO client identifier

Type: String

Syntax: rto-client-id id

Default: none

Previously: upa-client-id (TREP Adapter 7.1.5)

Since: TREP Adapter 7.1.6


RTO client secret for v2 authorisation.

Only use this for v2 authorisation.

Type: String

Syntax: rto-client-secret secret

Default: none

Since: TREP Adapter 7.1.9


RTO password

Type: String

Syntax: rto-password password

Default: none

Previously: upa-password (TREP Adapter 7.1.5)

Since: TREP Adapter 7.1.6


RTO username for v1 authorisation.

If you are using v1 authorisation make sure that only rto-username is configured, don’t configure upa-username.

If you want to use v2 authorisation make sure that neither rto-username nor upa-username are configured.

Type: String

Syntax: rto-username username

Default: none

Since: TREP Adapter 7.1.6


To ensure that an RTDS connection is made make sure that neither rto-discovery-locations nor rto-endpoint is configured.


RTDS server hostname.

Type: String

Default: trep01


RTDS service name/port to connect to

Type: String

Default: 14002


RTDS username.

This configuration option is optional — use it only if your RTDS endpoint requires a username.

Do not set both upa-username and rto-username.

Type: String

Default: none