Deprecated features

If you are migrating from an earlier release of WebSphere® Application Server, you should be aware of the various features that have been deprecated in this and earlier releases.

If a feature is listed here as deprecated, IBM® might remove this capability in a subsequent release of the product. Future investment will be focussed on the strategic function listed under "Recommended Migration Actions." Typically, a feature is not removed until at least two major releases or three full years (whichever time period is longer) after the release in which that feature is deprecated. For example, features that are deprecated in Version 6.0, Version 6.0.1, or Version 6.0.2 are not removed from the product until after Version 7.0 because both Version 6.0.x and Version 6.1.x are major releases. In rare cases, it might become necessary to remove features sooner; such cases are indicated clearly and explicitly in the descriptions of these deprecated features in this article.

The following tables summarize deprecated features by version and release. The tables indicate what is deprecated—such as application programming interfaces (APIs), scripting interfaces, tools, wizards, publicly exposed configuration data, naming identifiers, and constants. Where possible, the tables also indicate the recommended migration action.

This article contains the following deprecation tables:

Features deprecated in Version 7.0

Table 1. Features deprecated in Version 7.0. This table describes the features that are deprecated in Version 7.0.
Category Deprecation Recommended Migration Action
Application programming model registerSynchronizationCallbackForCurrentTran method in the com.ibm.websphere.jtaextensions.ExtendedJTATransaction interface Use the registerInterposedSynchronization method of the TransactionSynchronizationRegistry interface instead.

For more information, read JTA support.

com.ibm.ws.extensionhelper.TransactionControl interface Use the com.ibm.wsspi.uow.UOWManager interface instead.

For more information, read JTA support.

HttpServletRequestProxy class in the com.ibm.websphere.servlet.request package Use the HttpServletRequestWrapper class instead of the HttpServletRequestProxy class. You can use the subclasses of this class to overload or enhance the functionality of a server-provided HttpServletRequest.
HttpServletResponseProxy class in the com.ibm.websphere.servlet.response package Use the HttpServletResponseWrapper class instead of the HttpServletResponseProxy class. You can use the subclasses of this class to overload or enhance the functionality of a server-provided HttpServletResponse.
The following classes, interfaces, methods, and fields of the WebSphere relational resource adapter:
  • Classes:
    • com.ibm.websphere.rsadapter.JdbcAccessorImpl
    • com.ibm.websphere.rsadapter.OracleDataStoreHelper
  • Interfaces:
    • com.ibm.websphere.rsadapter.Beginnable
    • com.ibm.websphere.rsadapter.HandleStates
    • com.ibm.websphere.rsadapter.Reassociateable
    • com.ibm.websphere.rsadapter.WSNativeConnectionAccessor
  • Methods:
    • com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn)
    • com.ibm.websphere.rsadapter.WSCallHelper.call
    • com.ibm.websphere.rsadapter.WSConnection.getClientInformation
    • com.ibm.websphere.rsadapter.WSConnection.setClientInformation
    • com.ibm.ws.rsadapter.cci.WSResourceAdapterBase.getNativeConnection (javax.resource.cci.Connection)
    • com.ibm.ws.rsadapter.cci.WSResourceAdapterBase.getNativeConnection (com.ibm.ws.rsadapter.jdbc.WSJdbcConnection)
    • com.ibm.ws.rsadapter.jdbc.WSJdbcUtil.getNativeConnection (com.ibm.ws.rsadapter.jdbc.WSJdbcConnection)
  • Fields:
    • com.ibm.websphere.rsadapter.WSConnection.CLIENT_ACCOUNTING_INFO
    • com.ibm.websphere.rsadapter.WSConnection.CLIENT_APPLICATION_NAME
    • com.ibm.websphere.rsadapter.WSConnection.CLIENT_ID
    • com.ibm.websphere.rsadapter.WSConnection.CLIENT_LOCATION
    • com.ibm.websphere.rsadapter.WSConnection.CLIENT_OTHER_INFO
    • com.ibm.websphere.rsadapter.WSConnection.CLIENT_TYPE
If you are using the OracleDataStoreHelper, switch to Oracle 10g or 11g and use the Oracle10gDataStoreHelper or Oracle11gDataStoreHelper instead.

Instead of using getNativeConnection, use the Java™ Database Connectivity (JDBC) 4.0 wrapper pattern.

Instead of WSConnection client information, use JDBC 4.0 client-information APIs.

Instead of com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn), use the com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn, boolean logEvent) method. The new method provides a boolean parameter that allows you to control whether or not connection error events are logged to system out.

Instead of WSCallHelper.call, use standard Java reflections APIs.

The following session-management function:
  • Sharing sessions across Web modules within an enterprise application (shared session context)
  • Global session sharing through the Servlet21SessionCompatibility property
  • Session tracking using the SSL ID (rather than cookies or URL-rewriting)
  • Support for any session-manager properties as system properties
  • Support for any session-manager properties as Web container custom properties
For session sharing, redesign your applications so that the session is appropriately scoped at the Web module as specified in the Java Servlet Specification Version 2.2 and later. If data must be shared across the Web-module boundary, the IBMApplicationSession should be used.

For session tracking using the SSL ID, re-configure to use cookies or else modify the application and re-configure it to use URL rewriting.

Rather than specifying session manager properties as system or Web container custom properties, use session-manager custom properties.

Connection validation by SQL query Use the timeout-based validation introduced with JDBC 4.0.
Classes:
  • SERV1\ws\code\admin.thinclient\build\classes\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgr*.class
  • SERV1\ws\code\admin.thinclient\build\classes\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgrImpl*.class

Interface: SERV1\ws\code\admin.thinclient\src\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgr.java

Methods: All methods in the RemoteCommandMgr interface and MBean xml, SERV1\ws\code\admin.jmx\src\com\ibm\ws\management\ descriptor\xml\RemoteCommandMgr.xml

Constructor: RemoteCommandMgrImpl()

No migration action is necessary.
The following proprietary classes that are used to represent and manipulate WS-Addressing endpoint references in Java API for XML Web Services (JAX-WS) 2.0:
  • com.ibm.websphere.wsaddressing.jaxws.W3CEndpointReference
  • com.ibm.websphere.wsaddressing.jaxws.SubmissionEndpointReference
  • com.ibm.websphere.wsaddressing.jaxws.EndpointReferenceConverter
