Skip to content

Commit

Permalink
gg*{sh,bat} renamed to ignite*{sh,bat}
Browse files Browse the repository at this point in the history
  • Loading branch information
Anton Vinogradov committed Jan 30, 2015
1 parent 115f597 commit 7e8ea4f
Show file tree
Hide file tree
Showing 146 changed files with 182 additions and 182 deletions.
4 changes: 2 additions & 2 deletions assembly/libs/readme.txt
Expand Up @@ -2,15 +2,15 @@ Apache Ignite Dependencies
--------------------------

Current folder contains JAR files for all Apache Ignite modules along with their dependencies.
When node is started using 'ggstart.{sh|bat}' script, all JARs and classes located in
When node is started using 'ignite.{sh|bat}' script, all JARs and classes located in
'libs' folder and all its sub-folders except 'optional' are added to classpath of the node.

By default, only Apache Ignite core JAR and a minimum set of modules is enabled, while other
modules are located in 'optional' folder and therefore disabled.

To enable any of optional Ignite modules when starting a standalone node,
move corresponding module folder from 'libs/optional' to 'libs' before running
'ggstart.{sh|bat}' script. The content of the module folder will be added to
'ignite.{sh|bat}' script. The content of the module folder will be added to
classpath in this case.

If you need to add your own classes to classpath of the node (e.g., task classes), put them
Expand Down
4 changes: 2 additions & 2 deletions assembly/release-base-fabric.xml
Expand Up @@ -39,7 +39,7 @@
<directory>bin</directory>
<outputDirectory>/bin</outputDirectory>
<includes>
<include>ggrouter.bat</include>
<include>igniterouter.bat</include>
</includes>
</fileSet>

Expand All @@ -48,7 +48,7 @@
<outputDirectory>/bin</outputDirectory>
<fileMode>0755</fileMode>
<includes>
<include>ggrouter.sh</include>
<include>igniterouter.sh</include>
</includes>
</fileSet>

Expand Down
4 changes: 2 additions & 2 deletions assembly/release-base.xml
Expand Up @@ -55,7 +55,7 @@
</includes>
<excludes>
<exclude>**/*hadoop*.bat</exclude>
<exclude>ggrouter.bat</exclude>
<exclude>igniterouter.bat</exclude>
<exclude>**/target-classpath.bat</exclude>
</excludes>
</fileSet>
Expand All @@ -69,7 +69,7 @@
</includes>
<excludes>
<exclude>**/*hadoop*.sh</exclude>
<exclude>ggrouter.sh</exclude>
<exclude>igniterouter.sh</exclude>
<exclude>**/target-classpath.sh</exclude>
<exclude>**/service.sh</exclude>
</excludes>
Expand Down
2 changes: 1 addition & 1 deletion bin/ggstart.bat → bin/ignite.bat
Expand Up @@ -91,7 +91,7 @@ if /i "%SCRIPTS_HOME%\" == "%~dp0" goto setProgName
::
:: Set program name.
::
set PROG_NAME=ggstart.bat
set PROG_NAME=ignite.bat
if "%OS%" == "Windows_NT" set PROG_NAME=%~nx0%

:run
Expand Down
0 bin/ggstart.sh → bin/ignite.sh 100755 → 100644
File renamed without changes.
2 changes: 1 addition & 1 deletion bin/ggrouter.bat → bin/igniterouter.bat
Expand Up @@ -30,4 +30,4 @@ set MAIN_CLASS=org.gridgain.client.router.impl.GridRouterCommandLineStartup
::
:: Start router service.
::
call "%~dp0\ggstart.bat" %*
call "%~dp0\ignite.bat" %*
2 changes: 1 addition & 1 deletion bin/ggrouter.sh → bin/igniterouter.sh 100755 → 100644
Expand Up @@ -47,4 +47,4 @@ export MAIN_CLASS=org.gridgain.client.router.impl.GridRouterCommandLineStartup
#
# Start router service.
#
. "${SCRIPTS_HOME}"/ggstart.sh $@
. "${SCRIPTS_HOME}"/ignite.sh $@
File renamed without changes.
File renamed without changes.
2 changes: 1 addition & 1 deletion bin/setup-hadoop.bat
Expand Up @@ -23,4 +23,4 @@ if "%OS%" == "Windows_NT" setlocal

