You can create three different types of data grids: simple data grids, session data grids, and dynamic cache data grids.
Creating simple data grids
With a simple data grid,
you can perform create, retrieve, update and delete operations. In
particular, you can use the simple data grid to allow faster access
to data that is stored in a database.
Creating session data grids
You can create data grids to store HTTP sessions from your
Java or .NET applications.
Creating dynamic cache data grids
You can use IBM® WebSphere® DataPower® XC10 Appliance to
store data for a WebSphere Application
Server dynamic
cache instance. By setting up this capability, you can enable applications
that are written to use a WebSphere Application
Server dynamic
cache instance to take advantage of the features and performance capabilities
of the appliance.
Configuring the maximum capacity of a data grid
You can define a maximum capacity for each data grid in
a collective. Configuring a maximum capacity limits the amount of
data storage that a particular data grid can use. The capacity limit
ensures that the available storage capacity for the collective is
used in a predictable manner.
Enabling security for data grids
After you create your data grids, the security of the data grid is disabled by default.
You can change the security settings for a data grid to restrict access to
a certain user or group of users.
Clearing data grids
You can permanently delete all of the entries in a data
grid. You can clear the data grid to remove stale information or test
entries.
Removing data grids
If you want to clear the data grid data, you can remove
the data grid and then re-create
the data grid.
Configuring a Spring cache provider
Spring Framework Version 3.1 introduced
a new cache abstraction. With this new abstraction, you can transparently
add caching to an existing Spring application. You can use WebSphere DataPower XC10 Appliance as the cache provider
for the cache abstraction.
Configuring the management concentrator
You can receive notifications by listening to all of the servers directly or through the
management concentrator, which is hosted on one or more catalog servers.