Use the following classes instead:
  • javax.xml.ws.wsaddressing.W3CEndpointReference
  • com.ibm.websphere.wsaddressing.jaxws21.SubmissionEndpointReference
  • com.ibm.websphere.wsaddressing.jaxws21.EndpointReferenceConverter
The following Websphere Common Configuration Model (WCCM) types:
  • SIBJMSProvider
  • SIBJMSConnectionFactory
  • SIBJMSQueueConnectionFactory
  • SIBJMSTopicConnectionFactory
  • SIBJMSQueue
  • SIBJMSTopic
If one of your Jython or Jacl wsadmin scripts uses any of these types, modify the script to use the correct AdminTask command to complete the equivalent function. For example:
AdminTask.listSIBJMSQueues()
Environment IBM HTTP Server (IHS) mod_file_cache module Migrate your IHS configuration directives from mod_file_cache to the appropriate provided cache mechanism—either mod_mem_cache or mod_cache.
IHS mod_ibm_ldap module Migrate your mod_ibm_ldap configuration directives to the equivalent mod_ldap directives.
IHS mod_mime_magic module Remove any IHS configuration directives associated with this module.
IHS mod_proxy_ftp module Remove any IHS configuration directives associated with this module.
IHS mod_afpa_cache module

Adaptive Fast Path Architecture (AFPA) is being deprecated for both AIX® and Windows® operating systems for both static and dynamically generated content caching.

Remove any IHS configuration directives associated with this module.
Installation and maintenance tools Support for using IBM Update Installer for WebSphere Software Version 6.x to apply maintenance on WebSphere Application Server Version 6.0.2.21+ and Version 6.1.0.x Use IBM Update Installer for WebSphere Software Version 7.0.

Update Installer Version 7.0 supports applying maintenance on WebSphere Application Server Version 6.0.2.21+, Version 6.1.0.x, and Version 7.0.

Support for using IBM WebSphere Installation Factory Version 6.1 to create installation packages for WebSphere Application Server Version 6.1 Use IBM WebSphere Installation Factory Version 7.0.

WebSphere Installation Factory Version 7.0 supports creating installation packages for WebSphere Application Server Version 6.1 and Version 7.0.

J2EE resources The following features:
  • Support for using JMS providers that are not compliant with the J2EE Connector Architecture 1.5 specification is deprecated.

    The WebSphere Application Server Version 5 default messaging provider was deprecated in Version 6.1.

  • The WebSphere MQ messaging provider was updated in Version 7.0 to support the J2EE Connector Architecture 1.5. Support for other usages of this provider are deprecated.
Use JMS providers that are compliant with the J2EE Connector Architecture 1.5 specification.
Data access disablePK54589 system property Configure the data source custom property isConnectionSharingBasedOnCurrentState.

If you are using disablePK54589=true, you can replace it with isConnectionSharingBasedOnCurrentState=false.

Programming Shipment of JavaServer Faces widget library (JWL) with WebSphere Application Server Manually create a shared library for JWL using the jar from Rational® Application Developer.
Profile management manager profile template Use the management profile template with a deployment manager server.
Servers Shipment of Apache Struts 1.1, 1.2.4, and 1.2.7 as optional libraries within WebSphere Application Server If you would like to continue using these versions of Apache Struts, they are available from the Apache Struts Web site.
For core group transport, the following configuration options:
  • Unicast
  • Multicast
Move to channel framework transport.

For more information, read Core group transports.

System administration Option to install the Pluggable application client feature for the IBM Application Client for WebSphere Application Server Use the new EJB Thin Application Client feature instead.
The following service integration bus (SIBus) security features:
  • -secure flag on the createSIBus and the modifySIBus commands
  • listInheritSenderForTopic, listInheritReceiverForTopic, and listInheritDefaultsForDestination commands
  • Inter-engine authentication alias
Perform the following actions:
  • Use the -busSecurity flag instead of the -secure flag.
  • Replace usages of the listInheritSenderForTopic, listInheritReceiverForTopic, and listInheritDefaultsForDestination commands with the isInheritSenderForTopic, isInheritReceiverForTopic, and isInheritDefaultsForDestinaton commands respectively.
  • Remove any usage of the -interEngineAuthenticationAlias option on the createSIBus and modifySIBus commands.
Collector tool (collector.bat or collector.sh) that gathers information about the WebSphere Application Server installation and packages it in a Java archive (JAR) file that you can send to IBM Software Support Use AutoPD.

For more information, read Automate data collection for problem determination, Part 1: The Automated Problem Determination Tool.

Protocol-based proxy server templates Use the administrative console or the wsadmin commands in the ServerManagement command group to select one or multiple protocols for proxy servers.

For more information, read ServerManagement command group for the AdminTask object

WebSphere Touchpoint (WAS.admin.wstp component—all classes and methods) Use the other standard management interfaces in WebSphere Application Server.
Commands in the SecureConversation command group for the AdminTask object Use the commands in the WSSCacheManagement command group to manage Web Service Security (WS-Security) distributed-cache configurations.
The following Lightweight Directory Access Protocol (LDAP) configuration names in the virtual member manager (VMM) federated repository:
  • SECUREWAY, IDS4, IDS51, and IDS6
  • DOMINO5, DOMINO6, and DOMINO65
  • AD2000 and AD2003
Use the following configuration names:
  • IDS rather than SECUREWAY, IDS4, IDS51, or IDS6
  • DOMINO rather than DOMINO5, DOMINO6, or DOMINO65
  • AD rather than AD2000 or AD2003
Web services Support for the '2006/02' WS-Addressing Web Services Description Language (WSDL) binding namespace Replace any uses of the '2006/02' namespace in WSDL files with uses of the '2006/05' namespace
Web Services Distributed Management (WSDM) interface Use the other standard management interfaces in WebSphere Application Server.
IBM proprietary SOAP over Java Message Service (JMS) protocol for Java API for XML Web Services (JAX-WS) or Java API for XML-based RPC (JAX-RPC) applications Use the standard SOAP over JMS protocol.

For more information, read SOAP over JMS protocol and SOAP over Java Message Service .

Restriction: If your client application invokes enterprise-bean based Web services that are supported by a release of WebSphere Application Server that is earlier than Version 7.0, you must continue to use the IBM proprietary SOAP over JMS protocol to access those Web services.

Features deprecated in Version 6.1