set MAIN_CLASS=org.gridgain.grid.hadoop.GridHadoopSetup

call "%~dp0\ggstart.bat" %*
call "%~dp0\ignite.bat" %*
2 changes: 1 addition & 1 deletion bin/setup-hadoop.sh
Expand Up @@ -57,4 +57,4 @@ export MAIN_CLASS=org.gridgain.grid.hadoop.GridHadoopSetup
#
# Start utility.
#
. "${SCRIPTS_HOME}/ggstart.sh" $@
. "${SCRIPTS_HOME}/ignite.sh" $@
2 changes: 1 addition & 1 deletion config/hadoop/default-config.xml
Expand Up @@ -21,7 +21,7 @@
GridGain Spring configuration file.
When starting a standalone GridGain node, you need to execute the following command:
{IGNITE_HOME}/bin/ggstart.{bat|sh} path-to-this-file/default-config.xml
{IGNITE_HOME}/bin/ignite.{bat|sh} path-to-this-file/default-config.xml
When starting GridGain from Java IDE, pass path to this file into GridGain:
GridGain.start("path-to-this-file/default-config.xml");
Expand Down
2 changes: 1 addition & 1 deletion config/router/default-router.xml
Expand Up @@ -21,7 +21,7 @@
Default rest router configuration.
This file is automatically scanned by
$IGNITE_HOME/bin/ggrouter.sh and $IGNITE_HOME/bin/ggrouter.bat
$IGNITE_HOME/bin/igniterouter.sh and $IGNITE_HOME/bin/igniterouter.bat
for org.gridgain.client.router.GridTcpRestRouterConfiguration bean definition.
First found is used to start router instance.
Expand Down
6 changes: 3 additions & 3 deletions docs/hadoop_readme.md
Expand Up @@ -40,7 +40,7 @@ Installation requirements:
After setup script successfully completed, you can execute the Ignite startup script.
The following command will startup Ignite node with default configuration using multicast node discovery.

bin/ggstart.{sh|bat}
bin/ignite.{sh|bat}

If Ignite was installed successfully, the output from above commands should produce no exceptions or errors.
Note that you may see some other warnings during startup, but this is OK as they are meant to inform that certain
Expand All @@ -53,7 +53,7 @@ Here is an example of log printout when 2 nodes join topology:

You can also start Ignite Management Console, called Visor, and observe started nodes. To startup Visor, you should execute the following script:

/bin/ggvisorcmd.{sh|bat}
/bin/ignitevisorcmd.{sh|bat}

## 3. Configuration

Expand Down Expand Up @@ -112,6 +112,6 @@ Ignite comes with CLI (command) based DevOps Managements Console, called Visor,

To start Visor in console mode you should execute the following command:

`bin/ggvisorcmd.sh`
`bin/ignitevisorcmd.sh`

On Windows, run the same commands with `.bat` extension.
12 changes: 6 additions & 6 deletions docs/ignite_readme.md
Expand Up @@ -37,11 +37,11 @@ To verify Ignite installation, you can execute the Ignite startup script.

The following command will startup Ignite with default configuration using Multicast node discovery.

bin/ggstart.{sh|bat}
bin/ignite.{sh|bat}

The following command will startup Ignite with example configuration.

bin/ggstart.{sh|bat} examples/config/example-compute.xml
bin/ignite.{sh|bat} examples/config/example-compute.xml

If Ignite was installed successfully, the output from above commands should produce no exceptions or errors.
Note that you may see some warnings during startup, but this is OK as they are meant to inform that certain functionality is turned on or off by default.
Expand All @@ -53,7 +53,7 @@ Here is an example of log printout when 2 nodes join topology:

