Configuration

Tot Plugin Deployment

General Requirements

Each plugin may extend the requirements based on connectivity or compute needs, but as a baseline all of them need the following

  • JVM 17 (can be OpenJDK)

  • Inbound communication from the Tot server

  • Outbound communication to the Tot server

  • 1 core

  • >= 256Mb RAM

  • Linux 64-bit (RedHat or Debian families recommended)

Deployment Types

With the Anjana deployment kit, see https://wiki.anjanadata.com/es/instalacion/26.1/ansible-1 and https://wiki.anjanadata.com/es/instalacion/26.1/kubernetes

Execution Types

Check the configuration of the https://wiki.anjanadata.com/es/configuracion/26.1/backend to specify where the plugin configuration information should be retrieved from; all Anjana Data services follow the same pattern

Common Configurations

All plugins have two common configuration parts within their configuration file: the self-registration configuration, through which the plugin automatically registers itself to be used by the platform, and the configured functions, through which the plugin indicates to the platform which services it is able to perform.

Self-registration

As a general rule, this configuration does not need to be changed.

Each plugin shares two URL parameters used for:

  • totplugin.location

    • The plugin registers its own URL and port in tot so that it knows where to send requests for its technology.

  • totplugin.server.url

    • The plugin sends requests to tot at this URL and port

    • YAML
      totplugin:
        location: http://totpluginxxxxserver:15015/plugin/xxxx/api/v1
        server:
          url: http://totserver:15000/tot/
          keep-alive-seconds: 60
      


Function Activation

To activate the plugin's functions, the parameter totplugin.connection.[connection].aris must be set with an array indicating its function and on which triplet it will act:

YAML
totplugin:
  location: http://totpluginxxxxxserver:15015/plugin/xxxxx/api/v1
  server:
    url: http://totserver:15000/tot/
    keep-alive-seconds: 60
    connetion:
      - name: conectionnA
        aris:
          - ari: "anja:totplugin:extract:/xxxx/xxxx/xxxx/"
          - ari: "anja:totplugin:sample:/xxxx/xxxx/xxxx/"
          - ari: "anja:totplugin:im:/xxxx/xxxx/xxxx/"
            imAari: "anja:totplugin:im:/xxxx/xxxx/xxxx/"
        technology:
          ...
      - name: conectionnB
        aris:
          - ari: "anja:totplugin:extract:/xxxx/xxxx/xxxx/"
          - ari: "anja:totplugin:sample:/xxxx/xxxx/xxxx/"
          - ari: "anja:totplugin:im:/xxxx/xxxx/xxxx/"
            imAari: "anja:totplugin:im:/xxxx/xxxx/xxxx/"
        technology:
          ...

The triplet configuration manual must be followed for the correct configuration of the plugin's functions. https://wiki.anjanadata.com/es/configuracion/26.1/tripletas-para-plugins


Multi-connection

Since version 25.1, all Anjana Data plugins allow connecting to more than one connection supported by the plugin. As can be seen in the previous section, a list of connections can be defined, and even given a name (purely for informational purposes) to identify them more easily.

Within each connection, the ARIs are configured, as well as the properties specific to each connection and technology, about which more can be learned in each plugin's own documentation at https://wiki.anjanadata.com/es/integraciones/26.1/tot-plugins and in the example configuration YAML files at Nexus / com / anjana / documentation (login required)