# Deployment And Administration Guide

## Installation

### From Package

For Ubuntu 14.04 and CentOS 7 a package is provided by the INDIGO DataCloud team. In order to install the packages using the system package manager, the repository needs to be added. This is done by adding the INDIGO DataCloud package repository to your system.

The INDIGO DataCloud repository can be found at [INDIGO-DataCloud Software Repository](http://repo.indigo-datacloud.eu).

For information how to add the repository to your system, please refer to the documentation of your respective operating system.

#### Ubuntu 14.04

After adding the repository, one needs to update the package list and then install the Token Translation Service.

```
apt update
apt install tts
```

#### CentOS 7

After adding the repository, one needs to update the package list and then install the Token Translation Service.

```
yum update
yum install tts
```

### From Source

To be able to install the Token Translation Service from source, you need Erlang OTP 18.1 or newer installed.

Pre-built package for your operating system can be found at [Erlang Solutions](https://www.erlang-solutions.com/resources/download.html). Just download and install it.

Then follow the next few steps:

* clone the git repository
* build the package yourself
* install the package

  ```
  git clone https://github.com/indigo-dc/tts
  cd tts
  make clean
  make package
  ```

The package can be found in `./package/packages`.

## Upgrade WaTTS

### General

The best way to upgrade WaTTS is to stop it before upgrading:

```
watts stop
```

then upgrade WaTTs, either using the package management system of your distribution or manually. After upgrading WaTTs start it again

```
watts start
```

### v1.4.0 to v1.5.0

A new configuration setting 'allow\_insecure\_plugins' is added, which defaults to 'false'. If your WaTTS instance is using plugins that do not yet support parameter passing via stdin you need to add this to your config and set it to 'true'.

### v1.3.0 to v1.4.0

Nothing special needs to be done.

### v1.2.1 to v1.3.0

The configuration enable\_docs is renamed to enable\_user\_doc, so if you have it in your watts.conf please rename it.

### v1.2.0 to v1.2.1

Nothing special needs to be done by the administrator. WaTTS 1.2.1 includes only a bug-fix.

### v1.1.0 to v1.2.0

Nothing special needs to be done, WaTTS 1.2.0 includes only new features.

### v1.0.0 to v1.1.0

Only two new settings are needed in the watts.conf:

* nodename: `nodename = watts@127.0.0.1`
* distributed\_cookie: `distributed_cookie = watts`

Add these settings to your watts.conf and then restart WaTTs.

### v0.4.1 to v1.0.0

Upgrading from TTS to WaTTS is **not** straightforward as both the configuration file and the plugin API have changed. You can not reuse any old configuration or plugins.

For a clean and fresh setup, do the following:

* stop the TTS, with `tts stop`
* install the new package (still called `tts`)
* configure WaTTS according to your needs (see below for reusing existing data)
* start WaTTS, with `watts start`

If you really need to use the existing data, ensure the following:

* a plugin using the same data does exist for WaTTS 1.0
* you configure your newly set up WaTTS to use the existing *sqlite db*
* you configure the plugin to use the existing data

### v0.2.2 to v0.4.0 (called TTS)

Upgrading the TTS from version 0.2.2 to 0.4.0 is straightforward. As the configuration files are compatible the only actions to do are:

* stop the TTS `tts stop`
* install the new package
* start the newly installed TTS `tts start`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://indigo-dc.gitbook.io/token-translation-service/admin.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.