LATEST VERSION: 9.2.0 - CHANGELOG
Pivotal GemFire® v9.2

Changing the Default GemFire Configuration in the tc Server Module

By default, the tc Server HTTP module will run GemFire automatically with pre-configured settings. You can change these GemFire settings.

Here are the default GemFire settings:

  • GemFire peer-to-peer members use locators for discovery.
  • The region name is set to gemfire_modules_sessions.
  • The cache region is replicated for peer-to-peer configurations and partitioned (with redundancy turned on) for client/server configurations.
  • GemFire clients have local caching turned on and when the local cache needs to evict data, it will evict least-recently-used (LRU) data first.

Note: On the application server side, the default inactive interval for session expiration is set to 30 minutes. To change this value, refer to Session Expiration.

To change this default configuration, use the --interactive command line argument when creating the tc Server instance. Choose the appropriate command for the chosen topology and platform.

In Unix, for a peer-to-peer topology:
  $ ./tcruntime-instance.sh create my_instance_name --template gemfire-p2p \
        --interactive

In Unix, for a client/server topology:
  $ ./tcruntime-instance.sh create my_instance_name --template gemfire-cs \
         --interactive

In Windows, for a peer-to-peer topology:
  $ tcruntime-instance.bat create my_instance_name --template gemfire-p2p ^ 
         --interactive

In Windows, for a client/server topology:
  $ tcruntime-instance.bat create my_instance_name --template gemfire-cs ^ 
         --interactive

In interactive mode, you will be prompted to specify a series of property values. Hit <return> for any property that should use the default value.

After responding to approximately 20 prompts, you should see the following line:

Instance created.

Note: You cannot override region attributes on the cache server when using the HTTP Session Management Module. You must place all region attribute definitions in the region attributes template that you customize in tc Server. See Overriding Region Attributes for more information.

For information on setting up your instance for the most common types of configurations, refer to the sections below. For more information about each interactive prompt, refer to Interactive Mode Reference.

Using a Different Locator Port

For a GemFire peer-to-peer member to communicate on a different port than the default (10334), answer the following question in the tc Server HTTP module’s interactive mode:

Please enter the list of locators used by GemFire members to discover each other. 
The format is a comma-separated list of host[port]. Default 'localhost[10334]': localhost[10335]

This example changes the locator port to 10335 on localhost.

Overriding Region Attributes

When using the HTTP Session Management Module, you cannot override region attributes directly on the cache server. You must place all region attribute definitions in the region attributes template that you customize within tc Server. For example, to specify a different name for the region’s disk store, you could add the new disk-store-name specification to the region attributes template and then reference the template on the cache server.

<region-attributes id="MY_SESSIONS" refid="PARTITION_REDUNDANT_PERSISTENT_OVERFLOW" 
disk-store-name="mystore">
  ...
</region-attributes>

Then on the cache server side, reference the modified region attributes template to allow the region to use the disk-store-name attribute:

<region name="gemfire_modules_sessions" refid="MY_SESSIONS"/>