Table 2. Features deprecated in Version 6.1. This table describes the features that are deprecated in Version 6.1.
Category Deprecation Recommended Migration Action
Application programming model setDatabaseDefaultIsolationLevel(int) method in the com.ibm.websphere.rsadapter.DataStoreHelperMetaData class Start using the following instead:
public final void 
  setDatabaseDefaultIsolationLevel 
  ( int helperDefaultLevel, 
  int cusDefinedWasDefaultIsoLevel ) 
The following class and interface in the Mediation Framework runtime:
  • com.ibm.websphere.sib.mediation.handler.SIMessageContextException class
  • com.ibm.websphere.sib.mediation.messagecontext.SIMediationBean MessageContext interface
Replace all uses of the com.ibm.websphere.sib,.mediation.handler.SIMessageContextException class with the com.ibm.websphere.sib.mediation.handler.MessageContextException class.

Read Writing a routing mediation for an example.

Replace all uses of the com.ibm.websphere.sib.mediation.messagecontext.SIMediationBean MessageContext interface with an equivalent interface. WebSphere Application Server does not provide an implementation of this interface.

The following Web container message bean functions:
  • startTransports
  • stopTransports
  • restartWebApplication
Begin moving to the channel framework.

The channel framework provides the TransportChannelService message bean, which is more flexible and has more methods than the current Web container transport-related methods.

Support for deploying container-managed entity beans to a generic SQL database If an application uses SQL92 or SQL99 because the application has to run with different relational databases, use the IBM tooling to generate deployed code for each database vendor or version that the application might use. At installation time, specify the database vendor or version that will used with WebSphere Application Server.
IBM WebSphere Studio tools runtime support provided by the following classes (which were used to leverage Visual Age for Java tooling):
  • com.ibm.webtools.runtime.AbstractStudioServlet
  • com.ibm.webtools.runtime.BuildNumber
  • com.ibm.webtools.runtime.NoDataException
  • com.ibm.webtools.runtime.StudioPervasiveServlet
  • com.ibm.webtools.runtime.TransactionFailureException
  • com.ibm.webtools.runtime.WSUtilities
Rearchitect your applications to use standard J2EE coding conventions.
CUSTOM_HELPER constant field in the com.ibm.websphere.rsadapter.DataStoreHelper class API If you create your own DataStoreHelper implementation class, do not invoke setHelperType(DataStoreHelper.CUSTOM_HELPER). Instead, let the HelperType value be set by the implementation class from which it inherits.
J2EE resources Support for the ability to connect from either an application server or a J2EE application client to the JMS Server component of the embedded messaging feature in WebSphere Application Server Version 5
This deprecation includes the following capabilities:
  • Defining JMS resource definitions for the Version 5 default messaging provider
  • Establishing connections from client applications that are either running in a Version 5 environment or utilizing Version 5 default messaging provider resource definitions
Perform the following actions:
  1. Ensure that any JMS Server messaging providers that are hosted on WebSphere Application Server Version 5.1 application servers are moved onto Version 6.0 or later application servers. This task is handled automatically when you migrate a Version 5.x server to Version 6.0 or later.
  2. Change all JMS resource definitions to use the new Version 6 default messaging provider instead of the Version 5 default messaging provider.
System administration setup command Use the install command.
clientUpgrade command No migration action is necessary.
wasprofile command Use the manageprofiles command.

For more information, read manageprofiles command.

The following WASPostUpgrade command parameters:
  • -import xmi_data_file
  • -substitute "key1=value1[;key2=value2;[...]]"
No migration action is necessary.
Cloudscape® datastore helper (com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper) and Cloudscape Network Server datastore helper (com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper) as well as their types in DataStoreHelper For existing configurations, no migration action is necessary. The migration utility changes the deprecated Cloudscape helpers to Derby helpers.

For new configurations, use the Derby datastore helpers and types instead of the Cloudscape datastore helpers.

For more information, read Data source minimum required settings, by vendor.

DB2® Legacy CLI-based Type 2 JDBC Driver provider Start using the DB2 Universal JDBC Driver Provider.
Logical pool distribution support (com.ibm.websphere.csi.ThreadPoolStrategy.LogicalPoolDistribution) No migration action is necessary.

When this function is removed, however, all custom Object Request Broker (ORB) properties that you specified for it will be ignored. The custom ORB properties of interest are com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.*.

For more information, read Logical pool distribution and Object Request Broker custom properties.

ORB thread pool configuration as part of the Server object in the server.xml file Use the thread pool configuration that is part of the ServerIndex object in the serverindex.xml file.
JVM system property com.ibm.websphere.sendredirect.compatibility Begin modifying your applications to redirect non-relative URLs, those starting with a forward slash ("/"), relative to the servlet container root (web_server_root) instead of the web application context root.

Read the Java Servlet 2.4 Specification, which is available for download at http://jcp.org/aboutJava/communityprocess/final/jsr154/, for information on how sendRedirect should behave.

Web container PageList Servlet custom extension, including the following classes:
  • com.ibm.servlet.ClientList
  • com.ibm.servlet.ClientListElement
  • com.ibm.servlet.MLNotFoundException
  • com.ibm.servlet.PageListServlet
  • com.ibm.servlet.PageNotFoundException
Rearchitect your applications to use javax.servlet.filter classes rather than com.ibm.servlet classes.

Starting with the Java Servlet 2.3 specification, javax.servlet.filter classes give you the capability to intercept requests and examine responses. They also allow provide chaining functionality as well as functionality for embellishing or truncating responses.

The following custom properties for a data source:
  • validateNewConnection
  • validateNewConnectionRetryCount
  • validateNewConnectionRetryInterval
The product now offers these properties as pre-configured options, which are the replacement properties in the following list. To avoid runtime error messages, permanently disable the original custom properties by deleting them from the list of custom properties.
  • validateNewConnection is replaced by Pretest new connection
  • validateNewConnectionRetryCount is replaced by Number of retries
  • validateNewConnectionRetryInterval is replaced by Retry interval
Note: If the new properties and old properties coexist, the new properties take precedence.
DISABLE_FILE_LOCKING transaction service custom property Clear the Enable file locking check box on the Transaction Service panel of the administrative console.

For more information, read Disabling file locking.

Simple WebSphere Authentication Mechanism (SWAM) Use the Lightweight Third-Party Authentication (LTPA) mechanism.

For more information, read Lightweight Third Party Authentication.

Security LoginHelper CORBA authentication helper function (com.ibm.ws.security.util.LoginHelper) Migrate to the Java Authentication and Authorization Service (JAAS) programming model. For information on this migration, read Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS).
com.ibm.ws.security.web.WebSealTrustAssociationInterceptor trust association interceptor (TAI) interface

