Installation

Installing the Controller from a .tar.gz File (single node installation)

Tonomi Platform Enterprise Controller is distributed as a single archive containing all required dependencies.

  1. Unpack the archive into a temporary folder:

    tar -xzf %%PKG_NAME%%.tar.gz -C /tmp
    
  2. Run the installation script.

    Note

    This step requires root privileges.

    The installation script requires the Administrator to provide an answer file and parameter set. The answer file is unique for every Tonomi Platform Enterprise customer. Please contact your customer representative to obtain the proper answer file for your environment.

    Mandatory parameters:

    • -f </path/to/answer.file> : Answer file’s location
    • PUBLICADDRESS=<addr> : Address of the server that hosts the controller (can be a DNS name or an IP address). Will be used to generate links displayed on the portal.

    Optional parameters:

    • ENV_USER=<someuser> : User which will be the owner of the Controller processes. The user should exist. Default: qubell
    • PREFIX=<somepath> : Path to installation location of the Controller. Default: /opt/qubell

    Parameters must be passed to the installation script after the answer file parameter. For example, to set PUBLICADDRESS=192.168.1.100, the installation script should be run as:

    install.sh -f /path/to/answer.file PUBLICADDRESS=192.168.1.100

Installing the Controller from a .tar.gz File (HA mode)

Prerequisites:

  1. 2 hosts with CentOS 6 installed. Both should have resolvable from each other hostnames. Using /etc/hosts is an option if the hostnames are not DNS-resolvable.
  2. External mongoDB cluster with 2 databases (cobalt and worker) created.

Install process:

Unpack controller distribution archive on both nodes, like in single mode install.

Mandatory parameters:

  • -f </path/to/answer.file> : Answer file’s location
  • PUBLICADDRESS=<addr> : Address of the server that hosts the controller (can be a DNS name or an IP address). Will be used to generate links displayed on the portal.
  • CLUSTER_NODES=<hostname_of_1_node>,<hostname_of_second_node>
  • MONGO_COBALT_URL=<url_to_mongo_db_for_cobalt>
  • MONGO_WORKER_URL=<url_to_mongo_db_for_worker>

Here is example:

install.sh -f /path/to/answer.file PUBLICADDRESS=192.168.1.100 CLUSTER_NODES=node1.zone.int,node2.zone.int MONGO_COBALT_URL="mongodb://cobaltuser:cobaltpass@mymongohost.zone.int:27017/cobalt"  MONGO_COBALT_URL="mongodb://workeruser:workerpass@mymongohost.zone.int:27017/worker"