Deprecated properties and APIs

The following list of properties and APIs were deprecated in the specified releases. Use the recommended migration action to determine how to update your configuration.

[Version 8.5 and later]

Deprecated items in Version 8.5

Table 1. Deprecated properties and APIs
Deprecation Recommended migration action
WebSphereTransactionCallback
This plug-in was used to manage data grid transactions with enterprise applications that run in a WebSphere® Application Server environment.

[Version 8.5 and later] The WebSphereTransactionCallback interface has been replaced by the WebSphere eXtreme Scale resource adapter, which enables Java Transaction API (JTA) transaction management. You can install this resource adapter on WebSphere Application Server or other Java Platform, Enterprise Edition (Java EE) application servers. The WebSphereTransactionCallback plug-in is not an enlisted JTA API, and therefore, is not designed to roll back the JTA transaction if the commit fails.

Deprecated items in Version 7.1.1

Table 2. Deprecated properties and APIs
Deprecation Recommended migration action
com.ibm.websphere.objectgrid.plugins.builtins.TranPropListener class
This class was used to propagate successful ObjectGrid transaction commit processes to other WebSphere application servers hosting the same ObjectGrid instance, based upon the ObjectGrid name.

The TranPropListener interface has been replaced by the JMSObjectGridEventListener interface, which is a JMS-based implementation of the ObjectGridEventListener interface. It supports client-side, near cache invalidation and peer-to-peer replication.

com.ibm.websphere.objectgrid.plugins.OptimisticCallback class
This class was used to provide optimistic comparison operations for the values of a map.

The OptimisticCallback plug-in has been replaced by the ValueDataSerializer.Versionable interface, which you can implement when you use the DataSerializer plug-in with the COPY_TO_BYTES copy mode or when you use the @Version annotation with the EntityManager API. See the API documentation for more information.

com.ibm.websphere.objectgrid.plugins.NoVersioningOptimisticCallback plug-in
This plug-in was used for optimistic locking without doing version checking. With this built-in OptimisticCallback handler, the loader handled version checking, but optimistic locking was used to ensure that committed data is always returned on a read.

The NoVersioningOptimisticCallback interface extends the OptimisticCallback interface. Therefore, use the pessimistic locking strategy with a default transaction isolation of READ_COMMITTED or lower. See Tuning locking performance for more information.

com.ibm.websphere.objectgrid.plugins.ObjectTransformer class
This plug-iin was used to serialize, deserialize, and copy objects into the cache.

The ObjectTransformer interface has been replaced by the DataSerializer plug-ins, which you can use to efficiently store arbitrary data in WebSphere eXtreme Scale so that existing product APIs can efficiently interact with your data.

com.ibm.websphere.objectgrid.BackingMap.setMapEventListeners method
This method was used to set the list of MapEventListener objects.

Use either the addMapEventListener(EventListener) or removeMapEventListener(EventListener) methods to add or remove event listeners from a backing map.

com.ibm.websphere.objectgrid.ObjectGrid.setEventListeners method
This method was used to overwrite the current list of ObjectGridEventListener objects and replace it with the supplied list of ObjectGridEventListeners objects.

Use either the addEventListener(EventListener) or removeEventListener(EventListener) methods to add or remove event listeners or life cycle listeners from the data grid.

Stabilized features in Version 7.1.1

If a feature is listed as stabilized, IBM does not currently plan to deprecate or remove this capability in a subsequent release of the product; but future investment will be focused on the alternative function. Users do not need to change any existing applications and scripts that use a stabilized function; but they should consider using the strategic alternative for new applications.

Table 3. Deprecated properties and APIs
Stabilized feature Recommended migration action
xsadmin
The xsadmin utility is provided as a sample of how you can create custom utilities for your deployment.

Use the xscmd utility to complete administrative tasks in the environment such as: establishing multi-master replication links, overriding quorum, and stopping groups of servers with the teardown command.

Deprecated items in Version 7.1

Table 4. Deprecated properties and APIs
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 WebSphere Application Server configuration.

This custom property is deprecated starting in the Version 7.1 release.

Create a catalog service domain in the WebSphere Application Server administrative console, which creates the same configuration as using the custom property. See Creating catalog service domains in WebSphere Application Server for more information.

CoreGroupServicesMBean MBean and interface

This MBean is deprecated starting in the Version 7.1 release.

Use the CatalogServiceManagementMBean instead.

ServerMBean.updateTraceSpec() MBean operation

This operation is deprecated starting in the Version 7.1 release.

Use the TraceSpec attribute on the DynamicServerMBean instead.

CoreGroupServicesMBean MBean

This MBean is deprecated starting in the Version 7.1 release.

Use the CatalogServiceManagementMbean MBean instead.

ServiceUnavailableException exception

This exception is deprecated starting in the Version 7.1 release.

Use the TargetNotAvailableException exception instead.

 

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 your system properties to the new values.

-Dcom.ibm.websphere.objectgrid.CatalogServerProperties
The property was deprecated in WebSphere eXtreme Scale Version 7.0. Use the -Dobjectgrid.server.props property.
-Dcom.ibm.websphere.objectgrid.ClientProperties
The property was deprecated in WebSphere eXtreme Scale Version 7.0. Use the -Dobjectgrid.client.props property.
-Dobjectgrid.security.server.prop
The property was deprecated in WebSphere eXtreme Scale Version 6.1.0.3. Use the -Dobjectgrid.server.prop property.
-serverSecurityFile
This argument was deprecated in WebSphere eXtreme Scale Version 6.1.0.3. This option is passed into the startOgServer script. Use the -serverProps argument.