This Tivoli® TAI interceptor that implements the WebSphere Application Server TAI interface was provided to support WebSEAL Version 4.1.

If you plan to use WebSEAL 5.1 or later, you should migrate to use the com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus interceptor.
Support for the Java Virtual Machine Profiler Interface (JVMPI) is deprecated along with the following related JVM runtime counters:
  • ObjectMovedCount
  • ObjectFreedCount
  • ObjectAllocateCount
Begin moving to the Java Virtual Machine Tool Interface (JVMTI).

For more information, read JVM Tool Interface (JVMTI).

Performance Support for the Java Virtual Machine Debugger Interface (JVMDI) Begin moving to the Java Virtual Machine Tool Interface (JVMTI).

For more information, read JVM Tool Interface (JVMTI).

Message ID format that is used in WebSphere Application Server Version 6.0.x and earlier

The message prefixes for log files were not previously registered with the primary message registry. WebSphere Application Server Version 6.1.x and later use compliant message prefixes in the output logs.

Use the convertlog command and the MessageConverter class to assist you in migrating tools that rely on the older message format.

For more information, read Converting log files to use IBM unique Message IDs.

Problem determination The com.ibm.etools.logging.util plug-in, the logutil.jar file
  • Logging facility

    Logging facility used for logging Java primitives and complex objects to named loggers; configurable with predefined filtering levels, Logging Agent and file sinks, and output formats through an API, Eclipse plug-in manifest, or Eclipse preference panel

  • Logging agent

    XML-based messaging agent used in conjunction with the IBM Agent Controller to write log and trace XML records to a logging service remotely attachable through an API or Test and Performance Tools Platform (TPTP), formally Hyades, Eclipse workbench

  • Problem determination artifacts and messages

    Original implementation of the Manageability (M12) Model Problem Determination Architecture Version 1.5 and Problem Determination Artifacts Common Data Model specification used for capturing and encoding log and trace data

  • Distributed correlator service (DCS)

    Distributed correlator service that is used for instrumenting correlation identifiers for correlating log and trace data across one or more hosts

  • Java client bindings

    Java client bindings used to communicate with the IBM Agent Controller to launch local and remote processes, attach to running processes, and monitor active agents in a secure client environment

Begin moving plug-ins and application code using configuration files, classes, methods, or variables in the com.ibm.etools.logging.util plug-in to the following replacements:
  • Logging facility

    Replacement: Java Logging APIs in Java Version 1.4.0+; Logging Agent support for the Java Logging APIs provided in TPTP and Common Logging (com.ibm.etools.common.logging/logging.jar)

  • Logging agent

    Replacement: TPTP Logging Agent (org.eclipse.hyades.logging.core/hlcore.jar)

  • Problem determination artifacts and messages

    Replacement: Common Base Event Version 1.0.1 specification and TPTP implementation (org.eclipse.hyades.logging.core/hlcbe101.jar)

  • Distributed correlator service (DCS)

    Replacement: TPTP Correlation Service (org.eclipse.hyades.execution.correlation/hcorrelation.jar)

  • Java client bindings

    Replacement: TPTP Java Client Bindings (org.eclipse.hyades.execution/hexl.jar)

For more information, read the com.ibm.etools.logging.util\doc\IBM_Logging_Utilities_Migration_Guide.html document.
Edge component Edge component Caching Proxy function Use the Edge component Load Balancer with Media Access Control (MAC) forwarding in conjunction with one of the following:
  • WebSphere Application Server, Network Deployment proxy server
  • IBM HTTP Server plug-in in WebSphere Application Server, Network Deployment

For more information, read Setting up the proxy server and Setting up caching in the proxy server.

Edge component Load Balancer function that is associated with the following capabilities:
  • Content-based routing (CBR) component
  • Site Selector component
  • Cisco CSS Controller component
  • Nortel Alteon Controller component
  • Generic routing encapsulation (GRE)
  • Network address translation (NAT) forwarding method
  • CBR forwarding method
  • Remote administration
  • Rules-based load balancing
  • Wide-area load balancing
  • Mutual high availability
  • Simple Network Management Protocol (SNMP) subagent support
  • User Datagram Protocol (UDP) support
Use the Edge component Load Balancer with Media Access Control (MAC) forwarding in conjunction with one of the following:
  • WebSphere Application Server, Network Deployment proxy server
  • IBM HTTP Server plug-in in WebSphere Application Server, Network Deployment

For more information, read Setting up the proxy server.

Features deprecated in Version 6.0.2

Table 3. Features deprecated in Version 6.0.2. This table describes the features that are deprecated in Version 6.0.2
Category Deprecation Recommended Migration Action
Application programming model The following methods from class com.ibm.websphere.runtime.ServerName:
initialize(java.lang.String*!ENTITY!*cell,
  java.lang.String node, 
  java.lang.String server) 
was390Initialize(byte[] a_stoken,
  String a_printable_stoken, 
  String a_jsabpref, 
  int a_pid, 
  int an_asid, 
  String a_jsabjbnm) 
was390Initialize(byte[] a_stoken,
  java.lang.String a_printable_stoken,
  java.lang.String a_jsabpref, 
  int a_pid, 
  int an_asid, 
  java.lang.String a_jsabjbnm, 
  java.lang.String a_smcasid)
These methods are for WebSphere Application Server runtime use only. Applications should not call these methods.
Support for HTTP transport configuration Begin moving to channel-based transport.
Performance com.ibm.websphere.cache.DistributedLockingMap interface Do not use the com.ibm.websphere.cache.DistributedLockingMap interface because this interface is not supported by the WebSphere Application Server runtime.
TYPE_DISTRIBUTED_LOCKING_MAP constant that is defined in the com.ibm.websphere.cache.DistributedObjectCache class Do not use the TYPE_DISTRIBUTED_LOCKING_MAP constant that is defined in the com.ibm.websphere.cache.DistributedObjectCache class because this constant is not supported by the WebSphere Application Server runtime.
System Administration
The following custom properties for a data source:
  • dbFailOverEnabled
  • connRetriesDuringDBFailover
  • connRetryIntervalDuringDBFailover
Replace the properties with the following:
  • Use validateNewConnection instead of dbFailOverEnabled.
  • Use validateNewConnectionRetryCount instead of connRetriesDuringDBFailover.
  • Use validateNewConnectionRetryInterval instead of connRetryIntervalDuringDBFailover.
