You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by zh...@apache.org on 2017/07/21 06:41:59 UTC
[47/50] [abbrv] geode git commit: GEODE-3208 Revise docs with
outdated JAR references
GEODE-3208 Revise docs with outdated JAR references
This closes #644
Project: http://git-wip-us.apache.org/repos/asf/geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/119c20f9
Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/119c20f9
Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/119c20f9
Branch: refs/heads/feature/GEM-1483
Commit: 119c20f9b5148bd8c02ed3fecd26b2fff9e67f87
Parents: b71f3a6
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Jul 19 10:28:17 2017 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Jul 20 14:19:08 2017 -0700
----------------------------------------------------------------------
.../persisting_configurations.html.md.erb | 34 ++++++-------
.../running/running_the_cacheserver.html.md.erb | 2 +-
.../running/running_the_locator.html.md.erb | 17 ++-----
.../jsonformatter_pdxinstances.html.md.erb | 2 +-
.../15_minute_quickstart_gfsh.html.md.erb | 4 +-
.../jmx_manager_operations.html.md.erb | 52 +++++++-------------
.../gfsh/configuring_gfsh.html.md.erb | 4 +-
7 files changed, 45 insertions(+), 70 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/geode/blob/119c20f9/geode-docs/configuring/cluster_config/persisting_configurations.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/configuring/cluster_config/persisting_configurations.html.md.erb b/geode-docs/configuring/cluster_config/persisting_configurations.html.md.erb
index 372ea5b..4556192 100644
--- a/geode-docs/configuring/cluster_config/persisting_configurations.html.md.erb
+++ b/geode-docs/configuring/cluster_config/persisting_configurations.html.md.erb
@@ -53,7 +53,8 @@ This section provides a walk-through example of configuring a simple Apache Geod
gfsh>start locator --name=locator1
Starting a Geode Locator in /Users/username/my_geode/locator1...
.............................
- Locator in /Users/username/my_geode/locator1 on 192.0.2.0[10334] as locator1 is currently online.
+ Locator in /Users/username/my_geode/locator1 on 192.0.2.0[10334] as locator1
+ is currently online.
Process ID: 5203
Uptime: 15 seconds
Geode Version: 1.0.0
@@ -64,7 +65,6 @@ This section provides a walk-through example of configuring a simple Apache Geod
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/username/Apache_Geode_1.0.0_Linux/lib/geode-dependencies.jar
- :/Users/username/Apache_Geode_1.0.0_Linux/lib/locator-dependencies.jar
Successfully connected to: [host=192.0.2.0, port=1099]
@@ -79,7 +79,8 @@ This section provides a walk-through example of configuring a simple Apache Geod
gfsh>start server --name=server1 --group=group1
Starting a Geode Server in /Users/username/my_geode/server1...
.....
- Server in /Users/username/my_geode/server1 on 192.0.2.0[40404] as server1 is currently online.
+ Server in /Users/username/my_geode/server1 on 192.0.2.0[40404] as server1
+ is currently online.
Process ID: 5627
Uptime: 2 seconds
Geode Version: 1.0.0
@@ -90,12 +91,12 @@ This section provides a walk-through example of configuring a simple Apache Geod
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/username/Apache_Geode_1.0.0_Linux/lib/geode-dependencies.jar
- :/Users/username/Apache_Geode_1.0.0_Linux/lib/server-dependencies.jar
gfsh>start server --name=server2 --group=group1 --server-port=40405
Starting a Geode Server in /Users/username/my_geode/server2...
.....
- Server in /Users/username/my_geode/server2 on 192.0.2.0[40405] as server2 is currently online.
+ Server in /Users/username/my_geode/server2 on 192.0.2.0[40405] as server2
+ is currently online.
Process ID: 5634
Uptime: 2 seconds
Geode Version: 1.0.0
@@ -106,12 +107,12 @@ This section provides a walk-through example of configuring a simple Apache Geod
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/username/Apache_Geode_1.0.0_Linux/lib/geode-dependencies.jar
- :/Users/username/Apache_Geode_1.0.0_Linux/lib/server-dependencies.jar
gfsh>start server --name=server3 --server-port=40406
Starting a Geode Server in /Users/username/my_geode/server3...
.....
- Server in /Users/username/my_geode/server3 on 192.0.2.0[40406] as server3 is currently online.
+ Server in /Users/username/my_geode/server3 on 192.0.2.0[40406] as server3
+ is currently online.
Process ID: 5637
Uptime: 2 seconds
Geode Version: 1.0.0
@@ -122,7 +123,6 @@ This section provides a walk-through example of configuring a simple Apache Geod
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/username/Apache_Geode_1.0.0_Linux/lib/geode-dependencies.jar
- :/Users/username/Apache_Geode_1.0.0_Linux/lib/server-dependencies.jar
```
Note that the `gfsh` commands you used to start `server1` and `server2` specify a group named `group1` while the command for `server3` did not specify a group name.
@@ -171,13 +171,13 @@ This section provides a walk-through example of configuring a simple Apache Geod
You can use the `gfsh export cluster-configuration` command to create a zip file that contains the cluster's persisted configuration. The zip file contains a copy of the contents of the `cluster_config` directory. For example:
``` pre
- gfsh>export cluster-configuration --zip-file-name=myClusterConfig.zip --dir=/Users/username
+ gfsh>export cluster-configuration --zip-file-name=myClConfig.zip --dir=/Users/username
```
Apache Geode writes the cluster configuration to the specified zip file.
``` pre
- Downloading cluster configuration : /Users/username/myClusterConfig.zip
+ Downloading cluster configuration : /Users/username/myClConfig.zip
```
The remaining steps demonstrate how to use the cluster configuration you just created.
@@ -215,7 +215,8 @@ This section provides a walk-through example of configuring a simple Apache Geod
gfsh>start locator --name=locator2 --port=10335
Starting a Geode Locator in /Users/username/new_geode/locator2...
.............................
- Locator in /Users/username/new_geode/locator2 on 192.0.2.0[10335] as locator2 is currently online.
+ Locator in /Users/username/new_geode/locator2 on 192.0.2.0[10335] as locator2
+ is currently online.
Process ID: 5749
Uptime: 15 seconds
Geode Version: 1.0.0
@@ -226,7 +227,6 @@ This section provides a walk-through example of configuring a simple Apache Geod
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/username/Apache_Geode_1.0.0_Linux/lib/geode-dependencies.jar
- :/Users/username/Apache_Geode_1.0.0_Linux/lib/locator-dependencies.jar
Successfully connected to: [host=192.0.2.0, port=1099]
@@ -236,7 +236,7 @@ This section provides a walk-through example of configuring a simple Apache Geod
13. Import the cluster configuration using the `import cluster-configuration` command. For example:
``` pre
- gfsh>import cluster-configuration --zip-file-name=/Users/username/myClusterConfig.zip
+ gfsh>import cluster-configuration --zip-file-name=/Users/username/myClConfig.zip
Cluster configuration successfully imported
```
@@ -248,7 +248,8 @@ This section provides a walk-through example of configuring a simple Apache Geod
gfsh>start server --name=server4 --server-port=40414
Starting a Geode Server in /Users/username/new_geode/server4...
........
- Server in /Users/username/new_geode/server4 on 192.0.2.0[40414] as server4 is currently online.
+ Server in /Users/username/new_geode/server4 on 192.0.2.0[40414] as server4
+ is currently online.
Process ID: 5813
Uptime: 4 seconds
Geode Version: 1.0.0
@@ -259,7 +260,6 @@ This section provides a walk-through example of configuring a simple Apache Geod
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/username/Apache_Geode_1.0.0_Linux/lib/geode-dependencies.jar
- :/Users/username/Apache_Geode_1.0.0_Linux/lib/server-dependencies.jar
```
15. Start another server that references `group1`:
@@ -268,7 +268,8 @@ This section provides a walk-through example of configuring a simple Apache Geod
gfsh>start server --name=server5 --group=group1 --server-port=40415
Starting a Geode Server in /Users/username/new_geode/server5...
.....
- Server in /Users/username/new_geode/server2 on 192.0.2.0[40415] as server5 is currently online.
+ Server in /Users/username/new_geode/server2 on 192.0.2.0[40415] as server5
+ is currently online.
Process ID: 5954
Uptime: 2 seconds
Geode Version: 1.0.0
@@ -279,7 +280,6 @@ This section provides a walk-through example of configuring a simple Apache Geod
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/username/Apache_Geode_1.0.0_Linux/lib/geode-dependencies.jar
- :/Users/username/Apache_Geode_1.0.0_Linux/lib/server-dependencies.jar
```
16. Use the `list regions` command to display the configured regions. Note that region1 and region2, which were configured in the original cluster level are available.
http://git-wip-us.apache.org/repos/asf/geode/blob/119c20f9/geode-docs/configuring/running/running_the_cacheserver.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/configuring/running/running_the_cacheserver.html.md.erb b/geode-docs/configuring/running/running_the_cacheserver.html.md.erb
index 837cf7d..2d43f59 100644
--- a/geode-docs/configuring/running/running_the_cacheserver.html.md.erb
+++ b/geode-docs/configuring/running/running_the_cacheserver.html.md.erb
@@ -31,7 +31,7 @@ The Geode server is used primarily for hosting long-lived data regions and for r
The `gfsh` utility uses a working directory for its configuration files and log files. These are the defaults and configuration options:
-- When you start a standalone server using `gfsh`, `gfsh` will automatically load the required JAR file `$GEMFIRE/lib/server-dependencies.jar` into the CLASSPATH of the JVM process. If you start a standalone server using the ServerLauncher API, you must specify `$GEMFIRE/lib/server-dependencies.jar` inside your command to launch the process. For more information on CLASSPATH settings in Geode, see [Setting Up the CLASSPATH](../../getting_started/setup_classpath.html).
+- When you start a standalone server using `gfsh`, `gfsh` will automatically load the required JAR file `lib/geode-dependencies.jar` into the CLASSPATH of the JVM process. If you start a standalone server using the ServerLauncher API, you must specify this JAR file inside your command to launch the process. For more information on CLASSPATH settings in Geode, see [Setting Up the CLASSPATH](../../getting_started/setup_classpath.html).
- Servers are configured like any other Geode process, with `gemfire.properties` and shared cluster configuration files. It is not programmable except through application plug-ins. Typically, you provide the `gemfire.properties` file and the `gfsecurity.properties` file (if you are using a separate, restricted access security settings file). You can also specify a `cache.xml` file in the cache server’s working directory.
- By default, a new server started with `gfsh` receives its initial cache configuration from the cluster configuration service, assuming the locator is running the cluster configuration service. If you specify a group when starting the server, the server also receives configurations that apply to a group. The shared configuration consists of `cache.xml` files, `gemfire.properties` files, and deployed jar files. You can disable use of the cluster configuration service by specifying `--use-cluster-configuration=false` when starting the server using `gfsh`.
http://git-wip-us.apache.org/repos/asf/geode/blob/119c20f9/geode-docs/configuring/running/running_the_locator.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/configuring/running/running_the_locator.html.md.erb b/geode-docs/configuring/running/running_the_locator.html.md.erb
index 7d29646..6e3a49f 100644
--- a/geode-docs/configuring/running/running_the_locator.html.md.erb
+++ b/geode-docs/configuring/running/running_the_locator.html.md.erb
@@ -35,7 +35,7 @@ You can run the locator standalone or embedded within another Geode process. Run
Locator configuration and log files have the following properties:
-- When you start a standalone locator using `gfsh`, `gfsh` will automatically load the required JAR file (`$GEMFIRE/lib/locator-dependencies.jar`) into the CLASSPATH of the JVM process. If you start a standalone locator using the `LocatorLauncher` API, you must specify `$GEMFIRE/lib/locator-dependencies.jar` inside the command used to launch the locator process. For more information on CLASSPATH settings in Geode, see [CLASSPATH Settings for Geode Processes](../../getting_started/setup_classpath.html). You can modify the CLASSPATH by specifying the `--classpath` parameter.
+- When you start a standalone locator using `gfsh`, `gfsh` will automatically load the required JAR file `lib/geode-dependencies.jar` into the CLASSPATH of the JVM process. If you start a standalone locator using the `LocatorLauncher` API, you must specify this JAR file inside the command used to launch the locator process. For more information on CLASSPATH settings in Geode, see [CLASSPATH Settings for Geode Processes](../../getting_started/setup_classpath.html). You can modify the CLASSPATH by specifying the `--classpath` parameter.
- Locators are members of the distributed system just like any other member. In terms of `mcast-port` and `locators` configuration, a locator should be configured in the same manner as a server. Therefore, if there are two other locators in the distributed system, each locator should reference the other locators (just like a server member would). For example:
``` pre
@@ -76,16 +76,7 @@ Use the following guidelines to start the locator:
gfsh> start locator --name=locator2 --bind-address=192.0.2.0 --port=13489
```
- - Start the locator using the `main` method in the `org.apache.geode.distributed.LocatorLauncher` class and the Java executable. For example:
-
- ``` pre
- working/directory/of/Locator/process$java -server \
- -classpath "$GEMFIRE/lib/locator-dependencies.jar:/path/to/application/classes.jar" \
- org.apache.geode.distributed.LocatorLauncher start Locator1 --port=11235 \
- --redirect-output
- ```
-
- Specifically, you use the `LocatorLauncher` class API to run an embedded Locator service in Java application processes that you have created. The directory where you execute the java command becomes the working directory for the locator process.
+ - Start the locator using the `main` method in the `org.apache.geode.distributed.LocatorLauncher` class and the Java executable. Specifically, you use the `LocatorLauncher` class API to run an embedded Locator service in Java application processes that you have created. The directory where you execute the java command becomes the working directory for the locator process.
- When starting up multiple locators, do not start them up in parallel (in other words, simultaneously). As a best practice, you should wait approximately 30 seconds for the first locator to complete startup before starting any other locators. To check the successful startup of a locator, check for locator log files. To view the uptime of a running locator, you can use the `gfsh status locator` command.
@@ -172,7 +163,7 @@ Use the following guidelines to start the locator:
``` pre
/working/directory/of/MyApplication$ java \
- -server -classpath "$GEMFIRE/lib/locator-dependencies.jar:/path/to/application/classes.jar" \
+ -server -classpath "path/to/installation/lib/geode-dependencies.jar:/path/to/application/classes.jar" \
example.MyApplication Locator1 11235
```
@@ -218,7 +209,7 @@ Java Version: 1.7.0_65
Log File: /home/user/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
-Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar
+Class-Path: /Users/username/apache_geode/lib/geode-dependencies.jar
Cluster configuration service is up and running.
```
http://git-wip-us.apache.org/repos/asf/geode/blob/119c20f9/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb b/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
index b2abfb6..09aaae2 100644
--- a/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
+++ b/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
@@ -27,7 +27,7 @@ In terms of querying and indexing, because the documents are stored internally a
You can then use the `JSONFormatter` to convert the PdxInstance results back into the JSON document.
-`JSONFormatter` uses a streaming parser ([Jackson](http://wiki.fasterxml.com/JacksonHome), JSON processor) to turn JSON documents into the optimized PDX format. To use the JSONFormatter, make sure that `$GEMFIRE/lib/server-dependencies.jar` is available in your application's CLASSPATH.
+`JSONFormatter` uses a streaming parser ([Jackson](http://wiki.fasterxml.com/JacksonHome), JSON processor) to turn JSON documents into the optimized PDX format. To use the JSONFormatter, make sure that `lib/geode-dependencies.jar` is available in your application's CLASSPATH.
The `JSONFormatter` class has four static methods that are used to convert JSON document into PdxInstances and then to convert those PdxInstances back into JSON document.
http://git-wip-us.apache.org/repos/asf/geode/blob/119c20f9/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
index 954dcf8..a4970d8 100644
--- a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
+++ b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
@@ -420,8 +420,8 @@ In this step you restart the cache servers in parallel. Because the data is pers
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334] -Dgemfire.use-cluster-configuration=true
-XX:OnOutOfMemoryError=kill -KILL %p -Dgemfire.launcher.registerSignalHandlers=true
-Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
- Class-Path: /home/username/Apache_Geode_Linux/lib/gemfire.jar:
- /home/username/Apache_Geode_Linux/lib/server-dependencies.jar
+ Class-Path: /home/username/Apache_Geode_Linux/lib/geode-core-1.0.0.jar:
+ /home/username/Apache_Geode_Linux/lib/geode-dependencies.jar
```
5. Verify that the locator and two servers are running:
http://git-wip-us.apache.org/repos/asf/geode/blob/119c20f9/geode-docs/managing/management/jmx_manager_operations.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/managing/management/jmx_manager_operations.html.md.erb b/geode-docs/managing/management/jmx_manager_operations.html.md.erb
index aac909c..e48209c 100644
--- a/geode-docs/managing/management/jmx_manager_operations.html.md.erb
+++ b/geode-docs/managing/management/jmx_manager_operations.html.md.erb
@@ -50,39 +50,23 @@ The following is an example of starting a new locator that also starts an embedd
``` pre
gfsh>start locator --name=locator1
-Starting a GemFire Locator in /home/user/test2/locator1...
-............................................
-Locator in /home/user/test2/locator1 on ubuntu.local[10334] as locator1 is currently online.
-Process ID: 2081
-Uptime: 30 seconds
-GemFire Version: 8.0.0
-Java Version: 1.7.0_65
-Log File: /home/user/test2/locator1/locator1.log
-JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false
--Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
-Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar
-
-Successfully connected to: [host=ubuntu.local, port=1099]
-
-Cluster configuration service is up and running.
-```
-
-Or you can enter the command directly in your terminal:
-
-``` pre
-$ gfsh start locator --name=locator1
-....................................
-Locator in /home/user/locator1 on ubuntu.local[10334] as locator1 is currently online.
-Process ID: 2359
-Uptime: 21 seconds
-GemFire Version: 8.0.0
-Java Version: 1.7.0_65
-Log File: /home/user/locator1/locator1.log
-JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false
- -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
-Class-Path: /home/user/Pivotal_GemFire_800_b48319_Linux/lib/locator-dependencies.jar
-
-Successfully connected to: [host=ubuntu.local, port=1099]
+Starting a Geode Locator in /Users/username/apache-geode/locator1...
+....
+Locator in /Users/username/apache-geode/locator1 on 192.0.2.0[10334] as locator1
+is currently online.
+Process ID: 27144
+Uptime: 5 seconds
+Geode Version: 1.2.0
+Java Version: 1.8.0_111
+Log File: /Users/username/apache-geode/locator1/locator1.log
+JVM Arguments: -Dgemfire.enable-cluster-configuration=true
+-Dgemfire.load-cluster-configuration-from-dir=false
+-Dgemfire.launcher.registerSignalHandlers=true
+-Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
+Class-Path: /Users/username/apache-geode/lib/geode-core-1.2.0.jar
+:/Users/username/apache-geode/lib/geode-dependencies.jar
+
+Successfully connected to: JMX Manager [host=192.0.2.0, port=1099]
Cluster configuration service is up and running.
```
@@ -96,7 +80,7 @@ At any point, you can determine whether a node is a JMX Manager by using the Mem
Using the Java API, any managed node that has been configured with `jmx-manager=true` can also be turned into a JMX Manager Node by invoking the ManagementService startManager() method.
**Note:**
-If you start the JMX Manager programmatically and wish to enable command processing, you must also add the absolute path of `gfsh-dependencies.jar` (located in `$GEMFIRE/lib` of your Geode installation) to the CLASSPATH of your application. Do not copy this library to your CLASSPATH because this library refers to other dependencies in `$GEMFIRE/lib` by a relative path.
+If you start the JMX Manager programmatically and wish to enable command processing, you must also add the absolute path of `gfsh-dependencies.jar` (located in the `lib` directory of your installation) to the CLASSPATH of your application. Do not copy this library to your CLASSPATH, because this library refers to other dependencies in `lib` by a relative path.
## <a id="topic_263072624B8D4CDBAD18B82E07AA44B6" class="no-quick-link"></a>Configuring a JMX Manager
http://git-wip-us.apache.org/repos/asf/geode/blob/119c20f9/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb b/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb
index e48cfda..94125a7 100644
--- a/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb
@@ -24,9 +24,9 @@ The `gfsh.bat` and `gfsh` bash script automatically append the required Apache G
## <a id="concept_3B9C6CE2F64841E98C33D9F6441DF487__section_0D2EEA7A9ED54DFDB2E1EE955E47921E" class="no-quick-link"></a>JAR Libraries in CLASSPATH
-When you start up `gfsh`, it will automatically load required JAR files that have been packaged in the `gfsh-dependencies.jar` file. You do not need to modify your CLASSPATH to run gfsh. When starting servers and locators in gfsh, the start server and start locator commands will load `server-dependencies.jar` and `locator-dependencies.jar` files into the process CLASSPATH for you.
+When you start up `gfsh`, it will automatically load required JAR files that have been packaged in the `gfsh-dependencies.jar` file. You do not need to modify your CLASSPATH to run `gfsh`.
-These dependency JAR files are packaged in your Apache Geode installation in the `$GEMFIRE/lib` (or on Windows, the `%GEODE_HOME%\lib`) directory.
+The JAR files are packaged within your installation directory in the `lib` directory.
## <a id="concept_3B9C6CE2F64841E98C33D9F6441DF487__section_02EEF9A519094EAD9D6B5C8E896EBA27" class="no-quick-link"></a>Machine Hostname