Deprecated properties and APIs

IBMJSSE and IBMJSSEFIPS

Specifies the name of the context provider for the trust service.

Use the IBMJSSE2 value when you have a Java runtime environment that is provided by IBM. The values, IBMJSSE and IBMJSSEFIPS, are deprecated. Use a JRE from IBM to run an eXtreme Scale server when SSL security is used with the eXtremeIO (XIO) transport. If you use SSL security with the ORB transport and a JRE that is not provided by IBM, then see the documentation from your JRE vendor for an appropriate context provider setting.

numberOfBuckets attribute

The numberOfBuckets attribute in the ObjectGrid descriptor XML file described the number of buckets for the BackingMap instance to use. When set to 0, the client near cache was disabled.

The numberOfBuckets attribute in the ObjectGrid descriptor XML file was replaced with the nearCacheEnabled attribute. For more information, see Configuring the near cache and ObjectGrid descriptor XML file.

client-replicated maps

WebSphere eXtreme Scale clients can replicate maps. However, this function is deprecated, and therefore, not available in the XIO transport protocol of the Java client in Version 8.6. 

Use the continuous query function, instead, which is a superset of the replicated map capability. When you develop client applications that interact with the data grid, you might require queries that retrieve automatic, real-time results when new entries are inserted or updated. For more information, see Notifying clients of map updates using continuous query.

Object Request Broker (ORB)

The Object Request Broker (ORB) is a transport that is used to communicate over a TCP stack. The ORB is dependent on all client applications being written in the Java programming language.

INSERTUPDATE enumeration to the setPutMode

The setPutMode(PutMode.UPSERT) method is added to change the default behavior of the ObjectMap and JavaMap put() and putAll() methods to behave like ObjectMap.upsert() and upsertAll() methods.

The PutMode.UPSERT method replaces the setPutMode(PutMode.INSERTUPDATE) method. Use the PutMode.UPSERT method to tell the BackingMap and loader that an entry in the data grid needs to place the key and value into the grid. The BackingMap and loader does either an insert or an update to place the value into the grid and loader. If you run the upsert API within your applications, then the loader gets an UPSERT LogElement type, which allows loaders to do database merge or upsert calls instead of using insert or update.

startOgSever and stopOgServer commands

The startOgSever and stopOgServer commands are used to start and stop servers that use the ORB transport. If you are using XIO, you can no longer use these scripts to start your servers.

wxs_home/ObjectGrid/legacy/session/bin

This file path location was used for session management scripts prior to WebSphere eXtreme Scale Version 7.1

XIO container TCP secure and non-secure port properties

These ports were used to specify the listener port numbers of the IBM eXtremeIO transport on the server. You set these ports with the xioChannel.xioContainerTCPNonSecure.Port and xioChannel.xioContainerTCPSecure.Port properties in the server properties file.

WebSphereTransactionCallback

This plug-in was used to manage data grid transactions with enterprise applications that run in a WebSphere Application Server environment.

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.

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.

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.

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.