Connection

Type: String

Default: none

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

Since: TREP Adapter 7.1.6

RTO client identifier

Type: String array

Default: none

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

Since: TREP Adapter 7.1.6

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 rto-discovery-locations is configured, then RTDS 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 RTDS.

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:

Type: String

Default: none

Previously: upa-password (TREP Adapter 7.1.5)

Since: TREP Adapter 7.1.6

RTO password

Type: String

Default: tcps

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

Since: TREP Adapter 7.1.6

Connection scheme for RTO

Type: String

Default: none

Since: TREP Adapter 7.1.6

RTO username.

Type: String

Default: trep01

RTDS server hostname.

Type: String

Default: 14002

RTDS service name/port to connect to

Type: String

Default: none

RTDS username.

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