Note: If the new properties and old properties coexist, the new properties take precedence.

Features deprecated in Version 6.0

Table 4. Features deprecated in Version 6.0. This table describes the features that are deprecated in Version 6.0.
Category Deprecation Recommended Migration Action
Application programming model and container support Support for the following tsx tags in the JavaServer Pages (JSP) engine:
  • repeat
  • dbconnect
  • dbquery
  • getProperty
  • userid
  • passwd
  • dbmodify
Instead of using the tsx tags, you should use equivalent tags from the JavaServer Pages Standard Tag Library (JSTL). JSTL is supported in WebSphere Application Server Version 6.0, and the tag library is included with the product. Use this table as a guideline for converting tsx tags to JSTL tags:
tsx tag            JSTL tag

tsx:repeat         c:forEach
tsx:dbconnect      sql:setDataSource
tsx:dbquery        sql:query
tsx:getProperty    Use standard EL syntax; c:out
                   value="${book.title}" for example, 
                   where book is the current index in 
                   the result set
tsx:userid         Use the user attribute of the
                   setDataSource tag
tsx:passwd         Use the password attribute of
                   the setDataSource tag
tsx:dbmodify       sql:update
The following backend IDs:
  • SQL92 (1992 SQL Standard)
  • SQL99 (1999 SQL Standard)
Use other backend IDs.
Application services JRas Extensions API

No further enhancements are planned for JRas support.

Use the equivalent function in the java.util.logging package (JSR47).

Universal Description, Discovery and Integration (UDDI) Version 2 EJB interface to the UDDI Registry There is no replacement for the EJB interface. This interface is included in WebSphere Application Server Version 6.0 for compatibility with Version 5.x. Users do not need to take any specific actions and can continue to use the Version 2 EJB API; however, they should be aware that it does not include any UDDI functionality that is new to UDDI Version 3 and the interface might be removed in a subsequent release of WebSphere Application Server.
The UDDI4J Version 2 class library, the uddi4jv2.jar file Start using the Version 3 UDDI APIs. A client library is provided to simplify constructing and sending UDDI Version 3 requests from Java. This is the IBM UDDI Version 3 Client for Java, provided in uddiv3client.jar. The UDDI4J APIs can still be used; however, you should be aware that they do not provide access to any of the new UDDI Version 3 functionality and they might be removed in a subsequent release of WebSphere Application Server.
All of the low-level UDDI Utility Tools (UUT) APIs, such as BusinessStub, ServiceStub, and so on,

These APIs are all replaced with the high-level PromoterAPI interface in the com.ibm.uddi.promoter package.

Start using the PromoterAPI interface in the com.ibm.uddi.promoter package in place of these low-level APIs, which will be removed in a subsequent release ofWebSphere Application Server. The PromoterAPI provides the same functionality at a higher level of abstraction.
The following methods in the J2EE Connector Architecture runtime:
  • com.ibm.ws.management.descriptor.xml.ConnectionFactory.xml (getPoolContents and getAllPoolContents methods)
  • com.ibm.websphere.j2c.ConnectionManager interface
  • com.ibm.websphere.j2c.ConnectionEventListener interface
The methods are replaced as follows:
  • getPoolContents and getAllPoolContents are replaced with showPoolContents and showAllPoolContents.
  • ConnectionManager interface is replaced with J2EE Connector Architecture 1.5 LazyAssociatableConnectionManager interface.
  • ConnectionEventListener interface is replaced with J2EE Connector Architecture 1.5 LazyEnlistableConnectionManager interface.

For container-managed authentication aliases, specify the container-managed credentials in the resource binding information for the application.

ApplicationProfile property on the Work manager panel in the administrative console

Read the articles in the Application profiling section for the differences between application profiling in Version 5.x and Version 6.0.x.

The following two items from the Data source panel in the administrative console:
  • Container-Managed Authentication Alias
  • DefaultPrincipleMapping
Define the Container-Managed Authentication Alias and DefaultPrincipleMapping properties on the Resource Reference.
All classes in the com.ibm.websphere.servlet.filter package, including the following:
  • ChainedRequest
  • ChainedResponse
  • ChainerServlet
  • ServletChain
Rearchitect your applications to use javax.servlet.filter classes rather than com.ibm.websphere.servlet.filter classes. Starting from the Servlet 2.3 specification, javax.servlet.filter classes give you the capability to intercept requests and examine responses. They also allow you to achieve chaining functionality, as well as embellishing and truncating responses.
Multipurpose Internet Mail Extensions (MIME) filtering

MIME filters were first supported in WebSphere Application Server Version 3.5 as a way for servlets to embellish, truncate, and modify the responses generated by other servlets, based on the MIME types of the output content.

The javax.servlet.filters, which were introduced in the Servlet 2.3 specification, allow users to plug in filters that can intercept requests to and responses from servlets. They also have the capability to modify content flowing in either direction.

The javax.servlet.filters maintain all of the functionality of MIME filters. javax.servlet.filters are standard APIs, and are supported by all compliant application servers.

Refer to the Servlet 2.3 specification or Servlet filtering for more information.

Container-managed persistence (CMP) entity beans configured with method level access intent might run into data access problems, like deadlock. Therefore, the method level access intent is deprecated. Reconfigure CMP entity beans to use bean level access intent, or reconfigure application profiles with WebSphere Application Server Toolkit.
All of the methods and fields in the com.ibm.websphere.product.product and com.ibm.websphere.product.buildInfo classes
Therefore, the following methods from com.ibm.websphere.product.WASProduct class (which involves com.ibm.websphere.product.product and com.ibm.websphere.product.buildInfo objects) are deprecated:
  • public product getProductByFilename(String basename)
  • public product getProductById(String id)
  • public boolean productPresent(String id)
  • public boolean addProduct(product aProduct)
  • public boolean removeProduct(product aProduct)
  • public Iterator getProducts()
  • public Iterator getProductNames()
  • public String loadVersionInfoAsXMLString(String filename)
  • public String getProductDirName()
  • public static String computeProductDirName()
Use the following supported methods from com.ibm.websphere.product.WASDirectory:
  • public WASProductInfo getWASProductInfo(String id)
  • public boolean isThisProductInstalled(String id)
  • public WASProductInfo[] getWASProductInfoInstances()
  • public String getWasLocation()
