Connection

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

upa-address

Type: String

Default: trep01

TREP server hostname.

upa-client-id

Type: String

Default: none

Since: TREP Adapter 7.1.5

RTO client identifier

upa-password

Type: String

Default: none

Since: TREP Adapter 7.1.5

RTO password

upa-port

Type: String

Default: 14002

TREP service name/port to connect to

upa-username

Type: String

Default: none

RTO/TREP username. Required for RTO. Optional for TREP — use only if your TREP endpoint requires a username.

upa-rto-discovery-locations

Type: String array

Default: none

Since: TREP Adapter 7.1.5

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

When the TREP Adapter starts, it sends the list of locations to the RTO Discovery server, and the RTO Discovery server returns a list of suitable RTO endpoints for the adapter to connect to. The adapter connects to the first returned endpoint because all endpoints are equivalent.

If upa-rto-discovery-locations is configured, then TREP connection configuration items upa-address and upa-port are ignored if configured. If the adapter fails to connect to RTO, it does not attempt to connect to TREP.

When specifying multiple locations, you can separate locations by spaces or use multiple instances of upa-rto-discovery-locations for each location. For example, for a server deployed in Europe, the locations might be eu-west-1a and eu-west-1b:

Single configuration item
upa-rto-discovery-locations eu-west-1a eu-west-1b
Multiple configuration items
upa-rto-discovery-locations eu-west-1a
upa-rto-discovery-locations eu-west-1b

upa-rto-scheme

Type: String

Default: tcps

Since: TREP Adapter 7.1.5

Connection scheme for RTO