Administration guide > Configure the deployment environment

Configure clients

You can configure WXS to run in a stand-alone environment, or you can configure eXtreme Scale to run in an environment with WAS.

For a WXS deployment to pick up configuration changes on the server grid side, restart processes to make these changes take effect rather than being applied dynamically. However, on the client side, although you cannot alter the configuration settings for an existing client instance, you can create a new client instance with the settings you require by using an XML file or doing so programmatically. When creating a client, you can override the default settings that come from the current server configuration.

You can configure an eXtreme Scale client in the following ways, each of which can be done with a client override XML file or programmatically:

• XML configuration
• Programmatic configuration
• Spring Framework configuration
• Disable the near cache

You can override the following plug-ins on a client:

• ObjectGrid plug-ins
  • TransactionCallback plug-in
  • ObjectGridEventListener plug-in

• BackMap plug-ins
  • Evictor plug-in
  • MapEventListener plug-in
  • numberOfBuckets attribute
  • ttlEvictorType attribute
  • timeToLive attribute

See also

1. Client properties file

   You can create a properties file based on the requirements for WXS client processes.

2. Configure clients with WXS

   You can configure a WXS client based on the requirements such as the need to override settings.

3. Enable the client invalidation mechanism

   In a distributed WXS environment, the client side has a near cache by default when using the optimistic locking strategy or when locking is disabled. The near cache has its own local cached data. If an eXtreme Scale client commits an update, the update goes to the client near cache and server. However, other eXtreme Scale clients do not receive the update information and might have data that is out of date.

4. Configure request retry timeout values

   With reliable maps, you can supply a retry timeout value in milliseconds to WXS for transaction requests.

Parent topic:

Configure the deployment environment

Related concepts

Configure cache integration
Clients
Configure clients

Related tasks

Configure data grids
Configure deployment policies
Configure catalog and container servers
Configure ports
Configure Object Request Brokers
Configure entities
Configure Spring integration
Configure the REST data service

+

Search Tips   |   Advanced Search