Also, instead of getting product information (name, version, build level, build date) from the old WASProduct API (com.ibm.websphere.product.WASProduct), you should now use the following methods in the WASDirectory class to get that information:
  • com.ibm.websphere.product.WASDirectory.getName(String)
  • com.ibm.websphere.product.WASDirectory.getVersion(String)
  • com.ibm.websphere.product.WASDirectory.getBuildLevel(String)
  • com.ibm.websphere.product.WASDirectory.getBuildDate(String)
Data access beans, which are included with WebSphere Application Server in the databeans.jar file Instead of using data access beans, you should use Service Data Objects (SDO).

Read Service Data Objects for additional details.

reloadInterval and reloadingEnabled attributes of the IBM deployment descriptor extensions, including both the WAR file extension (WEB-INF/ibm-web-ext.xmi) and the application extension (META-INF/ibm-application-ext.xmi). Instead of using deployment descriptor extensions, you should use the reload enable and interval options provided during application deployment.

Read Enterprise application settings for additional details.

com.ibm.websphere.servlet.session.UserTransactionWrapper API There is no replacement for this API. The UserTransaction object can be placed directly into the HTTP session without using a wrapper.
Security SOAP-Security (XML digital signature) based on Apache SOAP implementation Instead of using SOAP-Security, you should migrate your application to JSR-109 implementation of Web service. Also, migrate (reconfigure your application) to use WSS (Web Service Security) 1.0 implementation.
Web Service Security (WSS) draft 13 specification-level support Applications should be migrated to the supported WSS 1.0 standard. The draft-level support does not provide interoperability with some third-party vendors, as the message level has been changed between the draft and the WSS 1.0 implementation.

WSS 1.0 is only supported in J2EE 1.4 applications. Therefore, you need to migrate applications to J2EE 1.4 first. The next step is to use Application Server Toolkit or Rational Application Developer tooling to reconfigure WSS for the migrated application. There is no automatic migration of WSS in this release of Application Server Toolkit or Rational Application Developer tooling for Version 6.0; the migration has to be done manually.

The following SPI has also been deprecated:

  com.ibm.wsspi.wssecurity.config.KeyLocator

You need to migrate your implementation to the new SPI for WSS 1.0 support in Version 6.0:

  com.ibm.wsspi.wssecurity.keyinfo.KeyLocator

Finally, the Java Authentication and Authorization Service (JAAS) LoginModule implementation needs to be migrated to the new programming model for JAAS LoginModule in Version 6.0.

Secure Authentication Service (SAS) IIOP security protocol Use the Common Secure Interoperability Version 2 (CSIv2) protocols.
Secure Authentication Service (SAS) CORBA security programming APIs Migrate from the SAS programming APIs to the Java Authentication and Authorization Service (JAAS). For information on this migration, read Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS).
System administration Configuring resources under cell scope You should configure resources under cluster scope instead. In previous releases, you configured cell scope resources to allow the cluster members to share the resource configuration definition. In Version 6, cell scope resource configuration is discouraged because cell scope resources are visible to every node in the cell, even though not every node in the cell is able to support the resource.
depl.extension.reg and installdir options for the install command in the AdminApp scripting object There is no replacement for the depl.extension.reg option. In Version 5.x, this option was a no-op. For the installdir option, use the installed.ear.destination option instead.
Performance PMI Client API, which was introduced in Version 4.0 to programmatically gather performance data from WebSphere Application Server The Java Management Extension (JMX) interface, which is part of the J2EE specification, is the recommended way to gather WebSphere Application Server performance data. PMI data can be gathered from the J2EE-managed object message beans, or from the WebSphere PMI Perf message bean. While the J2EE message beans provide performance data about a specific component, the Perf message bean acts as a gateway to the WebSphere Application Server PMI service, and provides access to the performance data for all of the components.

Features deprecated in Version 5.1.1

Table 5. Features deprecated in Version 5.1.1. This table describes the features that are deprecated in Version 5.1.1.
Category Deprecation Recommended Migration Action
Application programming model and container support Web services gateway customization API

Plan over time to replace your existing filters with a combination of JAX-RPC handlers and service integration bus mediations.

Application services The following Java Database Connectivity (JDBC) drivers:
  • Microsoft® SQL Server 2000 Driver for JDBC
  • SequeLink JDBC driver for Microsoft SQL Server
If you are using either of these JDBC drivers and still want to use Microsoft SQL Server as your database, switch to the Connect JDBC driver. You can purchase the Connect JDBC driver from DataDirect Technologies; or you can use the Connect JDBC driver that is included with WebSphere Application Server, which is free for use with WebSphere Application Server.

Features deprecated in Version 5.1

Table 6. Features deprecated in Version 5.1. This table describes the features that are deprecated in Version 5.1.
Category Deprecation Recommended Migration Action
Installation and migration tools The Application Assembly Tool that is used for developing J2EE applications is replaced with the Assembly Tool component of the Application Server Toolkit. Instead of running the Application Assembly Tool, users will install and run the Assembly Toolkit component of the Application Server Toolkit. The Application Server Toolkit is based on the Eclipse framework. On starting the Application Server Toolkit, the J2EE function is found by opening the J2EE Perspective.
Business processes modeled with WebSphere Studio Application Developer Integration Edition Version 5.0 or earlier Business processes modeled with WebSphere Studio Application Developer Integration Edition Version 5.0 or earlier need to be migrated to a BPEL-based process. Use the Migrate option provided with WebSphere Studio Application Developer Integration Edition Version 5.1.
Several process choreographer API interfaces and methods used for business processes created with WebSphere Studio Application Developer Integration Edition Version 5.0 or earlier. A list can be found in the API documentation provided with process choreographer. Information on the recommended migration action for the deprecated APIs is available in the API documentation for the appropriate API.
JDOM (a Java representation of an XML document that provides an API for efficient reading, manipulating, and writing documentation)

The currently packaged version of JDOM in WebSphere Application Server will not be packaged in subsequent releases.

Go to the JDOM Web site, get the latest copy of JDOM, and bundle it inside your application.
Note: Customers running WebSphere Studio Application Developer Integration Edition Version 4.1 applications will need to migrate them to WebSphere Studio Application Developer Integration Edition Version 5.0.
The C++ Object Request Broker (ORB), the C++ library for IDL value types and the WebSphere Application Server C++ security client

Support is no longer available for the Common Object Request Broker Architecture (CORBA) C++ Developer Kit. The CORBA technology is a bridge for migration to a Java 2 Platform Enterprise Edition (J2EE) and WebSphere Application Server environment.

In addition to the preceding information, the CORBA C++ client feature will be removed from the Application Clients installation image in subsequent releases.

