This is an automated email from the ASF dual-hosted git repository.
dmagda pushed a commit to branch IGNITE-7595
in repository https://gitbox.apache.org/repos/asf/ignite.git
The following commit(s) were added to refs/heads/IGNITE-7595 by this push:
new 62aaf5d New Ignite Docs: ported and expanded the tools list
62aaf5d is described below
commit 62aaf5dcec1f63168840a25fe5c1dcb3617f9f7c
Author: Denis Magda <dma...@gridgain.com>
AuthorDate: Thu Oct 1 21:46:23 2020 -0700
New Ignite Docs: ported and expanded the tools list
---
docs/_data/toc.yaml | 20 +-
docs/_docs/images/tools/gg-control-center.png | Bin 0 -> 251342 bytes
.../images/tools/informatica-import-tables.png | Bin 0 -> 54326 bytes
.../images/tools/informatica-rel-connection.png | Bin 0 -> 40510 bytes
.../images/tools/pentaho-ignite-connection.png | Bin 0 -> 77439 bytes
.../images/tools/pentaho-new-transformation.png | Bin 0 -> 81849 bytes
.../tools/pentaho-running-and-inspecting-data.png | Bin 0 -> 56310 bytes
docs/_docs/images/tools/tableau-choose_dsn_01.png | Bin 0 -> 12515 bytes
docs/_docs/images/tools/tableau-choose_dsn_02.png | Bin 0 -> 12860 bytes
.../images/tools/tableau-choosing_driver_01.png | Bin 0 -> 100372 bytes
.../images/tools/tableau-creating_dataset.png | Bin 0 -> 59092 bytes
.../_docs/images/tools/tableau-edit_connection.png | Bin 0 -> 7123 bytes
.../images/tools/tableau-visualizing_data.png | Bin 0 -> 86105 bytes
docs/_docs/images/tools/visor-cmd.png | Bin 0 -> 208235 bytes
docs/_docs/{ => tools}/control-script.adoc | 0
docs/_docs/tools/gg-control-center.adoc | 20 ++
docs/_docs/tools/informatica.adoc | 290 +++++++++++++++++++++
docs/_docs/tools/pentaho.adoc | 51 ++++
docs/_docs/{ => tools}/sqlline.adoc | 2 +-
docs/_docs/tools/tableau.adoc | 52 ++++
docs/_docs/tools/visor-cmd.adoc | 54 ++++
21 files changed, 484 insertions(+), 5 deletions(-)
diff --git a/docs/_data/toc.yaml b/docs/_data/toc.yaml
index 4e7e349..396e09e 100644
--- a/docs/_data/toc.yaml
+++ b/docs/_data/toc.yaml
@@ -367,10 +367,6 @@
url: SQL/ODBC/error-codes
- title: REST API
url: restapi
-- title: Control Script
- url: control-script
-- title: SQLLine
- url: sqlline
- title: Extensions and Integrations
items:
- title: Spring
@@ -473,6 +469,22 @@
url: cpp-specific/cpp-platform-interoperability
- title: Objects Lifetime
url: cpp-specific/cpp-objects-lifetime
+- title: Tools
+ items:
+ - title: Control Script
+ url: tools/control-script
+ - title: Visor CMD
+ url: tools/visor-cmd
+ - title: GridGain Control Center
+ url: tools/gg-control-center
+ - title: SQLLine
+ url: tools/sqlline
+ - title: Tableau
+ url: tools/tableau
+ - title: Informatica
+ url: tools/informatica
+ - title: Pentaho
+ url: tools/pentaho
- title: Plugins
url: plugins
- title: SQL Reference
diff --git a/docs/_docs/images/tools/gg-control-center.png
b/docs/_docs/images/tools/gg-control-center.png
new file mode 100644
index 0000000..d884adb
Binary files /dev/null and b/docs/_docs/images/tools/gg-control-center.png
differ
diff --git a/docs/_docs/images/tools/informatica-import-tables.png
b/docs/_docs/images/tools/informatica-import-tables.png
new file mode 100644
index 0000000..e1f4cfc
Binary files /dev/null and
b/docs/_docs/images/tools/informatica-import-tables.png differ
diff --git a/docs/_docs/images/tools/informatica-rel-connection.png
b/docs/_docs/images/tools/informatica-rel-connection.png
new file mode 100644
index 0000000..097a009
Binary files /dev/null and
b/docs/_docs/images/tools/informatica-rel-connection.png differ
diff --git a/docs/_docs/images/tools/pentaho-ignite-connection.png
b/docs/_docs/images/tools/pentaho-ignite-connection.png
new file mode 100644
index 0000000..1b15d6a
Binary files /dev/null and
b/docs/_docs/images/tools/pentaho-ignite-connection.png differ
diff --git a/docs/_docs/images/tools/pentaho-new-transformation.png
b/docs/_docs/images/tools/pentaho-new-transformation.png
new file mode 100644
index 0000000..58bbc4c
Binary files /dev/null and
b/docs/_docs/images/tools/pentaho-new-transformation.png differ
diff --git a/docs/_docs/images/tools/pentaho-running-and-inspecting-data.png
b/docs/_docs/images/tools/pentaho-running-and-inspecting-data.png
new file mode 100644
index 0000000..e138ef4
Binary files /dev/null and
b/docs/_docs/images/tools/pentaho-running-and-inspecting-data.png differ
diff --git a/docs/_docs/images/tools/tableau-choose_dsn_01.png
b/docs/_docs/images/tools/tableau-choose_dsn_01.png
new file mode 100644
index 0000000..5719d7a
Binary files /dev/null and b/docs/_docs/images/tools/tableau-choose_dsn_01.png
differ
diff --git a/docs/_docs/images/tools/tableau-choose_dsn_02.png
b/docs/_docs/images/tools/tableau-choose_dsn_02.png
new file mode 100644
index 0000000..95cfed4
Binary files /dev/null and b/docs/_docs/images/tools/tableau-choose_dsn_02.png
differ
diff --git a/docs/_docs/images/tools/tableau-choosing_driver_01.png
b/docs/_docs/images/tools/tableau-choosing_driver_01.png
new file mode 100644
index 0000000..03f9c9e
Binary files /dev/null and
b/docs/_docs/images/tools/tableau-choosing_driver_01.png differ
diff --git a/docs/_docs/images/tools/tableau-creating_dataset.png
b/docs/_docs/images/tools/tableau-creating_dataset.png
new file mode 100644
index 0000000..33dc98d
Binary files /dev/null and
b/docs/_docs/images/tools/tableau-creating_dataset.png differ
diff --git a/docs/_docs/images/tools/tableau-edit_connection.png
b/docs/_docs/images/tools/tableau-edit_connection.png
new file mode 100644
index 0000000..ec35e68
Binary files /dev/null and
b/docs/_docs/images/tools/tableau-edit_connection.png differ
diff --git a/docs/_docs/images/tools/tableau-visualizing_data.png
b/docs/_docs/images/tools/tableau-visualizing_data.png
new file mode 100644
index 0000000..e5351ed
Binary files /dev/null and
b/docs/_docs/images/tools/tableau-visualizing_data.png differ
diff --git a/docs/_docs/images/tools/visor-cmd.png
b/docs/_docs/images/tools/visor-cmd.png
new file mode 100644
index 0000000..55249eb
Binary files /dev/null and b/docs/_docs/images/tools/visor-cmd.png differ
diff --git a/docs/_docs/control-script.adoc
b/docs/_docs/tools/control-script.adoc
similarity index 100%
rename from docs/_docs/control-script.adoc
rename to docs/_docs/tools/control-script.adoc
diff --git a/docs/_docs/tools/gg-control-center.adoc
b/docs/_docs/tools/gg-control-center.adoc
new file mode 100644
index 0000000..33ddc3a
--- /dev/null
+++ b/docs/_docs/tools/gg-control-center.adoc
@@ -0,0 +1,20 @@
+= Using GridGain Control Center With Apache Ignite
+
+== Overview
+
+https://www.gridgain.com/products/software/control-center[GridGain Control
Center, window=_blank] is a management and
+monitoring tool designed for Apache Ignite that allows you to do the following:
+
+* Monitor the state of the cluster with customizable dashboards.
+* Define custom alerts to track and react on over 200 cluster, node, and
storage metrics.
+* Execute and optimize SQL queries as well as monitor already running commands.
+* Perform OpenCensus-based root cause analysis with visual debugging of API
calls as they execute on nodes across the cluster.
+* Take full, incremental, and continuous cluster backups to enable disaster
recovery in the event of data loss or corruption.
+* And more...
+
+image::images/tools/gg-control-center.png[GridGain Contro Center]
+
+== Installation and Usage
+
+Refer to the
https://www.gridgain.com/docs/control-center/latest/overview[official
documentation of GridGain Control Center, window=_blank]
+for detailed installation and usage instructions.
diff --git a/docs/_docs/tools/informatica.adoc
b/docs/_docs/tools/informatica.adoc
new file mode 100644
index 0000000..d97ba0d
--- /dev/null
+++ b/docs/_docs/tools/informatica.adoc
@@ -0,0 +1,290 @@
+= Using Informatica With Apache Ignite
+
+== Overview
+
+Informatica is a cloud data management and data integration tool. You can
connect Informatica to Ignite through the ODBC driver.
+
+== Connecting from Informatica PowerCenter Designer
+
+You need to install the 32-bit Ignite OBDC driver to connect an Ignite cluster
with the Power Center Designer. Use the
+following links to build and install the driver:
+
+* link:SQL/ODBC/odbc-driver#installing-on-windows[Install the driver on
Windows]
+* link:SQL/ODBC/connection-string-dsn#configuring-dsn[Configure DSN]
+
+Then do the following:
+
+. Select the `Sources` or `Targets` menu and choose `Import from Database...`
to import tables from Ignite.
+. Connect to the cluster by choosing `Apache Ignite DSN` as the ODBC data
source.
+
+image::images/tools/informatica-import-tables.png[Informatica Import Tables]
+
+== Installing Ignite ODBC on an Informatica Service Node
+
+Refer to the link:SQL/ODBC/odbc-driver#building-on-linux[Building on Linux] and
+link:SQL/ODBC/odbc-driver#installing-on-linux[Installing on Linux]
instructions to install the Ignite ODBC on an Ignite service node.
+
+Informatica uses configuration files referenced by the `$ODBCINI` and
`$ODBCISTINI` environment variables
+(https://kb.informatica.com/howto/6/Pages/19/499306.aspx[Configure the UNIX
environment for ODBC, window=_blank]). Configure
+the Ignite ODBC driver and create a new DSN as shown below:
+
+[tabs]
+--
+tab:odbc.ini[]
+[source,text]
+----
+[ApacheIgnite]
+Driver = /usr/local/lib/libignite-odbc.so
+Description = Apache Ignite ODBC
+Address = 192.168.0.105
+User = ignite
+Password = ignite
+Schema = PUBLIC
+----
+tab:odbcinst.ini[]
+[source,text]
+----
+[ApacheIgnite]
+Driver = /usr/local/lib/libignite-odbc.so
+----
+--
+
+To check the ODBC connection, use the `ssgodbc.linux64` utility included in
the Informatica deployment, as show below:
+
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+<INFORMATICA_HOME>/tools/debugtools/ssgodbc/linux64/ssgodbc.linux64 -d
ApacheIgnite -u ignite -p ignite -v
+----
+--
+
+If the unixODBC or Ignite ODBC libraries are not installed in the default
directory - `/usr/local/lib`, add them to `LD_LIBRARY_PATH`
+and then check the connection, like so:
+
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+UNIXODBC_LIB=/opt/unixodbc/lib/
+IGNITE_ODBC_LIB=/opt/igniteodbc/lib
+LD_LIBRARY_PATH=<UNIXODBC_LIB>:<IGNITE_ODBC_LIB>
+
+<INFORMATICA_HOME>/tools/debugtools/ssgodbc/linux64/ssgodbc.linux64 -d
ApacheIgnite -u ignite -p ignite -v
+----
+--
+
+== Configuring Relation Connection
+
+Choose `Connections > Relational..` to show the Relational Connection Browser.
+
+Select the ODBC type and create a new connection.
+
+image::images/tools/informatica-rel-connection.png[Informatica Relational
Connection]
+
+
+== Installing Ignite ODBC on Suse 11.4
+
+Follow the steps below to build and install Ignite with the Ignite ODBC driver
on Suse 11.4:
+
+. Add repositories - `oss`, `non-oss`, `openSUSE_Factory`, `devel_gcc`
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+sudo zypper ar http://download.opensuse.org/distribution/11.4/repo/oss/ oss
+sudo zypper ar http://download.opensuse.org/distribution/11.4/repo/non-oss/
non-oss
+sudo zypper ar
https://download.opensuse.org/repositories/devel:/tools:/building/openSUSE_Factory/
openSUSE_Factory
+sudo zypper ar http://download.opensuse.org/repositories/devel:/gcc/SLE-11/
devel_gcc
+----
+--
+
+. Install `automake` and `autoconf`
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+sudo zypper install autoconf automake
+----
+--
+
+. Install `libtool`
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+sudo zypper install libtool-2.4.6-7.1.x86_64
+
+Loading repository data...
+Reading installed packages...
+Resolving package dependencies...
+
+Problem: nothing provides m4 >= 1.4.16 needed by libtool-2.4.6-7.1.x86_64
+ Solution 1: do not install libtool-2.4.6-7.1.x86_64
+ Solution 2: break libtool-2.4.6-7.1.x86_64 by ignoring some of its
dependencies
+
+Choose from above solutions by number or cancel [1/2/c] (c): 2
+----
+--
+
+. Install OpenSSL
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+sudo zypper install openssl openssl-devel
+
+Loading repository data...
+Reading installed packages...
+'openssl-devel' not found in package names. Trying capabilities.
+Resolving package dependencies...
+
+Problem: libopenssl-devel-1.0.0c-17.1.x86_64 requires zlib-devel, but this
requirement cannot be provided
+ uninstallable providers: zlib-devel-1.2.5-8.1.i586[oss]
+ zlib-devel-1.2.5-8.1.x86_64[oss]
+ Solution 1: downgrade of zlib-1.2.7-0.12.3.x86_64 to zlib-1.2.5-8.1.x86_64
+ Solution 2: do not ask to install a solvable providing openssl-devel
+ Solution 3: do not ask to install a solvable providing openssl-devel
+ Solution 4: break libopenssl-devel-1.0.0c-17.1.x86_64 by ignoring some of its
dependencies
+
+Choose from above solutions by number or cancel [1/2/3/4/c] (c): 1
+----
+--
+
+. Install the GCC Compiler
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+sudo zypper install gcc5 gcc5-c++
+
+Loading repository data...
+Reading installed packages...
+Resolving package dependencies...
+2 Problems:
+Problem: gcc5-5.5.0+r253576-1.1.x86_64 requires libgcc_s1 >=
5.5.0+r253576-1.1, but this requirement cannot be provided
+Problem: gcc5-c++-5.5.0+r253576-1.1.x86_64 requires gcc5 = 5.5.0+r253576-1.1,
but this requirement cannot be provided
+
+Problem: gcc5-5.5.0+r253576-1.1.x86_64 requires libgcc_s1 >=
5.5.0+r253576-1.1, but this requirement cannot be provided
+ uninstallable providers: libgcc_s1-5.5.0+r253576-1.1.i586[devel_gcc]
+ libgcc_s1-5.5.0+r253576-1.1.x86_64[devel_gcc]
+ libgcc_s1-6.4.1+r251631-80.1.i586[devel_gcc]
+ libgcc_s1-6.4.1+r251631-80.1.x86_64[devel_gcc]
+ libgcc_s1-7.3.1+r258812-103.1.i586[devel_gcc]
+ libgcc_s1-7.3.1+r258812-103.1.x86_64[devel_gcc]
+ libgcc_s1-8.1.1+r260570-32.1.i586[devel_gcc]
+ libgcc_s1-8.1.1+r260570-32.1.x86_64[devel_gcc]
+ Solution 1: install libgcc_s1-8.1.1+r260570-32.1.x86_64 (with vendor change)
+ SUSE LINUX Products GmbH, Nuernberg, Germany -->
obs://build.opensuse.org/devel:gcc
+ Solution 2: do not install gcc5-5.5.0+r253576-1.1.x86_64
+ Solution 3: do not install gcc5-5.5.0+r253576-1.1.x86_64
+ Solution 4: break gcc5-5.5.0+r253576-1.1.x86_64 by ignoring some of its
dependencies
+
+Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c]
(c): 1
+
+Problem: gcc5-c++-5.5.0+r253576-1.1.x86_64 requires gcc5 = 5.5.0+r253576-1.1,
but this requirement cannot be provided
+ uninstallable providers: gcc5-5.5.0+r253576-1.1.i586[devel_gcc]
+ gcc5-5.5.0+r253576-1.1.x86_64[devel_gcc]
+ Solution 1: install libgomp1-8.1.1+r260570-32.1.x86_64 (with vendor change)
+ SUSE LINUX Products GmbH, Nuernberg, Germany -->
obs://build.opensuse.org/devel:gcc
+ Solution 2: do not install gcc5-c++-5.5.0+r253576-1.1.x86_64
+ Solution 3: do not install gcc5-c++-5.5.0+r253576-1.1.x86_64
+ Solution 4: break gcc5-c++-5.5.0+r253576-1.1.x86_64 by ignoring some of its
dependencies
+
+Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c]
(c): 1
+Resolving dependencies...
+Resolving package dependencies...
+
+Problem: gcc5-c++-5.5.0+r253576-1.1.x86_64 requires libstdc++6-devel-gcc5 =
5.5.0+r253576-1.1, but this requirement cannot be provided
+ uninstallable providers:
libstdc++6-devel-gcc5-5.5.0+r253576-1.1.i586[devel_gcc]
+ libstdc++6-devel-gcc5-5.5.0+r253576-1.1.x86_64[devel_gcc]
+ Solution 1: install libstdc++6-8.1.1+r260570-32.1.x86_64 (with vendor change)
+ SUSE LINUX Products GmbH, Nuernberg, Germany -->
obs://build.opensuse.org/devel:gcc
+ Solution 2: do not install gcc5-c++-5.5.0+r253576-1.1.x86_64
+ Solution 3: do not install gcc5-c++-5.5.0+r253576-1.1.x86_64
+ Solution 4: break gcc5-c++-5.5.0+r253576-1.1.x86_64 by ignoring some of its
dependencies
+
+Choose from above solutions by number or cancel [1/2/3/4/c] (c): 1
+----
+--
+
+. Provide symlinks to compiler executables.
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+sudo rm /usr/bin/gcc
+sudo rm /usr/bin/g++
+
+sudo ln -s /usr/bin/g++-5 /usr/bin/g++
+sudo ln -s /usr/bin/gcc-5 /usr/bin/gcc
+----
+--
+
+. Install unixODBC from sources. Download and install the latest
unixODBC(2.3.6 or later) library from http://www.unixodbc.org/.
+
+. Check that all required libraries and tools are installed with specified
versions.
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+1. libtool --version
+libtool (GNU libtool) 2.4.6
+2. m4 --version
+m4 (GNU M4) 1.4.12
+3. autoconf --version
+autoconf (GNU Autoconf) 2.69
+4. automake --version
+automake (GNU automake) 1.16.1
+5. openssl version
+OpenSSL 1.0.0c 2 Dec 2010
+6. g++ --version
+g++ (SUSE Linux) 5.5.0 20171010 [gcc-5-branch revision 253640]
+7. JDK 1.8
+----
+--
+
+. Check if the environment variable `JAVA_HOME` is set. Then issue the
following commands:
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+cd $IGNITE_HOME/platforms/cpp
+export LDFLAGS=-lrt
+
+libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
+./configure --enable-odbc
+make
+sudo make install
+----
+--
+. Reboot the system.
+
+. Install the ODBC driver
++
+[tabs]
+--
+tab:Shell[]
+[source,shell]
+----
+sudo odbcinst -i -d -f
$IGNITE_HOME/platforms/cpp/odbc/install/ignite-odbc-install.ini
+----
+--
diff --git a/docs/_docs/tools/pentaho.adoc b/docs/_docs/tools/pentaho.adoc
new file mode 100644
index 0000000..ae5e5c9
--- /dev/null
+++ b/docs/_docs/tools/pentaho.adoc
@@ -0,0 +1,51 @@
+= Using Pentaho With Apache Ignite
+
+== Overview
+
+http://www.pentaho.com[Pentaho, window=_blank] is a comprehensive platform
that provides the ability to extract,
+transform, visualize, and analyze your data easily. Pentaho Data Integration
uses the Java Database Connectivity (JDBC)
+API in order to connect to your database.
+
+Apache Ignite is shipped with its own implementation of the JDBC driver which
makes it possible to connect to Ignite
+from the Pentaho platform and analyze the data stored in a distributed Ignite
cluster.
+
+== Installation and Configuration
+
+* Download and Install Pentaho platform. Refer to the official
https://help.pentaho.com/Documentation/7.1/Installation[Pentaho documentation,
window=_blank].
+* After Pentaho is successfully installed, you will need to install the Apache
Ignite JDBC Driver using the JDBC Distribution Tool.
+To do so, download Apache Ignite and locate
`{apache-ignite}/libs/ignite-core-{version}.jar` and copy the file to the
`{pentaho}/jdbc-distribution` directory.
+* Open a command line tool, navigate to the `{pentaho}/jdbc-distribution`
directory and run the following script `./distribute-files.sh
ignite-core-{version}.jar`
+
+== Ignite JDBC Driver Setup
+
+The next step is to set up the JDBC driver and connect to the cluster. Below
you will find the minimal number of actions
+that need to be taken. Refer to the link:SQL/JDBC/jdbc-driver[JDBC Thin
Driver] documentation for the more details.
+
+. Open your command line tool, go to the
`{pentaho}/design-tools/data-integration` directory and launch Pentaho Data
Integration using the `./spoon.sh` script.
+. Once the screen like the one below appears, click on the `File` menu option
and create a new transformation - `New -> Transformation`
++
+image::images/tools/pentaho-new-transformation.png[Pentaho New Transformation]
+
+. You can create a new Database Connection using setting the following
parameters in Pentaho:
++
+[opts="header"]
+|===
+|Pentaho Property Name | Value
+
+| Connection Name| Set some custom name such as `IgniteConnection`
+| Connection Type| Select the `Generic database` option.
+| Access| Select the `Native (JDBC)` option.
+| Custom Connection URL| `jdbc:ignite:thin://localhost:10800` or the real
address of a cluster node to connect to.
+| Custom Driver Class Name| `org.apache.ignite.IgniteJdbcThinDriver`
+|===
+
+. Click the `Test` button to check that the connection​ can be established:
++
+image::images/tools/pentaho-ignite-connection.png[Pentaho Ignite Connection]
+
+== Data Querying and Analysis
+
+Once the connection between Ignite and Pentaho is established , you can query,
transform, and analyze the data in a
+variety of ways supported by Pentaho. For more details, refer to the official
Pentaho documentation.
+
+image::images/tools/pentaho-running-and-inspecting-data.png[Pentaho Running
Queries]
diff --git a/docs/_docs/sqlline.adoc b/docs/_docs/tools/sqlline.adoc
similarity index 99%
rename from docs/_docs/sqlline.adoc
rename to docs/_docs/tools/sqlline.adoc
index 20489b5..9717919 100644
--- a/docs/_docs/sqlline.adoc
+++ b/docs/_docs/tools/sqlline.adoc
@@ -1,4 +1,4 @@
-= SQLLine
+= Using SQLLine With Apache Ignite
Command line tool for SQL connectivity.
diff --git a/docs/_docs/tools/tableau.adoc b/docs/_docs/tools/tableau.adoc
new file mode 100644
index 0000000..73b4132
--- /dev/null
+++ b/docs/_docs/tools/tableau.adoc
@@ -0,0 +1,52 @@
+= Using Tableau With Apache Ignite
+
+== Overview
+
+http://www.tableau.com[Tableau, window=_blank] is an interactive
data-visualization tool focused on business intelligence.
+It uses ODBC APIs to connect to a variety of databases and data platforms
allowing to analyze data stored there.
+
+You can use the link:SQL/ODBC/odbc-driver[Ignite ODBC driver] to interconnect
Ignite with Tableau and analyze the data stored
+in the cluster.
+
+== Installation and Configuration
+
+To connect to an Apache Ignite cluster from Tableau, you need to do the
following:
+
+* Download and install Tableau Desktop. Refer to an official Tableau
documentation located on http://www.tableau.com[the product's main website,
window=_blank].
+* Install the Apache Ignite ODBC driver on a Windows or Unix-based operating
system. The detailed instructions can be found on the
link:SQL/ODBC/odbc-driver[driver's configuration page].
+* Finalize the driver configuration by
link:SQL/ODBC/connection-string-dsn#configuring-dsn[setting up a DSN (Data
Source Name)].
+Tableau will connect to the DSN configured at this step.
+* The ODBC driver communicates to the Ignite cluster over a so-called `ODBC
processor`. Make sure that this component is
+enabled on the
link:SQL/ODBC/querying-modifying-data#configuring-the-cluster[cluster side].
+
+After all the above steps are accomplished, you can connect to the cluster and
analyze its data.
+
+== Connecting to Ignite Cluster
+
+. Launch Tableau application and find `Other Databases (ODBC)` setting located
under `Connect` \-> `To a Server` \-> `+More...+` window.
++
+image::images/tools/tableau-choosing_driver_01.png[Tableau Driver Selection]
+
+
+. Click on the `Edit connection` reference.
++
+image::images/tools/tableau-edit_connection.png[Tableau Edit Connection]
+
+. Set the `DSN` property to the name you configured before. In the example
below it's equal to `LocalApacheIgniteDSN`.
+Once this is done, click on the `Connect` button.
++
+image::images/tools/tableau-choose_dsn_01.png[Tableau Choose DSN]
+
+. Tableau will try to check the connection by opening a temporary one. If the
validation succeeds, the `Sign In` button
+as well as additional connection related fields will become active. Click on
`Sign In` to finalize the connection process.
++
+image::images/tools/tableau-choose_dsn_02.png[Tableau Choose DSN]
+
+== Data Querying and Analysis
+
+Once the connection is successfully established between Ignite and Tableau,
the data can be queried and analyzed in a
+variety of ways supported by Tableau. For more details, refer to the
http://www.tableau.com/learn/training[official Tableau documentation,
window=_blank].
+
+image::images/tools/tableau-creating_dataset.png[Tableau Creating DataSet]
+
+image::images/tools/tableau-visualizing_data.png[Tableau Visualizing Data]
diff --git a/docs/_docs/tools/visor-cmd.adoc b/docs/_docs/tools/visor-cmd.adoc
new file mode 100644
index 0000000..ffb3ffb
--- /dev/null
+++ b/docs/_docs/tools/visor-cmd.adoc
@@ -0,0 +1,54 @@
+= Visor CMD
+
+== Overview
+
+Visor Command Line Interface (CMD) is a command-line tool for Ignite clusters
monitoring. It provides basic statistics
+about cluster nodes, caches, and compute tasks. It also lets you manage the
size of your cluster by starting or stopping nodes.
+
+[NOTE]
+====
+[discrete]
+=== Ignite Control Script
+The link:tools/control-script[Control Script] is another command-line tool
developed by the Ignite community.
+It complements and expands capabilities of Visor CMD.
+====
+
+image::images/tools/visor-cmd.png[Visor CMD]
+
+== Usage
+
+Ignite ships the `IGNITE_HOME/bin/ignitevisorcmd.{sh|bat}` script that starts
Visor CMD. To connect Visor CMD to a cluster,
+use the `open` command.
+
+The following commands are supported by Visor. To get full information on a
command, type `help "cmd"` or `? "cmd"`.
+
+[cols="15%,15%,70%", opts="header"]
+|===
+|Command | Alias | Description
+
+| `ack`| | Acks arguments on all remote nodes.
+| `alert`| | Alerts for user-defined events.
+| `cache`| | Prints cache statistics, clears cache, prints list of all entries
from cache.
+| `close`| | Disconnects Visor CMD console from the cluster.
+| `config`| | Prints nodes' configurations.
+| `deploy`| | Copies file or folder to remote host.
+| `disco`| | Prints topology change log.
+| `events`| | Prints events from a node.
+| `gc`| | Runs GC on remote nodes.
+| `help`| `?`| Visor CMD's help.
+| `kill`| | Kills or restarts a node.
+| `log`| | Starts or stops the cluster-wide events logging.
+| `mclear`| | Clears Visor CMD's memory variables.
+| `mget`| | Gets Visor CMD' memory variables
+| `mlist`| | Prints Visor CMD's memory variables.
+| `node`| | Prints node's statistics.
+| `open`| | Connects Visor CMD to the cluster.
+| `ping`| | Pings a node.
+| `quit`| | Close Visor CMD's connection.
+| `start`| | Starts or restarts remote nodes.
+| `status`| `!`| Prints detailed Visor CMD's status.
+| `tasks`| | Prints tasks' execution statistics.
+| `top`| | Prints the current cluster topology.
+| `vvm`| | Opens VisualVM for nodes in the cluster.
+|===
+