You can also start Ignite Management Console, called Visor, and observe started nodes. To startup Visor, you should execute the following script:

/bin/ggvisorcmd.{sh|bat}
/bin/ignitevisorcmd.{sh|bat}

### 2.2 Running Ignite Examples

Expand All @@ -78,18 +78,18 @@ You can use maven to add Ignite artifacts to your project. Ignite has one main a


## 4. Starting Ignite Nodes
Ignite nodes can be started by executing `bin/ggstart.{sh|bat}` script and passing a relative path to Ignite configuration file. If no file is passed, then grid nodes are started with default configuration using Multicast discovery protocol.
Ignite nodes can be started by executing `bin/ignite.{sh|bat}` script and passing a relative path to Ignite configuration file. If no file is passed, then grid nodes are started with default configuration using Multicast discovery protocol.

Here is an example of how to start Ignite node with non-default configuration:

`bin/ggstart.sh examples/config/example-cache.xml`
`bin/ignite.sh examples/config/example-cache.xml`

## 5. Management & Monitoring with Visor
Ignite comes with CLI (command) based DevOps Managements Console, called Visor, delivering advance set of management and monitoring capabilities.

To start Visor in console mode you should execute the following command:

`bin/ggvisorcmd.sh`
`bin/ignitevisorcmd.sh`

On Windows, run the same commands with `.bat` extension.

Expand Down
2 changes: 1 addition & 1 deletion examples/config/example-cache.xml
Expand Up @@ -21,7 +21,7 @@
GridGain Spring configuration file to startup grid cache.
When starting a standalone GridGain node, you need to execute the following command:
{IGNITE_HOME}/bin/ggstart.{bat|sh} examples/config/example-cache.xml
{IGNITE_HOME}/bin/ignite.{bat|sh} examples/config/example-cache.xml
When starting GridGain from Java IDE, pass path to this file to GridGain:
GridGain.start("examples/config/example-cache.xml");
Expand Down
2 changes: 1 addition & 1 deletion examples/config/example-streamer.xml
Expand Up @@ -21,7 +21,7 @@
GridGain Spring configuration file to startup grid with streamers.
When starting a standalone GridGain node, you need to execute the following command:
{IGNITE_HOME}/bin/ggstart.{bat|sh} examples/config/example-streamer.xml
{IGNITE_HOME}/bin/ignite.{bat|sh} examples/config/example-streamer.xml
When starting nodes this way JAR file containing the examples code
should be placed to {IGNITE_HOME}/libs folder. You can build
gridgain-examples.jar by running "mvn package" in {IGNITE_HOME}/examples folder.
Expand Down
2 changes: 1 addition & 1 deletion examples/config/filesystem/example-ggfs.xml
Expand Up @@ -21,7 +21,7 @@
GridGain Spring configuration file to startup grid cache.
When starting a standalone GridGain node, you need to execute the following command:
{IGNITE_HOME}/bin/ggstart.{bat|sh} examples/config/filesystem/example-ggfs.xml
{IGNITE_HOME}/bin/ignite.{bat|sh} examples/config/filesystem/example-ggfs.xml
When starting GridGain from Java IDE, pass path to this file into GridGain:
GridGain.start("examples/config/filesystem/example-ggfs.xml");
Expand Down
2 changes: 1 addition & 1 deletion examples/rest/http-rest-example.php
Expand Up @@ -22,7 +22,7 @@
* To execute this script simply start up an instance of GridGain with cache enabled.
* You can use any cache configuration from examples/config folder as follows:
* ----
* ${IGNITE_HOME}/bin/ggstart.sh examples/config/example-cache.xml
* ${IGNITE_HOME}/bin/ignite.sh examples/config/example-cache.xml
* ----
*
* Make sure you have correctly specified $CACHE_NAME script global variable
Expand Down
2 changes: 1 addition & 1 deletion examples/rest/memcache-rest-example.php
Expand Up @@ -27,7 +27,7 @@
* You can use default cache configuration from examples/config folder to
* start up an instance of GridGain with cache enabled as follows:
* ----
* ${IGNITE_HOME}/bin/ggstart.sh examples/config/example-cache-default.xml
* ${IGNITE_HOME}/bin/ignite.sh examples/config/example-cache-default.xml
* ----
*/