It is recommended that customers migrate to the Object Request Broker (ORB) service for Java technology that ships with WebSphere Application Server. However, there is no equivalent J2EE functionality for the C++ security client or the C++ value-type library. Customers that require such functionality must provide or develop their own.

For information on the ORB service for Java technology, read Managing Object Request Brokers.

The deprecation of the CORBA C++ Developer Kit does not affect support for CORBA interoperability with vendor software for CORBA services. View the following links for additional information about interoperability:
IBM Cloudscape Version 5.1.x Use the Cloudscape WebSphere Application Server, Network DeploymentServer JDBC driver.
Server IBM HTTP Server (IHS) Version 1.3.x If you are using IHS Version 1.3.x with modules that:
  • are included as part of IHS Version 1.3.x packages, you do not need to take any action to migrate those modules.
  • are supplied by a third party (including other IBM products), you need to obtain IHS/Apache 2 versions of these modules from the third party.
  • have been customized or are inhouse, you need to port these modules to the new IHS/Apache 2 API.
Application programming model and container support Bean Scripting Framework (BSF) JavaServer Pages (JSP) execution and debugging functionality The functionality will need to be rearchitected if you are using the JavaScript™, Tcl, and Python languages. If using BSF scripting in your own custom applications, they will be unaffected. Custom scripts written for the WebSphere Application Server administrative console will also be unaffected.

This functionality will continue to exist in WebSphere Application Server Version 5.1 and succeeding releases until Version 6.0. If debugging JSP files, you might have to restart the application server during JavaScript debugging sessions.

The following Business Rule Bean classes, methods, and attributes:
  • Public classes:
    • com.ibm.websphere.brb.RuleImporter
    • com.ibm.websphere.brb.RuleExporter
  • Public method:
    • getLocalRuleManager() on class com.ibm.websphere.brb.TriggerPoint
  • Protected attribute:
    • ruleMgr on class com.ibm.websphere.brb.TriggerPoint
Users do not have to take any action.
Data access programming interfaces in com.ibm.websphere.rsadapter.

Relational resource adapter interface: (com.ibm.websphere.rsadapter).

Methods are deprecated in the following types:

com.ibm.websphere.rsadapter.OracleDataStoreHelper
 public void doSpecialBLobWork(ResultSet rset, 
   InputStream[] data, String[] blobColumnNames)
 public String assembleSqlString(String[] blobColumnNames,
   StringBuffer whereClause, String[] varValues, 
   String tableName)
These relational resource adapter deprecated methods do not impact the application.
Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of OracleDataStoreHelper class. Those deprecated methods will not be called by the WebSphere Application Server runtime.
Scheduler (com.ibm.websphere.scheduler) programming interfaces -- Version 5.x public types in:
  • Interface methods
    scheduler.Scheduler
    public BeanTaskInfo createBeanTaskInfo(); 
    public MessageTaskInfo createMessageTaskInfo();
Use the following methods instead of the deprecated methods:
public Object createTaskInfo(Class 
  taskInfoInterface) throws TaskInfoInvalid;
To create a BeanTaskInfo object using the supported createTaskInfo methods:
BeanTaskInfo ti = (BeanTaskInfo) 
  Scheduler.createTaskInfo(BeanTaskInfo.class);
Web container API modifications:
Note: There are no declared deprecations. The only changes are caused because of a Java API that changed between 1.3 and 1.4.
The changed class is com.ibm.websphere.servlet.error.ServletErrorReport. The return signature for getStackTrace( ) is changed because java.lang.Throwable now defines the same method with a different return signature.
  • Previous method signature
    public String getStackTrace();  
    // returns a String representation of the
    exception stack
  • New method signature (Java Development Kit 1.4, WebSphere Application Server 5.1)
    public StackTraceElement[] getStackTrace(); 
    // returns an array of stack trace
    elements
  • Replacement method (WebSphere Application Server 5.1) (a replacement method that carries on the old functionality has been provided):
    public String getStackTraceAsString(); 
    // returns a String representation
    of the Exception Stack
If you are using com.ibm.websphere.servlet.error.ServletErrorReport.getStackTrace( ) and expecting a return type of String, you need to change your application to use the replacement method.
Application services Data access binaries -- Common Connector Framework, including the following JAR files:
  • ccf.jar
  • ccf2.jar
  • recjava.jar
  • eablib.jar
The J2EE Connector Architecture solution should be used instead of the Common Connector Framework.

For more information on the usage (tools and runtime) of the J2EE Connector Architecture read Accessing data using Java EE Connector Architecture connectors.

Setting the XA partner log directory using the TRANLOG_ROOT variable The setting currently stored in the TRANLOG_ROOT variable (if any) will need to be added to the Transaction Service panel for all servers that need to use the XA partner log. If the default location is to be used, then no action is required. The Transaction Service panel can be found on the administrative console by selecting Application Servers on the left, choosing the application server to be modified, and selecting Transaction Service on the panel that is displayed. The directory currently in TRANLOG_ROOT should be entered in the Logging Directory box on the panel.
Security API for com.ibm.websphere.security.auth.WSPrincipal.getCredential(). Instead of getting the WSCredential from the principal, you should now use one of the following methods to get the Subject that contains the WSCredential:
  • The RunAs Subject is the Subject used for outbound requests.
  • The Caller subject is the Subject that represents the authenticated caller for the current request.
  • The methods to use to get the runAs and caller subjects are as follows:

      com.ibm.websphere.security.auth.WSSubject.getRunAsSubject()

    and

      com.ibm.websphere.security.auth.WSSubject.getCallerSubject()

    respectively.
The following elements in the security programming interface:
  • The interface is deprecated in com.ibm.websphere.security.auth.WSSecurityContext.
  • The exception is deprecated in com.ibm.websphere.security.auth.WSSecurityContextException.
  • The class is deprecated in com.ibm.websphere.security.auth.WSSecurityContextResult.
Use Java Authentication and Authorization Service (JAAS) for all authentication related functionality.
Integrated Cryptographic Services Facility (ICSF) authentication mechanism Use the Lightweight Third-Party Authentication (LTPA) mechanism.

For more information, read Lightweight Third Party Authentication.

System administration The following class:

  com.ibm.websphere.rsadapter.DB2390DataStoreHelper

If you currently use the DB2390DataStoreHelper class for the DB2 Legacy CLI-based provider when you are accessing data, you should now use the DB2DataStoreHelper class.

