Installing the TREP Adapter

This page describes how to install the TREP Adapter.

Contents:

Requirements
Pre-deployment tasks
Deploying the adapter
Configuring the adapter
Generating DataSource field definitions for Refinitiv fields
Starting and stopping the adapter

Requirements

To deploy the TREP Adapter, you require the following:

TREP Adapter installation kit (CPB_TREPAdapter-<version>.zip)
Caplin Deployment Framework 7

To ease log-file analysis across servers, time zones, and daylight savings transitions, we recommend that you set the system clocks of all hosts in a Caplin stack to UTC.

Pre-deployment tasks

Perform the following tasks before deploying the adapter:

Install the Deployment Framework. For more information, see Installing the Deployment Framework.
Deploy Liberator 7. For more information, see Installing Liberator.
Deploy Transformer 7. For more information, see Installing Transformer.

Deploying the adapter

Follow the steps below to deploy the TREP Adapter:

Copy the installation kit (CPB_TREPAdapter-<version>.zip) to your Deployment Framework’s kits directory.
From the root of your deployment framework, run the command below to stop all running components in the Deployment Framework:
```
$ ./dfw stop
```
From the root of your deployment framework, run the command below to deploy the TREP Adapter:
```
$ ./dfw deploy
```
Run the command below to specify the hostnames of the primary and secondary server on which the adapter should run (for more information on this command, see dfw hosts):
```
$ ./dfw hosts TREPAdapter <primary-server> <secondary-server>
```
If you are installing the adapter on a developer’s machine, you can specify localhost for both the primary and secondary servers: ./dfw hosts TREPAdapter localhost localhost

Configuring the adapter

Follow the steps below:

In the file global_config/TREPAdapter/DataSource/etc/upasrc.conf, configure your connection to RTO (Refinitiv Real-Time — Optimized) or RTDS:

Do not configure upa-priority-groups when you configure an RTO connection.
- You can connect to RTO using v1 or v2 authorisation
  - To connect to RTO with v1 authorisation and service discovery, add the configuration items below (available from TREP Adapter 7.1.5):
    
    rto-client_id
    
    rto-username
    
    rto-password
    
    rto-scheme
    
    rto-discovery-locations
  - To connect to RTO with v2 authorisation and service discovery, add the configuration items below (available from TREP Adapter 7.1.9):
    
    rto-client_id
    
    rto-client-secret
    
    rto-scheme
    
    rto-discovery-locations
  - When connecting to RTO you have the option to select a particular endpoint instead of using service discovery
    
    rto-endpoint
- To connect to RTDS, add the configuration items below:
  - upa-address
  - upa-port
  - upa-username (optional — use only if your RTDS endpoint requires a username)
If you want the TREP Adapter to supply historical charting data to Transformer’s Charting Service, then deploy the TS1 Decoder Service to Transformer. The TS1 Decoder Service transforms TS1 charting data served by the TREP Adapter into a format that the Charting Service can consume.

Generating DataSource field definitions for Refinitiv fields

After deploying the TREP Adapter for the first time, and after deploying any new version of the TREP Adapter, follow the instructions in Generating DataSource field definitions to update the fields-reuters.conf file with field definitions for Refinitiv fields.

Starting and stopping the adapter

To start the adapter, run the command below from the root directory of your Deployment Framework:

$ ./dfw start TREPAdapter

To stop the adapter, run the command below from the root directory of your Deployment Framework:

$ ./dfw stop TREPAdapter

See also:

Caplin Deployment Framework