Note: Please mind that work in Ignite Web Configuration is Console in ea
Jira | ||||
---|---|---|---|---|
|
Beta
First beta was released as part of ignite-1.6 release.Description from IGNITE-843:
Specific frameworks:
Install node.js locally.
Install Angular, LESS, and Grunt plugins into IDEA.
Use LESS instead of CSS.
Frameworks to be used:
------------------------------------
To run Web Configuration:
Ignite Web Agent is a java standalone application that allow to connect Ignite Grid to Ignite Web Console.
Ignite Web Agent communicates with grid nodes via REST interface and connects to Ignite Web Console via web-socket.
Two main functions of Ignite Web Agent:
1. Proxy between Ignite Web Console and Ignite Grid to execute SQL statements and collect metrics for monitoring.
You may need to specify URI for connect to Ignite REST server via "-n" option.
2. Proxy between Ignite Web Console and user RDBMS to collect database metadata for later CacheTypeMetadata configuration.
You may need to copy JDBC driver into "./jdbc-drivers" subfolder or specify path via "-d" option.
Usage example:
ignite-web-agent.sh
Configuration file:
Should be a file with simple line-oriented format as described here: http://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#load(java.io.Reader)
Available entries names:
tokens
server-uri
node-uri
driver-folder
Example configuration file:
tokens=1a2b3c4d5f,2j1s134d12
serverURI=https://console.example.com:3001
Security tokens:
1) By default security token of current user will be included into "default.properties" inside downloaded "ignite-web-agent-x.x.x.zip".
2) One can get/reset token in Web Console profile (https://<your_console_address>/settings/profile).
3) One may specify several comma separated tokens using configuration file or command line arguments of web agent.
Ignite Web agent requirements:
Options:
-h, --help
Print this help message
-c, --config
Path to configuration file
-d, --driver-folder
Path to folder with JDBC drivers, default value: ./jdbc-drivers
-n, --node-uri
URI for connect to Ignite REST server, default value: http://localhost:8080
-s, --server-uri
URI for connect to Ignite Web Console via web-socket protocol, default value: http://localhost:3001
-t, --tokens
User's security tokens
How to build:
To build from sources run following command in Ignite project root folder:
Code Block | ||
---|---|---|
| ||
mvn clean package -pl :ignite-web-agent -am -P web-console -DskipTests=true |
Ignite Web Console is an interactive configuration wizard and management tool for Apache Ignite.
How to deploy locally:
Change directory '$IGNITE_HOME/modules/web-console/src/main/js'.
Steps 1 - 7 should be executed once.
How to run console in development mode:
In new terminal change directory to '$IGNITE_HOME/modules/web-console/backend'.
If needed run "npm install --no-optional" (if dependencies changed) and run "npm start" to start backend.
In new terminal change directory to '$IGNITE_HOME/modules/web-console/frontend'.
If needed run "npm install --no-optional" (if dependencies changed) and start webpack in development mode "npm run dev".
How to deploy locally:
Steps 1 - 6 should be executed once.
How to run console in development mode: