New and deprecated features in this release

Product overview > WebSphere eXtreme Scale overview

New and deprecated features in this release

WebSphere eXtreme Scale includes many new features in v7.1, including integration with the dynamic cache, byte array maps, and more.

What is new in WebSphere eXtreme Scale v7.1

Table 1. New features in WebSphere eXtreme Scale v7.1
Feature Description
DB2 client information integration Integrate eXtreme Scale JPA Loader plug-ins with DB2, so when DB2 is used as the backend database, the WebSphere eXtreme Scale information (username, workstation name, application name, and accounting information) can be made available in the DB2 Performance Monitor. This feature allows enabling and disabling configuration of client info to DB2. This function is disabled by default. For more information, see Monitor eXtreme Scale information in DB2 for more information.
Catalog service domain configuration Catalog service domains can be configured using the WAS administrative console or using administrative tasks. Catalog service domains define a group. For more information, see Create catalog service domains.
Multi-master replication Multiple data centers can be linked together asynchronously, allowing data center to access data locally and maintain high availability. See Multi-master data grid replication topologies (AP) for more information.
Last update time TTL evictor The TTL evictor has been updated to track the time in which an entry was updated, expanding on the time-to-live evictor. For more information, see TimeToLive (TTL) evictor
usedBytes statistics for in-memory grids The amount of memory that is used by cache entries in a BackingMap can be tracked using all of the statistics providers. For more information, see Cache memory consumption sizing.
Dynamic statistics Statistics can now be enabled and disabled on demand. For more information, see Monitor with managed beans (MBeans).
Monitor console The graphical monitoring console provides current and historical views into WebSphere eXtreme Scale server statistics. For more information, see Monitor with the web console.
Improved HTTP Session Manager Configuration of the HTTP session manager has been simplified. You can now configure the HTTP session manager in the WAS administrative console. For more information, see Create session persistence to a data grid.
Multi-homed client support Clients can be configured to use a specific network adapter. For more information, see Client properties file.
ISA Lite IBM Support Assistant Lite for WebSphere eXtreme Scale provides automatic data collection and symptom analysis support for problem determination scenarios. For more information, see IBM support assistant for WebSphere eXtreme Scale.
REST The REST data service provides non-Java clients access to eXtreme Scale data, supporting the Open Data Protocol (OData), providing full compatibility with Microsoft WCF Data Services. For more information, see REST data services overview.
Client-only installation WebSphere eXtreme Scale clients can now be installed independently, decreasing the installation footprint for WebSphere eXtreme Scale applications. For more information, see Install WebSphere eXtreme Scale.

Deprecated features

Table 2. Deprecated features
Deprecation Recommended migration action

catalog.services.cluster cell and server property: This custom property was used to define a group of catalog servers in the WAS configuration.

This custom property is deprecated starting in the v7.1 release.
Create a catalog service domain in the WAS administrative console, which creates the same configuration as using the custom property. See Create catalog service domains for more information.

CoreGroupServicesMBean MBean and interface

This MBean is deprecated starting in the v7.1 release.
Use the CatalogServiceManagementMBean instead.

ServerMBean.updateTraceSpec() MBean operation

This operation is deprecated starting in the v7.1 release.
Use the TraceSpec attribute on the DynamicServerMBean instead.

CoreGroupServicesMBean MBean

This MBean is deprecated starting in the v7.1 release.
Use the CatalogServiceManagementMbean MBean instead.

ServiceUnavailableException exception

This exception is deprecated starting in the v7.1 release.
Use the TargetNotAvailableException exception instead.

Partitioning facility (WPF): The partitioning facility is a set of programming APIs that allow Java EE applications to support asymmetric clustering.

The capabilities of WPF can be alternatively realized in WebSphere eXtreme Scale.

StreamQuery: A continuous query over in-flight data stored in ObjectGrid maps.

None

Static grid configuration: A static, cluster-based topology using the cluster deployment XML file.

Replaced with the improved, dynamic deployment topology for managing large data grids.

Deprecated system properties: System properties to specify the server and client properties files are deprecated.

You can still use these arguments, but change the system properties to the new values.

-Dcom.ibm.websphere.objectgrid.CatalogServerProperties

The property was deprecated in WebSphere eXtreme Scale v7.0. Use the -Dobjectgrid.server.props property.

-Dcom.ibm.websphere.objectgrid.ClientProperties

The property was deprecated in WebSphere eXtreme Scale v7.0. Use the -Dobjectgrid.client.props property.

-Dobjectgrid.security.server.prop

The property was deprecated in WebSphere eXtreme Scale v6.1.0.3. Use the -Dobjectgrid.server.prop property.

-serverSecurityFile

This argument was deprecated in WebSphere eXtreme Scale v6.1.0.3. This option is passed into the startOgServer script. Use the -serverProps argument.

