WebSphere eXtreme Scale Administration Guide >

Configure WebSphere eXtreme Scale

You can configure WebSphere eXtreme Scale to run in a stand-alone environment, or you can configure eXtreme Scale to run in an environment with WebSphere Application Server or WAS ND. For an eXtreme Scale 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 may not alter the configuration settings for an existing client instance, you can create a new client 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.

• Configure a local eXtreme Scale configuration
  A local in-memory eXtreme Scale configuration can be created by using an ObjectGrid descriptor XML file or eXtreme Scale APIs.

• Map entry locking
  An ObjectGrid BackingMap supports several locking strategies for maps to maintain cache entry consistency.

• Distributed eXtreme Scale grid configuration
  Use the deployment policy descriptor XML file and the objectgrid descriptor XML file to manage the topology.

• WebSphere eXtreme Scale client configuration
  You can configure an eXtreme Scale client based on the requirements such as the need to override settings.

• Troubleshoot XML configuration
  Occasionally, when you configure eXtreme Scale, you can encounter unexpected behavior in XML configuration.

• Loaders
  With an eXtreme Scale Loader plug-in, an eXtreme Scale map can behave as a memory cache for data that is typically kept in a persistent store on either the same system or another system. Typically, a database or file system is used as the persistent store. A remote Java™ virtual machine (JVM) can also be used as the source of data, allowing hub-based caches to be built using eXtreme Scale. A loader has the logic for reading and writing data to and from a persistent store.

• Cache integration
  WebSphere eXtreme Scale can integrate with other caching-related products. JPA can be used between WebSphere eXtreme Scale and the database to integrate changes as a loader. You can also use the WebSphere eXtreme Scale dynamic cache provider to plug WebSphere eXtreme Scale into the dynamic cache component in WebSphere Application Server. Another extension to WebSphere Application Server is the WebSphere eXtreme Scale HTTP session manager, which can help to cache HTTP sessions.

• Configure evictors
  Evictors can be configured using the ObjectGrid descriptor XML file or programmatically.

• Configure the HashIndex
  The HashIndex plug-in supports both the MapIndex and MapRangeIndex interfaces. Defining and using indexes properly can significantly improve query performance.

• Configure peer-to-peer replication with JMS
  The Java Message Service (JMS) based peer-to-peer replication mechanism is used in both the distributed and local WebSphere eXtreme Scale environment. JMS is a core-to-core replication process and allows data updates to flow among local ObjectGrids and distributed ObjectGrids. For example, with this mechanism you can move data updates from a distributed eXtreme Scale grid to a local eXtreme Scale grid, or from a grid to another grid in a different system domain.

• Configure with XML files
  WebSphere eXtreme Scale is configured by a collection of XML files.

• Properties file reference
  Server properties files contain settings for running the catalog servers and container servers. You can specify a server properties file for either a stand-alone or WebSphere Application Server configuration. Client property files contain settings for the client.

• Integrate with Spring framework
  Spring is a popular framework for developing Java applications. WebSphere eXtreme Scale provides support to allow Spring to manage eXtreme Scale transactions and configure the clients and servers comprising the deployed in-memory data grid.

• Use WebSphere Real Time
  Using WebSphere eXtreme Scale with WebSphere Real Time increases consistency and predictability at a cost of performance throughput in comparison to the default garbage collection policy employed in the standard IBM Java™ SE Runtime Environment (JRE). The cost versus benefit proposition can vary. WebSphere eXtreme Scale creates many temporary objects that are associated with each transaction. These temporary objects deal with requests, responses, log sequences, and sessions. Without WebSphere Real Time, transaction response time can go up to hundreds of milliseconds. However, using WebSphere Real Time with WebSphere eXtreme Scale can increase the efficiency of garbage collection and reduce response time to 10% of the stand-alone configuration response time.

Related tasks

Configure a local eXtreme Scale configuration

+

Search Tips   |   Advanced Search