| Table of Contents |
|---|
Overiew
The TQL Command Line Interface (CLI) is a unified tool to manage your TQLEngine A-Stack (Single or Cluster) runtime. TQL CLI is packaged as part of your overall TQLEngine zip downloadvarious A-Stack Sub components. With just one tool, you can control multiple TQLEngines A-Stack runtimes within reachable cluster from the command line and automate them through scripts. Table below gives the list of TQL CLI Commands, description and components where those are applicable.
| TQL Subcommand | Description | Applicable A-Stack Component Runtime |
|---|---|---|
| engine | Individual A-Stack Runtime Management | A-StackPrime; A-StackTQLConsole; A-StackConfiguratorDaemon; A-StackMonitoringDashboard |
| protocol | Install protocol handlers | A-StackPrime; A-StackTQLConsole; |
| cluster | A-Stack Cluster Management | A-StackConfiguratorDaemon |
| monitoringconfig | Provision Alarms, and Monitoring dashboard | A-StackMonitoringDashboard |
| logserver | LogServer Management | A-StackPrime; A-StackTQLConsole |
Usage
After you download and install TQLEngine the TQL CLI tool is part of the bin folder. You need to set two environment variables :
- JAVA_HOME - Set this enviornment variable value to the location where Java JDK is installed.
- TQL_HOME - Set this environment variable value to the current installation location of the TQLEngine.
From the current install location on the command line you can invoke the tool using the command bin/tql
bin/tql -<Command> -<Subcommand> <Arguments>
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
$ bin/tql
$ bin/tql -engine -status
$ bin/tql -engine -start
$ bin/tql -engine -stop |
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
$ using CMD (under bin)
$ tql -engine -status
$ tql -engine -start
$ tql -engine -stop
$ using Git Bash (under bin)
$ ./tql -engine -status
$ ./tql -engine -start
$ ./tql -engine -stop |