If you currently use the DB2390DataStoreHelper class for the DB2 Universal JDBC provider when you are accessing data, you should now use the DB2UniversalDataStoreHelper class.

Features deprecated in Version 5.0.2

Table 7. Features deprecated in Version 5.0.2. This table describes the features that are deprecated in Version 5.0.2.
Category Deprecation Recommended Migration Action
Application Programming Model and Container Support Apache SOAP channel in Web services gateway. Gateway services should be deployed to the SOAP HTTP channel instead of the Apache SOAP channel. The Endpoint (URL) of the service will be different for this channel and therefore client programs that are talking to the gateway will need to use the new service Endpoint.
Apache SOAP, WEBSJAVA.SOAP:
  • soap.jar
  • wssoap.jar

See Migrating Apache SOAP Web services to JAX-RPC Web Services based on Java EE standards for more information.

Scheduler (com.ibm.websphere.scheduler) programming interfaces -- Version 5.x public types in:
  • interface method
    scheduler.MessageTaskInfo
    public int setJMSPriority();
Use the following method instead of the deprecated method:
public int getJMSPriority();
Application Services Data access programming interfaces in com.ibm.websphere.rsadapter.

Relational resource adapter interface (com.ibm.websphere.rsadapter)

Methods have been deprecated in these types:

com.ibm.websphere.rsadapter.DataStoreHelper
  public int processSQL(java.lang.String.sqlString, 
    int isolevel, boolean addForUpdate, 
    boolean addextendedForUpdateSyntax);
  public DataStoreAdatperException 
    mapException(DataStoreAdapterException e);
com.ibm.websphere.rsadapter.GenericDataStoreHelper
  public int processSQL(java.lang.String.sqlString, 
    int isolevel, boolean addForUpdate, 
    boolean addextendedForUpdateSyntax);
  public DataStoreAdatperException 
    mapException(DataStoreAdapterException e);
com.ibm.websphere.rsadapter.WSCallHelper
  public static DataStoreHelper 
    createDataStoreHelper(String dsClassName)
These relational resource adapter deprecated methods do not impact the application.
Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of GenericDataStoreHelper. Those deprecated methods will not be called by the WebSphere Application Server runtime.

For com.ibm.websphere.rsadapter.WSCallHelper, use the getDataStoreHelper(datasource) method to get a DataStoreHelper object.

System Administration DB2390DataStoreHelper and DB2390LocalDataStoreHelper classes The DB2DataStoreHelper class now gives all the required helper information needed for the providers that currently use the DB2390DataStoreHelper and the DB2390LocalDataStoreHelper classes.
testConnection command in the AdminControl scripting object ($AdminControl TestConnection configId props)
Running this command in WebSphere Application Server, Version 5.0.2 or later returns the following message:
WASX7390E: Operation not supported - testConnection 
command with config id and properties arguments is not 
supported. Use testConnection command with config id 
argument only.
As of WebSphere Application Server, Version 5.0.2 or later, the preferred way to test a data source connection is the testConnection command passing in the data source configuration ID as the only parameter.
getPropertiesForDataSource command in the AdminControl scripting object ($AdminControl getPropertiesForDataSource configId)
This command incorrectly assumes the availability of the configuration service when you run it in the connected mode. Running this command in WebSphere Application Server, Version 5.0.2 or later returns the following message:
WASX7389E: Operation not supported - 
getPropertiesForDataSource command is 
not supported.
There is no replacement for this command.

Features deprecated in Version 5.0.1

Table 8. Features deprecated in Version 5.0.1. This table describes the features that are deprecated in Version 5.0.1.
Category Deprecation Recommended Migration Action
Application Services Data access programming interfaces in com.ibm.websphere.rsadapter.

Relational resource adapter interface (com.ibm.websphere.rsadapter).

Methods have been deprecated in these types:

com.ibm.websphere.rsadapter.DataStoreHelper
  public int processSQL(java.lang.String sqlString,
    int isolevel);
com.ibm.websphere.rsadapter.GenericDataStoreHelper
  public int processSQL(java.lang.String sqlString,
    int isolevel);
com.ibm.websphere.rsadapter.DB2390DataStoreHelper
  public int processSQL(java.lang.String sqlString, 
    int isolevel);
These relational resource adapter deprecated methods do not impact the application.
Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of com.ibm.websphere.rsadapter.GenericDataStoreHelper. Those deprecated methods will not be called by the WebSphere Application Server runtime.

Features deprecated in Version 5.0

Table 9. Features deprecated in Version 5.0. This table describes the features that are deprecated in Version 5.0.
Category Deprecation Recommended Migration Action
Application Services The following three methods from com.ibm.websphere.appprofile.accessintent.AccessIntent:
public boolean getPessimisticUpdateHintWeakestLockAtLoad();
public boolean getPessimisticUpdateHintNoCollision();
public boolean getPessimisticUpdateHintExclusive();

This is a base API.

Rather than using the three deprecated methods on the AccessIntent interface, developers should use the following method from the same interface:
public int getPessimisticUpdateLockHint();
The possible return values are defined on the AccessIntent interface:
public final static int 
 PESSIMISTIC_UPDATE_LOCK_HINT_NOCOLLISION = 1;
public final static int 
 PESSIMISTIC_UPDATE_LOCK_HINT_WEAKEST_LOCK_AT_LOAD = 2;
public final static int 
 PESSIMISTIC_UPDATE_LOCK_HINT_NONE = 3;
public final static int
 PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE = 4;
Web application programming interfaces -- Various Version 5.x methods in com.ibm.websphere.ServletErrorReport  
Security com.ibm.websphere.security.CustomRegistry interface Use the com.ibm.websphere.security.UserRegistry interface.

See Migrating custom user registries.

Performance Performance Monitoring Infrastructure -- Various Version 5.x public methods in:
  • com.ibm.websphere.pmi.stat.StatsUtil
  • com.ibm.websphere.pmi.PmiJmxTest
  • com.ibm.websphere.pmi.client.PmiClient
These methods are replaced as follows:
  • com.ibm.websphere.pmi.stat.StatsUtil

    There is no replacement for StatsUtil.

  • com.ibm.websphere.pmi.PmiJmxTest

    Use PmiClient.findConfig() instead.

  • com.ibm.websphere.pmi.client.PmiClient

    The getNLSValue (String key) is replaced with getNLSValue (String key, String moduleID).




Reference topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 7:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=rmig_depfeat
File name: rmig_depfeat.html