Expand Down
Expand Up @@ -28,7 +28,7 @@
* Demonstrates broadcasting computations within grid projection.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -31,7 +31,7 @@
* word.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -30,7 +30,7 @@
* nodes and then computes total amount of non-whitespaces characters in the phrase.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -40,7 +40,7 @@
* previous word has been received.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -27,7 +27,7 @@
* Simple example to demonstrate usage of grid-enabled executor service provided by GridGain.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -37,7 +37,7 @@
* {@link org.apache.ignite.compute.ComputeJobContext#callcc()} method calls in {@link FibonacciClosure} class.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -26,7 +26,7 @@
* Demonstrates new functional APIs.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -31,7 +31,7 @@
* calculated. Then total phrase length is calculated using reducer.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -28,7 +28,7 @@
* Demonstrates a simple use of {@link org.apache.ignite.lang.IgniteRunnable}.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -30,7 +30,7 @@
* three times with initial scheduling delay equal to five seconds.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -34,7 +34,7 @@
* calculated on reduce stage.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -32,7 +32,7 @@
* is calculated on reduce stage.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -27,7 +27,7 @@
* Monte-Carlo example. Demonstrates distributed credit risk calculation.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-compute.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-compute.xml'}.
* <p>
* Alternatively you can run {@link ComputeNodeStartup} in another JVM which will start GridGain node
* with {@code examples/config/example-compute.xml} configuration.
Expand Down
Expand Up @@ -30,7 +30,7 @@
* example is to provide the simplest code example of this logic.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-cache.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-cache.xml'}.
* <p>
* Alternatively you can run {@link CacheNodeStartup} in another JVM which will
* start GridGain node with {@code examples/config/example-cache.xml} configuration.
Expand Down
Expand Up @@ -28,7 +28,7 @@
* This example demonstrates some of the cache rich API capabilities.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-cache.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-cache.xml'}.
* <p>
* Alternatively you can run {@link CacheNodeStartup} in another JVM which will
* start GridGain node with {@code examples/config/example-cache.xml} configuration.
Expand Down
Expand Up @@ -28,7 +28,7 @@
* This examples demonstrates continuous query API.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-cache.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-cache.xml'}.
* <p>
* Alternatively you can run {@link CacheNodeStartup} in another JVM which will
* start GridGain node with {@code examples/config/example-cache.xml} configuration.
Expand Down
Expand Up @@ -27,7 +27,7 @@
* together and properly manages load on remote nodes.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-cache.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-cache.xml'}.
* <p>
* Alternatively you can run {@link CacheNodeStartup} in another JVM which will
* start GridGain node with {@code examples/config/example-cache.xml} configuration.
Expand Down
Expand Up @@ -31,7 +31,7 @@
* must be specifically enabled, just like in {@code examples/config/example-cache.xml} file.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-cache.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-cache.xml'}.
* <p>
* Alternatively you can run {@link CacheNodeStartup} in another JVM which will
* start GridGain node with {@code examples/config/example-cache.xml} configuration.
Expand Down
Expand Up @@ -30,7 +30,7 @@
* Real time popular numbers counter.
* <p>
* Remote nodes should always be started with special configuration file which
* enables P2P class loading: {@code 'ggstart.{sh|bat} examples/config/example-cache.xml'}.
* enables P2P class loading: {@code 'ignite.{sh|bat} examples/config/example-cache.xml'}.
* <p>
* Alternatively you can run {@link CacheNodeStartup} in another JVM which will
* start GridGain node with {@code examples/config/example-cache.xml} configuration.
Expand Down

0 comments on commit 7e8ea4f

Please sign in to comment.