Deploying and Running Pivotal GemFire describes how to deploy your production
system, and manage startup and shutdown.
Deploying Pivotal GemFire Configuration Files
You can deploy your Pivotal GemFire configuration files in your system directory structure or in jar files. You determine how you want to deploy your configuration files and set them up accordingly.
Managing Pivotal GemFire System Output Files
GemFire output files are optional and can become quite large. Work with your system administrator to determine where to place them to avoid interfering with other system activities.
Using the GemFire SHell (gfsh)
Pivotal GemFire gfsh (pronounced "gee-fish") provides a single, powerful command-line interface from which you can launch, manage, and monitor Pivotal GemFire processes, data, and applications.
Pivotal GemFire Locator Process
The locator is a Pivotal GemFire process that tells new, connecting members where running members are located and provides load balancing for server use.
Pivotal GemFire Servers
A GemFire server is a Pivotal GemFire process that runs as a long-lived, configurable member of a distributed system.
Using Member Groups
Pivotal GemFire allows you to organize your distributed system members into logical member groups.
Deploying Application JARs to Pivotal GemFire Members
You can dynamically deploy your application JAR files to specific members or to all members in your distributed system. GemFire automatically keeps track of JAR file versions; autoloads the deployed JAR files to the CLASSPATH; and auto-registers any functions that the JAR contains.
You can configure and limit port usage for situations that involve firewalls, for example, between client -server or server-server connections.