Parent topic:
WebSphere eXtreme Scale overview

Related concepts

WebSphere eXtreme Scale major concepts
Plan overview
Integrate with WebSphere products
Product name changes
Free trial
Program and Administration Guides

Related reference

Directory conventions

+
Search Tips | Advanced Search

Feature	Description
DB2 client information integration	Integrate eXtreme Scale JPA Loader plug-ins with DB2, so when DB2 is used as the backend database, the WebSphere eXtreme Scale information (username, workstation name, application name, and accounting information) can be made available in the DB2 Performance Monitor. This feature allows enabling and disabling configuration of client info to DB2. This function is disabled by default. For more information, see Monitor eXtreme Scale information in DB2 for more information.
Catalog service domain configuration	Catalog service domains can be configured using the WAS administrative console or using administrative tasks. Catalog service domains define a group. For more information, see Create catalog service domains.
Multi-master replication	Multiple data centers can be linked together asynchronously, allowing data center to access data locally and maintain high availability. See Multi-master data grid replication topologies (AP) for more information.
Last update time TTL evictor	The TTL evictor has been updated to track the time in which an entry was updated, expanding on the time-to-live evictor. For more information, see TimeToLive (TTL) evictor
usedBytes statistics for in-memory grids	The amount of memory that is used by cache entries in a BackingMap can be tracked using all of the statistics providers. For more information, see Cache memory consumption sizing.
Dynamic statistics	Statistics can now be enabled and disabled on demand. For more information, see Monitor with managed beans (MBeans).
Monitor console	The graphical monitoring console provides current and historical views into WebSphere eXtreme Scale server statistics. For more information, see Monitor with the web console.
Improved HTTP Session Manager	Configuration of the HTTP session manager has been simplified. You can now configure the HTTP session manager in the WAS administrative console. For more information, see Create session persistence to a data grid.
Multi-homed client support	Clients can be configured to use a specific network adapter. For more information, see Client properties file.
ISA Lite	IBM Support Assistant Lite for WebSphere eXtreme Scale provides automatic data collection and symptom analysis support for problem determination scenarios. For more information, see IBM support assistant for WebSphere eXtreme Scale.
REST	The REST data service provides non-Java clients access to eXtreme Scale data, supporting the Open Data Protocol (OData), providing full compatibility with Microsoft WCF Data Services. For more information, see REST data services overview.
Client-only installation	WebSphere eXtreme Scale clients can now be installed independently, decreasing the installation footprint for WebSphere eXtreme Scale applications. For more information, see Install WebSphere eXtreme Scale.

Deprecation	Recommended migration action
catalog.services.cluster cell and server property: This custom property was used to define a group of catalog servers in the WAS configuration.	This custom property is deprecated starting in the v7.1 release. Create a catalog service domain in the WAS administrative console, which creates the same configuration as using the custom property. See Create catalog service domains for more information.
CoreGroupServicesMBean MBean and interface	This MBean is deprecated starting in the v7.1 release. Use the CatalogServiceManagementMBean instead.
ServerMBean.updateTraceSpec() MBean operation	This operation is deprecated starting in the v7.1 release. Use the TraceSpec attribute on the DynamicServerMBean instead.
CoreGroupServicesMBean MBean	This MBean is deprecated starting in the v7.1 release. Use the CatalogServiceManagementMbean MBean instead.
ServiceUnavailableException exception	This exception is deprecated starting in the v7.1 release. Use the TargetNotAvailableException exception instead.
Partitioning facility (WPF): The partitioning facility is a set of programming APIs that allow Java EE applications to support asymmetric clustering.	The capabilities of WPF can be alternatively realized in WebSphere eXtreme Scale.
StreamQuery: A continuous query over in-flight data stored in ObjectGrid maps.	None
Static grid configuration: A static, cluster-based topology using the cluster deployment XML file.	Replaced with the improved, dynamic deployment topology for managing large data grids.
Deprecated system properties: System properties to specify the server and client properties files are deprecated.	You can still use these arguments, but change the system properties to the new values. -Dcom.ibm.websphere.objectgrid.CatalogServerProperties The property was deprecated in WebSphere eXtreme Scale v7.0. Use the -Dobjectgrid.server.props property. -Dcom.ibm.websphere.objectgrid.ClientProperties The property was deprecated in WebSphere eXtreme Scale v7.0. Use the -Dobjectgrid.client.props property. -Dobjectgrid.security.server.prop The property was deprecated in WebSphere eXtreme Scale v6.1.0.3. Use the -Dobjectgrid.server.prop property. -serverSecurityFile This argument was deprecated in WebSphere eXtreme Scale v6.1.0.3. This option is passed into the startOgServer script. Use the -serverProps argument.