You can use data
caching products with the WebSphere® Application Server Liberty profile to develop HTTP
sessions, client-server connections through the REST gateway, and
manage other cache integration scenarios.
In WebSphere eXtreme Scale, you can use the Liberty profile to connect to the data grid. For example, when you install WebSphere eXtreme Scale with the Liberty profile, you have access to features that you can use to manage HTTP session applications, Java client applications, and REST client applications that are installed in the Liberty profile.
The following features contain information about the main available features. Including a feature in the configuration might cause one or more features to be loaded automatically. Each feature includes a brief description and an example of how the feature is declared
The server feature contains the capability for running an eXtreme Scale server, both catalog and container. Add the server feature when you want to run a catalog server in the Liberty profile or when you want to deploy a grid application into the Liberty profile.
<server description="WebSphere eXtreme Scale Server">
<featureManager>
<feature>eXtremeScale.server-1.1</feature>
</featureManager>
<xsServer/>
</server>
The client feature contains most of the programming model for eXtreme Scale. Add the client feature when you have an application that is running in the Liberty profile that is going to use eXtreme Scale APIs.
<server description="WebSphere eXtreme Scale Client">
<featureManager>
<feature>eXtremeScale.client-1.1</feature>
</featureManager>
</server>
The web
feature is deprecated. Use the webapp feature when you want to replicate
HTTP session data for fault tolerance.
The web feature contains the capability to extend the Liberty profile web application. Add the web feature when you want to replicate HTTP session data for fault tolerance.
<server description="WebSphere eXtreme Scale enabled Web Server">
<featureManager>
<feature>eXtremeScale.web-1.1</feature>
</featureManager>
<xsWebAppV85/>
</server>
The webApp feature contains the capability to extend the Liberty profile web application. Add the webApp feature when you want to replicate HTTP session data for fault tolerance.
<server description="WebSphere eXtreme Scale enabled Web Server">
<featureManager>
<feature>eXtremeScale.webApp-1.1</feature>
</featureManager>
<xsWebApp/>
</server>
A Liberty profile server can host a data grid that caches data for applications to replicate HTTP session data for fault tolerance.
<server description="WebSphere eXtreme Scale enabled Web Server">
<featureManager>
<feature>eXtremeScale.webGrid-1.1</feature>
</featureManager>
<xsWebGrid/>
</server>
Use the Representational State Transfer (REST) gateway to access simple data grids that are hosted by a collective in the Liberty profile.
<server description="WebSphere eXtreme Scale enabled Web Server">
<featureManager>
<feature>eXtremeScale.rest-1.1</feature>
</featureManager>
<xsRest/>
</server>
A Liberty profile server can host a data grid that caches data for applications that have dynamic cache enabled.
<server description="WebSphere eXtreme Scale enabled Web Server">
<featureManager>
<feature>eXtremeScale.dynacacheGrid-1.1</feature>
</featureManager>
<xsDynacacheGrid/>
</server>
The Liberty profile server can host WebSphere eXtreme Scale, which you can configure as a dynamic cache provider with this feature.
See the following example for using the default cache provider in the Liberty profile:
<server description="WebSphere eXtreme Scale enabled Web Server">
<featureManager>
<feature>eXtremeScale.dynacacheapp-1.1</feature>
</featureManager>
<xsClientDomain default="production">
<endpointConfig> production;localhost:2809 </endpointConfig>
</xsClientDomain>
<distributedMap id="baseCache" libraryRef="idgenerator" cacheProviderName="WebSphere eXtreme Scale">
<xsDynacacheApp remoteDomain="production" />
</distributedMap>
<distributedMap id="cache01" jndiName="cache01" memorySizeInEntries="2000" createCacheAtServerStartup="true" cacheProviderName="WebSphere eXtreme Scale">
<xsDynacacheApp remoteDomain="production" />
</distributedMap>
</server>