Deprecated and removed features

Deprecated and removed features

+
Search Tips | Advanced Search

Overview

Various features have been either deprecated or removed in WAS product offerings since V5.0.
If a feature is listed here as deprecated, IBM intends to remove this capability in a future release of the product. Generally, IBM will not remove a feature until at least two major releases or three full years (whichever is longer) after the release in which it is deprecated. For example, features that were deprecated in WAS V5.0, Version 5.0.1, or V5.0.2 will not be removed from the product until after Version 6.0 because both V5.0.x and V5.1.x are considered to be 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.

Deprecated and removed features

See the following topics to find more information on deprecated and removed features:

Deprecation list
Removal list

Deprecation list

The following tables summarize deprecated features by version and release. The tables indicate what is being 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 V6.1
Features deprecated in V6.0.2
Features deprecated in V6.0
Features deprecated in V5.1.1
Features deprecated in V5.1
Features deprecated in V5.0.2
Features deprecated in V5.0.1
Features deprecated in V5.0

Features deprecated in V6.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.
See 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 WebContainer MBean functions:

startTransports

stopTransports

restartWebApplication

Begin moving to the channel framework.
The channel framework provides the TransportChannelService MBean, which is more flexible and has more methods than the current WebContainer 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 WAS.
See EJB query to SQL syntax to help determine which back-end you should use when the deprecated SQL92 and SQL99 back-ends are no longer available.
IBM WebSphere Studio tools runtime support provided by the following classes (which were used to leverage VAJava 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 appserver or a J2EE application client to the JMS Server component of the embedded messaging feature in WAS V5
This deprecation includes the following:

Ability to define JMS resource definitions for the V5 default messaging provider

Ability to establish connections from client applications that are either running in a V5 environment or utilizing V5 default messaging provider resource definitions

Perform the following actions:

Ensure that any JMS Server messaging providers that are hosted on WebSphere Application Server V5.1 appservers are moved onto Version 6.0 or later appservers. This task is handled automatically when you migrate a V5.x server to V6.0 or later.

Change all JMS resource definitions to use the new V6 default messaging provider instead of the V5 default messaging provider.

System Administration WebSphere administrative (wsadmin) scripting support for the Jacl language Begin converting your existing Jacl syntax wsadmin scripts into Jython syntax wsadmin scripts, and use Jython syntax for any new wsadmin scripting.
For more information, go to Application Server Toolkit > Administering applications > Developing automation scripts in this information center.
setup command Use the install command.
clientUpgrade command No migration action is necessary.
wasprofile command Use the manageprofiles command.
See 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.
See Data source minimum required settings, by vendor.
Derby Network Server Using Universal JDBC Driver Provider, which uses the db2jcc.jar file Start using the Derby Network Server Using Derby Client provider, which uses the derbyclient.jar file and has the benefit of supporting XA.
See JDBC providers.
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 ORB properties specified for it will be ignored. The custom ORB properties of interest are com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.*.
See 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.
See the Java Servlet 2.4 Specification, 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.
Start 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 datasource custom properties:

dbFailOverEnabled

connRetriesDuringDBFailover

connRetryIntervalDuringDBFailover

Replace the deprecated properties with new properties.

Use validateNewConnection instead of dbFailOverEnabled.

Use validateNewConnectionRetryCount instead of connRetriesDuringDBFailover.

Use validateNewConnectionRetryInterval instead of connRetryIntervalDuringDBFailover.

If both 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 console.
See Disabling file locking.
Security Simple WebSphere Authentication Mechanism (SWAM) Use the mechanism.
See LTPA.
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, see Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS).
Performance Support for the Java Virtual Machine Profiler Interface (JVMPI) is deprecated along with three related JVM runtime counters:

ObjectMovedCount

ObjectFreedCount

ObjectAllocateCount

Begin moving to the Java Virtual Machine Tool Interface (JVMTI).
See JVM Tool Interface (JVMTI).
Support for the Java Virtual Machine Debugger Interface (JVMDI) Begin moving to the Java Virtual Machine Tool Interface (JVMTI).
See JVM Tool Interface (JVMTI).
Problem Determination Message ID format that is used in WebSphere Application Server V6.0.x and earlier
The message prefixes for log files were not previously registered with the primary message registry. WebSphere Application Server V6.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.
See Converting log files to use IBM unique Message IDs.
The com.ibm.etools.logging.util plug-in, thelogutil.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 V1.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, see the com.ibm.etools.logging.util\doc\IBM_Logging_Utilities_Migration_Guide.html document.
Edge Component 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:

WAS ND proxy server

IBM HTTP Server plug-in in WAS ND

See Setting up the proxy server.
Edge component Caching Proxy function Use the Edge component Load Balancer with Media Access Control (MAC) forwarding in conjunction with one of the following:

WAS ND proxy server

IBM HTTP Server plug-in in WAS ND

See Setting up the proxy server and Setting up caching in the proxy server.
Features deprecated in V6.0.2
Category Deprecation Recommended Migration Action
Application Programming Model
The following methods from class com.ibm.websphere.runtime.ServerName:
initialize(java.lang.String 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 WAS 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 WAS runtime.
Features deprecated in V6.0
Category Deprecation Recommended Migration Action
Application Programming Model and Container Support
Support for the following tsx tags in the JavaServer Pages 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 WAS V6.0, and the tag library is shipped with the product. Use the following 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 back-end IDs:

SQL92 (1992 SQL Standard)

SQL99 (1999 SQL Standard)

Use other back-end IDs.
See EJB query to SQL syntax to help determine which back-end IDs you should use.
Application Services JRAS Extensions API
No further enhancements are planned for JRAS support.

Use the equivalent function in the java.util.logging package (JSR47).
UDDI V2 EJB interface to the UDDI Registry There is no replacement for the EJB interface. This interface is included in WAS V6.0 for compatibility with V5.x. Users do not need to take any specific actions and can continue to use the V2 EJB API, but they should be aware that it does not include any UDDI functionality that is new to UDDI V3 and the interface might be removed in a future release of WAS.
The UDDI4J V2 class library, the uddi4jv2.jar file Start using the V3 UDDI APIs. A client library is provided to simplify constructing and sending UDDI V3 requests from Java. This is the IBM UDDI V3 Client for Java, provided in uddiv3client.jar. The UDDI4J APIs can still be used, but you should be aware that they do not provide access to any of the new UDDI V3 functionality and they might be removed in a future release of WAS.
All of the low-level UDDI Utility Tools (UUT) APIs, such as BusinessStub, ServiceStub, and so on,
These 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 future release of WAS. 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

Also, container-managed authentication aliases on a J2C Connection Factory or datasource are deprecated.
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 application's resource binding information.
ApplicationProfile property on the WorkManager panel in the console
See the articles in the Application profiling section for the differences between application profiling in V5.x and Version 6.0.x.
Two items from the DataSource panel in the administrative console:

Container-Managed Authentication Alias

DefaultPrincipleMapping

Define Container-Managed Authentication Alias and DefaultPrincipleMapping properties on the Resource Reference.
All classes in the com.ibm.websphere.servlet.filter package:

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.
MIME filtering
MIME filters were first introduced in WAS V3.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 the functionality of MIME filters. javax.servlet.filters are standard APIs, and are supported by all compliant appservers.
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 WAS Tool (AST).
All the methods and fields in 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 shipped with WebSphere Application Server in the databeans.jar file, Instead of using data access beans, you should use Service Data Objects (SDO).
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.
See 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 is deprecated in favor of the WSS 1.0 implementation. 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, migrate applications to J2EE 1.4 first. The next step is to use AST/RAD tooling to reconfigure WSS for the migrated application. There is no automatic migration of WSS in this release of AST/RAD tooling for V6.0; the migration has to be done manually. The following SPI has also been deprecated:
com.ibm.wsspi.wssecurity.config.KeyLocator We need to migrate your implementation to the new SPI for WSS 1.0 support in V6.0:
com.ibm.wsspi.wssecurity.keyinfo.KeyLocator
Finally, the JAAS LoginModule implementation needs to be migrated to the new programming model for JAAS LoginModule in V6.0.
Secure Authentication Service (SAS) IIOP security protocol Use the Common Secure Interoperability V2 (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, see Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS).
System Administration Configure 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 V5.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 V4.0 to programmatically gather performance data from WAS The 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 MBeans, or from the WebSphere PMI Perf MBean. While the J2EE MBeans provide performance data about a specific component, the Perf MBean acts as a gateway to the WAS PMI service, and provides access to the performance data for all the components.
Features deprecated in V5.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:

MS SQL Server 2000 Driver for JDBC

SequeLink JDBC driver for MS SQL Server

If you are using either of these JDBC drivers and still want to use MS 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 shipped with WebSphere Application Server, which is free for use with WAS.

Features deprecated in V5.1
Category Deprecation Recommended Migration Action
Installation and Migration Tools The Application Assembly Tool (AAT) that is used for developing J2EE applications is replaced with the Assembly Tool (ATk) component of the Application Server Toolkit (ASTk). Instead of running the Application Assembly Tool, users will install and run the Assembly Toolkit component of the Application Server Toolkit. ASTk is based on the Eclipse framework. Upon starting the ASTk, the J2EE function is found by opening the J2EE Perspective.
Business processes modeled with WebSphere Studio Application Developer Integration Edition V5.0 or earlier Business processes modeled with WebSphere Studio Application Developer Integration Edition V5.0 or earlier need to be migrated to a BPEL-based process. Use the Migrate option provided with WebSphere Studio Application Developer Integration Edition V5.1.
Several process choreographer API interfaces and methods used for business processes created with WebSphere Studio Application Developer Integration Edition V5.0 or earlier. A detailed 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 WAS will not be packaged in future releases.
Go to JDOM and get the latest copy of JDOM and bundle it inside your application.
Customers running WebSphere Studio Application Developer Integration Edition Version 4.1 applications will need to migrate them to WebSphere Studio Application Developer Integration Edition V5.0.
The C++ Object Request Broker (ORB), the C++ library for IDL value types and the WAS C++ security client
IBM will no longer ship or support the Common Object Request Broker Architecture (CORBA) C++ Developer Kit. The CORBA technology is a bridge for migration to a J2EE (J2EE) and WAS environment.
In addition to the preceding information, the CORBA C++ client feature will be removed from the Application Clients installation image in future releases.
IBM recommends 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, see Manage 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:

CORBA Interoperability Samples documentation

IBM WebSphere Application Servers CORBA Interoperability white paper

IBM Cloudscape V5.1.x Use the Cloudscape Network Server JDBC driver.
Server IBM HTTP Server (IHS) V1.3.x If you are using IHS V1.3.x with modules that:

are shipped as part of IHS V1.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), we need to obtain IHS/Apache 2 versions of these modules from the third party.

have been customized or are inhouse, port these modules to the new IHS/Apache 2 API.

Application Programming Model and Container Support Bean Scripting Framework (BSF) JavaServer Pages 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 console will also be unaffected.
This functionality will continue to exist in WAS Version 5.1 and succeeding releases until V6.0. If debugging JSP files, you might have to restart the appserver during JavaScript debugging sessions.
Business Rule Bean programming interfaces -- Public classes, methods, attributes as in:

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 have been deprecated in these 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.
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 -- V5.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:
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.
Old method signature
public String getStackTrace();  
// returns a String representation of the exception stack
New method signature (JDK 1.4, WAS 5.1)
public StackTraceElement[] getStackTrace(); 
// returns an array of stack trace elements
Replacement method (WAS 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, change your application to use the replacement method.
Application Services Data access binaries -- Common Connector Framework:
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 see Accessing data using J2EE 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 console by selecting Application Servers on the left, choosing the appserver 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 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 mechanism.
See LTPA.
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 V5.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 Web Services for J2EE standards for more information.
Scheduler (com.ibm.websphere.scheduler) programming interfaces -- V5.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.
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 WAS 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.
DB2 390 Local JDBC Provider (RRS) This provider is replaced with the DB2 zOS Local JDBC Provider (RRS).
testConnection command in the AdminControl scripting object ($AdminControl TestConnection configId props) Running this command in WAS, V5.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 WAS, V5.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 WAS, V5.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 V5.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.
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 WAS runtime.
Features deprecated in V5.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).
Removal list

The following tables describe what is removed—such as features, APIs, scripting interfaces, tools, wizards, publicly exposed configuration data, naming identifiers, and constants. Where possible, the recommended replacement is identified.

Features removed in V6.1

Features removed in V6.0

Features removed in V6.1

Feature Recommended Migration Action

com.ibm.websphere.security.CustomRegistry interface Use the com.ibm.websphere.security.UserRegistry interface.
See Migrating custom user registries.
Support for the Secure Authentication Service (SAS) IIOP security protocol Use the Common Secure Interoperability V2 (CSIv2) protocols.
Support for the 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, see Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS).
Support for the Common Connector Framework (CCF) Use the J2EE Connector Architecture (JCA) solution.
For information on using the J2EE Connector Architecture, see Accessing data using J2EE Connector Architecture connectors.
Support for the IBM Cloudscape V5.1.x database Use the IBM Cloudscape V10.1 database.
This database provides Derby V10.1 binaries, NLS enablement, QA, and IBM problem support.
When using WAS, you will see the term "Derby" rather than "Cloudscape" used in places such as the administrative console, the ejbdeploy command, and others.
Profile creation wizard Use the Profile Management tool.
For information on using the Profile Management tool to create a profile, see Creating profiles through the graphical user interface.
Log Analyzer, the tool that was previously provided for viewing and analyzing the activity or service log file Use the Log and Trace Analyzer tool for Eclipse in the Application Server Toolkit (AST). This tool is installable from the AST launchpad console.
For more information, go to Application Server Toolkit > Detecting and analyzing runtime problems > Log and Trace Analyzer in this information center.
Mozilla Rhino JavaScript (js.jar) Use the Rhino code available from Mozilla.
Go to Rhino: JavaScript for Java and get the latest copy of Rhino.
Java Document Object Model (JDOM) Use the code available from the JDOM organization.
Go to JDOM, get the latest copy of JDOM, and bundle it inside your application.
Class preloading function No migration action is necessary.
The following samples from the Samples Gallery:

Adventure Builder

Greenhouse by WebSphere

WebSphere Bank

The following technology samples from the Samples Gallery:

Bean-Managed Persistence (BMP)

Container-Managed Persistence (CMP) 1.1

Container-Managed Persistence (CMP) 2.1

Container-Managed Relationships (CMR)

EJB Time

Filter Servlet

JavaServer Pages 2.0

Message-Driven Beans (MDB)

Pagelist Servlet

Simple JavaServer Pages

Simple Servlet

Stateful Session

TagLib

No migration action is necessary.

Features removed in V6.0

Component Classes and interfaces

activity
com.ibm.ws.activity.ActivityConstants
com.ibm.ws.activity.ActivityService
com.ibm.ws.activity.ActivityServiceInitializer
com.ibm.ws.activity.ActivityTrace
com.ibm.ws.activity.GlobalIdImpl
com.ibm.ws.activity.HighlyAvailableServiceManager
com.ibm.ws.activity.HLSLiteDataInterface
com.ibm.ws.activity.HLSLiteExtended
com.ibm.ws.activity.HLSLiteInfo
com.ibm.ws.activity.j2ee_activity_specific_data
com.ibm.ws.activity.j2ee_activity_specific_dataHelper
com.ibm.ws.activity.ServiceMigration
com.ibm.ws.activity.VUTrace
com.ibm.ws.activity.WebSphereServiceManager
com.ibm.ws.activity.WebSphereUserActivity
com.ibm.ws.javax.activity.ActionErrorException
com.ibm.ws.javax.activity.ActionNotFoundException
com.ibm.ws.javax.activity.ActivityCoordinator
com.ibm.ws.javax.activity.ActivityInformation
com.ibm.ws.javax.activity.ActivityManager
com.ibm.ws.javax.activity.ActivityNotProcessedException
com.ibm.ws.javax.activity.ActivityPendingException
com.ibm.ws.javax.activity.ActivityToken
com.ibm.ws.javax.activity.CompletionStatus
com.ibm.ws.javax.activity.ContextPendingException
com.ibm.ws.javax.activity.CoordinationInformation
com.ibm.ws.javax.activity.GlobalId
com.ibm.ws.javax.activity.InvalidParentContextException
com.ibm.ws.javax.activity.InvalidStateException
com.ibm.ws.javax.activity.NoActivityException
com.ibm.ws.javax.activity.NoImplementException
com.ibm.ws.javax.activity.NotOriginatorException
com.ibm.ws.javax.activity.Outcome
com.ibm.ws.javax.activity.PersistentActivityCoordinator
com.ibm.ws.javax.activity.PropertyGroupContext
com.ibm.ws.javax.activity.PropertyGroupRegisteredException
com.ibm.ws.javax.activity.PropertyGroupUnknownException
com.ibm.ws.javax.activity.ServiceAlreadyRegisteredException
com.ibm.ws.javax.activity.ServiceInformation
com.ibm.ws.javax.activity.ServiceNotRegisteredException
com.ibm.ws.javax.activity.Signal
com.ibm.ws.javax.activity.SignalSetActiveException
com.ibm.ws.javax.activity.SignalSetInactiveException
com.ibm.ws.javax.activity.SignalSetUnknownException
com.ibm.ws.javax.activity.Status
com.ibm.ws.javax.activity.SystemException
com.ibm.ws.javax.activity.TimeoutRangeException
com.ibm.ws.javax.activity.UserActivity
com.ibm.ws.javax.activity.coordination.Action
com.ibm.ws.javax.activity.coordination.RecoverableAction
com.ibm.ws.javax.activity.coordination.ServiceManager
com.ibm.ws.javax.activity.coordination.SignalSet
com.ibm.ws.javax.activity.coordination.SubordinateSignalSet
com.ibm.ws.javax.activity.propertygroup.PropertyGroup
com.ibm.ws.javax.activity.propertygroup.PropertyGroupManager
com.ibm.ws.javax.ejb.ActivityCompletedLocalException
com.ibm.ws.javax.ejb.ActivityRequiredLocalException
com.ibm.ws.javax.ejb.InvalidActivityLocalException

admin com.ibm.websphere.management.application.EarUtils
als com.ibm.websphere.als.BufferManager
anttasks
com.ibm.websphere.ant.tasks.endptEnabler.Property
com.ibm.websphere.ant.tasks.Java2WSDL.Mapping
com.ibm.websphere.ant.tasks.Messages
com.ibm.websphere.ant.tasks.WSDL2Java.Mapping

dynacache com.ibm.websphere.servlet.cache.CacheConfig
ras
com.ibm.ras.RASConsoleHandler
com.ibm.ras.RASEnhancedMessageFormatter
com.ibm.ras.RASEnhancedTraceFormatter
com.ibm.ras.RASErrorHandler com.ibm.ras.RASFileHandler
com.ibm.ras.RASFormatter com.ibm.ras.RASHandler
com.ibm.ras.RASMessageFormatter
com.ibm.ras.RASMultiFileHandler
com.ibm.ras.RASSerialFileHandler com.ibm.ras.RASSocketHandler
com.ibm.ras.RASTextAreaHandler
com.ibm.ras.RASTraceFormatter
com.ibm.websphere.ras.WsOrbRasManager

security
com.ibm.websphere.security.AuthorizationTable
com.ibm.websphere.security.FileRegistrySample
com.ibm.websphere.security.SecurityProviderException
com.ibm.websphere.security.WASPrincipal
com.ibm.websphere.security.auth.AuthDataFileEnc

userprofile
com.ibm.websphere.userprofile.UserProfile
com.ibm.websphere.userprofile.UserProfileCreateException
com.ibm.websphere.userprofile.UserProfileExtender
com.ibm.websphere.userprofile.UserProfileFinderException
com.ibm.websphere.userprofile.UserProfileManager
com.ibm.websphere.userprofile.UserProfileProperties
com.ibm.websphere.userprofile.UserProfileRemoveException

Scheduler API
com.ibm.websphere.scheduler.pmi.SchedulerPmiModule
com.ibm.websphere.scheduler.pmi.SchedulerPerf

Scheduler API com.ibm.websphere.scheduler.MessageTaskInfo.setJMSPriority()
ObjectPool APIs
com/ibm/websphere/objectpool/pmi/ObjectPoolPerf.java
com/ibm/websphere/objectpool/pmi/ObjectPoolPmiModule.java

Asynchronous Beans APIs
com/ibm/websphere/asynchbeans/pmi/AlarmManagerPerf.java
com/ibm/websphere/asynchbeans/pmi/AsynchBeanPerf.java
com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorManagerPerf.java
com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorPerf.java
com/ibm/websphere/asynchbeans/pmi/AlarmManagerPmiModule.java
com/ibm/websphere/asynchbeans/pmi/AsynchBeanPmiModule.java
com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorManagerPmiModule.java
com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorPmiModule.java

Related tasks
Migrating and coexisting

Related information
Reference: Generated API documentation

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. See 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 WebContainer MBean functions: startTransports stopTransports restartWebApplication	Begin moving to the channel framework. The channel framework provides the TransportChannelService MBean, which is more flexible and has more methods than the current WebContainer 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 WAS. See EJB query to SQL syntax to help determine which back-end you should use when the deprecated SQL92 and SQL99 back-ends are no longer available.
IBM WebSphere Studio tools runtime support provided by the following classes (which were used to leverage VAJava 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 appserver or a J2EE application client to the JMS Server component of the embedded messaging feature in WAS V5 This deprecation includes the following: Ability to define JMS resource definitions for the V5 default messaging provider Ability to establish connections from client applications that are either running in a V5 environment or utilizing V5 default messaging provider resource definitions	Perform the following actions: Ensure that any JMS Server messaging providers that are hosted on WebSphere Application Server V5.1 appservers are moved onto Version 6.0 or later appservers. This task is handled automatically when you migrate a V5.x server to V6.0 or later. Change all JMS resource definitions to use the new V6 default messaging provider instead of the V5 default messaging provider.
System Administration	WebSphere administrative (wsadmin) scripting support for the Jacl language	Begin converting your existing Jacl syntax wsadmin scripts into Jython syntax wsadmin scripts, and use Jython syntax for any new wsadmin scripting. For more information, go to Application Server Toolkit > Administering applications > Developing automation scripts in this information center.
setup command	Use the install command.
clientUpgrade command	No migration action is necessary.
wasprofile command	Use the manageprofiles command. See 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. See Data source minimum required settings, by vendor.
Derby Network Server Using Universal JDBC Driver Provider, which uses the db2jcc.jar file	Start using the Derby Network Server Using Derby Client provider, which uses the derbyclient.jar file and has the benefit of supporting XA. See JDBC providers.
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 ORB properties specified for it will be ignored. The custom ORB properties of interest are com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.*. See 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. See the Java Servlet 2.4 Specification, 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. Start 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 datasource custom properties: dbFailOverEnabled connRetriesDuringDBFailover connRetryIntervalDuringDBFailover	Replace the deprecated properties with new properties. Use validateNewConnection instead of dbFailOverEnabled. Use validateNewConnectionRetryCount instead of connRetriesDuringDBFailover. Use validateNewConnectionRetryInterval instead of connRetryIntervalDuringDBFailover. If both 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 console. See Disabling file locking.
Security	Simple WebSphere Authentication Mechanism (SWAM)	Use the mechanism. See LTPA.
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, see Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS).
Performance	Support for the Java Virtual Machine Profiler Interface (JVMPI) is deprecated along with three related JVM runtime counters: ObjectMovedCount ObjectFreedCount ObjectAllocateCount	Begin moving to the Java Virtual Machine Tool Interface (JVMTI). See JVM Tool Interface (JVMTI).
Support for the Java Virtual Machine Debugger Interface (JVMDI)	Begin moving to the Java Virtual Machine Tool Interface (JVMTI). See JVM Tool Interface (JVMTI).
Problem Determination	Message ID format that is used in WebSphere Application Server V6.0.x and earlier The message prefixes for log files were not previously registered with the primary message registry. WebSphere Application Server V6.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. See Converting log files to use IBM unique Message IDs.
The com.ibm.etools.logging.util plug-in, thelogutil.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 V1.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, see the com.ibm.etools.logging.util\doc\IBM_Logging_Utilities_Migration_Guide.html document.
Edge Component	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: WAS ND proxy server IBM HTTP Server plug-in in WAS ND See Setting up the proxy server.
Edge component Caching Proxy function	Use the Edge component Load Balancer with Media Access Control (MAC) forwarding in conjunction with one of the following: WAS ND proxy server IBM HTTP Server plug-in in WAS ND See Setting up the proxy server and Setting up caching in the proxy server.

Category	Deprecation	Recommended Migration Action
Application Programming Model	The following methods from class com.ibm.websphere.runtime.ServerName: initialize(java.lang.String 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 WAS 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 WAS runtime.

Category	Deprecation	Recommended Migration Action
Application Programming Model and Container Support	Support for the following tsx tags in the JavaServer Pages 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 WAS V6.0, and the tag library is shipped with the product. Use the following 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 back-end IDs: SQL92 (1992 SQL Standard) SQL99 (1999 SQL Standard)	Use other back-end IDs. See EJB query to SQL syntax to help determine which back-end IDs you should use.
Application Services	JRAS Extensions API No further enhancements are planned for JRAS support.	Use the equivalent function in the java.util.logging package (JSR47).
UDDI V2 EJB interface to the UDDI Registry	There is no replacement for the EJB interface. This interface is included in WAS V6.0 for compatibility with V5.x. Users do not need to take any specific actions and can continue to use the V2 EJB API, but they should be aware that it does not include any UDDI functionality that is new to UDDI V3 and the interface might be removed in a future release of WAS.
The UDDI4J V2 class library, the uddi4jv2.jar file	Start using the V3 UDDI APIs. A client library is provided to simplify constructing and sending UDDI V3 requests from Java. This is the IBM UDDI V3 Client for Java, provided in uddiv3client.jar. The UDDI4J APIs can still be used, but you should be aware that they do not provide access to any of the new UDDI V3 functionality and they might be removed in a future release of WAS.
All of the low-level UDDI Utility Tools (UUT) APIs, such as BusinessStub, ServiceStub, and so on, These 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 future release of WAS. 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 Also, container-managed authentication aliases on a J2C Connection Factory or datasource are deprecated.	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 application's resource binding information.
ApplicationProfile property on the WorkManager panel in the console	See the articles in the Application profiling section for the differences between application profiling in V5.x and Version 6.0.x.
Two items from the DataSource panel in the administrative console: Container-Managed Authentication Alias DefaultPrincipleMapping	Define Container-Managed Authentication Alias and DefaultPrincipleMapping properties on the Resource Reference.
All classes in the com.ibm.websphere.servlet.filter package: 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.
MIME filtering MIME filters were first introduced in WAS V3.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 the functionality of MIME filters. javax.servlet.filters are standard APIs, and are supported by all compliant appservers. 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 WAS Tool (AST).
All the methods and fields in 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 shipped with WebSphere Application Server in the databeans.jar file,	Instead of using data access beans, you should use Service Data Objects (SDO).
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. See 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 is deprecated in favor of the WSS 1.0 implementation.	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, migrate applications to J2EE 1.4 first. The next step is to use AST/RAD tooling to reconfigure WSS for the migrated application. There is no automatic migration of WSS in this release of AST/RAD tooling for V6.0; the migration has to be done manually. The following SPI has also been deprecated: com.ibm.wsspi.wssecurity.config.KeyLocator We need to migrate your implementation to the new SPI for WSS 1.0 support in V6.0: com.ibm.wsspi.wssecurity.keyinfo.KeyLocator Finally, the JAAS LoginModule implementation needs to be migrated to the new programming model for JAAS LoginModule in V6.0.
Secure Authentication Service (SAS) IIOP security protocol	Use the Common Secure Interoperability V2 (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, see Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS).
System Administration	Configure 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 V5.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 V4.0 to programmatically gather performance data from WAS	The 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 MBeans, or from the WebSphere PMI Perf MBean. While the J2EE MBeans provide performance data about a specific component, the Perf MBean acts as a gateway to the WAS PMI service, and provides access to the performance data for all the components.

Category	Deprecation	Recommended Migration Action
Installation and Migration Tools	The Application Assembly Tool (AAT) that is used for developing J2EE applications is replaced with the Assembly Tool (ATk) component of the Application Server Toolkit (ASTk).	Instead of running the Application Assembly Tool, users will install and run the Assembly Toolkit component of the Application Server Toolkit. ASTk is based on the Eclipse framework. Upon starting the ASTk, the J2EE function is found by opening the J2EE Perspective.
Business processes modeled with WebSphere Studio Application Developer Integration Edition V5.0 or earlier	Business processes modeled with WebSphere Studio Application Developer Integration Edition V5.0 or earlier need to be migrated to a BPEL-based process. Use the Migrate option provided with WebSphere Studio Application Developer Integration Edition V5.1.
Several process choreographer API interfaces and methods used for business processes created with WebSphere Studio Application Developer Integration Edition V5.0 or earlier. A detailed 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 WAS will not be packaged in future releases.	Go to JDOM and get the latest copy of JDOM and bundle it inside your application. Customers running WebSphere Studio Application Developer Integration Edition Version 4.1 applications will need to migrate them to WebSphere Studio Application Developer Integration Edition V5.0.
The C++ Object Request Broker (ORB), the C++ library for IDL value types and the WAS C++ security client IBM will no longer ship or support the Common Object Request Broker Architecture (CORBA) C++ Developer Kit. The CORBA technology is a bridge for migration to a J2EE (J2EE) and WAS environment. In addition to the preceding information, the CORBA C++ client feature will be removed from the Application Clients installation image in future releases.	IBM recommends 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, see Manage 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: CORBA Interoperability Samples documentation IBM WebSphere Application Servers CORBA Interoperability white paper
IBM Cloudscape V5.1.x	Use the Cloudscape Network Server JDBC driver.
Server	IBM HTTP Server (IHS) V1.3.x	If you are using IHS V1.3.x with modules that: are shipped as part of IHS V1.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), we need to obtain IHS/Apache 2 versions of these modules from the third party. have been customized or are inhouse, port these modules to the new IHS/Apache 2 API.
Application Programming Model and Container Support	Bean Scripting Framework (BSF) JavaServer Pages 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 console will also be unaffected. This functionality will continue to exist in WAS Version 5.1 and succeeding releases until V6.0. If debugging JSP files, you might have to restart the appserver during JavaScript debugging sessions.
Business Rule Bean programming interfaces -- Public classes, methods, attributes as in: 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 have been deprecated in these 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. 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 -- V5.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: 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. Old method signature public String getStackTrace(); // returns a String representation of the exception stack New method signature (JDK 1.4, WAS 5.1) public StackTraceElement[] getStackTrace(); // returns an array of stack trace elements Replacement method (WAS 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, change your application to use the replacement method.
Application Services	Data access binaries -- Common Connector Framework: 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 see Accessing data using J2EE 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 console by selecting Application Servers on the left, choosing the appserver 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 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 mechanism. See LTPA.
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.

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 Web Services for J2EE standards for more information.
Scheduler (com.ibm.websphere.scheduler) programming interfaces -- V5.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. 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 WAS 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.
DB2 390 Local JDBC Provider (RRS)	This provider is replaced with the DB2 zOS Local JDBC Provider (RRS).
testConnection command in the AdminControl scripting object ($AdminControl TestConnection configId props) Running this command in WAS, V5.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 WAS, V5.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 WAS, V5.0.2 or later returns the following message: WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported.	There is no replacement for this command.

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).

Feature	Recommended Migration Action
com.ibm.websphere.security.CustomRegistry interface	Use the com.ibm.websphere.security.UserRegistry interface. See Migrating custom user registries.
Support for the Secure Authentication Service (SAS) IIOP security protocol	Use the Common Secure Interoperability V2 (CSIv2) protocols.
Support for the 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, see Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS).
Support for the Common Connector Framework (CCF)	Use the J2EE Connector Architecture (JCA) solution. For information on using the J2EE Connector Architecture, see Accessing data using J2EE Connector Architecture connectors.
Support for the IBM Cloudscape V5.1.x database	Use the IBM Cloudscape V10.1 database. This database provides Derby V10.1 binaries, NLS enablement, QA, and IBM problem support. When using WAS, you will see the term "Derby" rather than "Cloudscape" used in places such as the administrative console, the ejbdeploy command, and others.
Profile creation wizard	Use the Profile Management tool. For information on using the Profile Management tool to create a profile, see Creating profiles through the graphical user interface.
Log Analyzer, the tool that was previously provided for viewing and analyzing the activity or service log file	Use the Log and Trace Analyzer tool for Eclipse in the Application Server Toolkit (AST). This tool is installable from the AST launchpad console. For more information, go to Application Server Toolkit > Detecting and analyzing runtime problems > Log and Trace Analyzer in this information center.
Mozilla Rhino JavaScript (js.jar)	Use the Rhino code available from Mozilla. Go to Rhino: JavaScript for Java and get the latest copy of Rhino.
Java Document Object Model (JDOM)	Use the code available from the JDOM organization. Go to JDOM, get the latest copy of JDOM, and bundle it inside your application.
Class preloading function	No migration action is necessary.
The following samples from the Samples Gallery: Adventure Builder Greenhouse by WebSphere WebSphere Bank The following technology samples from the Samples Gallery: Bean-Managed Persistence (BMP) Container-Managed Persistence (CMP) 1.1 Container-Managed Persistence (CMP) 2.1 Container-Managed Relationships (CMR) EJB Time Filter Servlet JavaServer Pages 2.0 Message-Driven Beans (MDB) Pagelist Servlet Simple JavaServer Pages Simple Servlet Stateful Session TagLib	No migration action is necessary.

Component	Classes and interfaces
activity	com.ibm.ws.activity.ActivityConstants com.ibm.ws.activity.ActivityService com.ibm.ws.activity.ActivityServiceInitializer com.ibm.ws.activity.ActivityTrace com.ibm.ws.activity.GlobalIdImpl com.ibm.ws.activity.HighlyAvailableServiceManager com.ibm.ws.activity.HLSLiteDataInterface com.ibm.ws.activity.HLSLiteExtended com.ibm.ws.activity.HLSLiteInfo com.ibm.ws.activity.j2ee_activity_specific_data com.ibm.ws.activity.j2ee_activity_specific_dataHelper com.ibm.ws.activity.ServiceMigration com.ibm.ws.activity.VUTrace com.ibm.ws.activity.WebSphereServiceManager com.ibm.ws.activity.WebSphereUserActivity com.ibm.ws.javax.activity.ActionErrorException com.ibm.ws.javax.activity.ActionNotFoundException com.ibm.ws.javax.activity.ActivityCoordinator com.ibm.ws.javax.activity.ActivityInformation com.ibm.ws.javax.activity.ActivityManager com.ibm.ws.javax.activity.ActivityNotProcessedException com.ibm.ws.javax.activity.ActivityPendingException com.ibm.ws.javax.activity.ActivityToken com.ibm.ws.javax.activity.CompletionStatus com.ibm.ws.javax.activity.ContextPendingException com.ibm.ws.javax.activity.CoordinationInformation com.ibm.ws.javax.activity.GlobalId com.ibm.ws.javax.activity.InvalidParentContextException com.ibm.ws.javax.activity.InvalidStateException com.ibm.ws.javax.activity.NoActivityException com.ibm.ws.javax.activity.NoImplementException com.ibm.ws.javax.activity.NotOriginatorException com.ibm.ws.javax.activity.Outcome com.ibm.ws.javax.activity.PersistentActivityCoordinator com.ibm.ws.javax.activity.PropertyGroupContext com.ibm.ws.javax.activity.PropertyGroupRegisteredException com.ibm.ws.javax.activity.PropertyGroupUnknownException com.ibm.ws.javax.activity.ServiceAlreadyRegisteredException com.ibm.ws.javax.activity.ServiceInformation com.ibm.ws.javax.activity.ServiceNotRegisteredException com.ibm.ws.javax.activity.Signal com.ibm.ws.javax.activity.SignalSetActiveException com.ibm.ws.javax.activity.SignalSetInactiveException com.ibm.ws.javax.activity.SignalSetUnknownException com.ibm.ws.javax.activity.Status com.ibm.ws.javax.activity.SystemException com.ibm.ws.javax.activity.TimeoutRangeException com.ibm.ws.javax.activity.UserActivity com.ibm.ws.javax.activity.coordination.Action com.ibm.ws.javax.activity.coordination.RecoverableAction com.ibm.ws.javax.activity.coordination.ServiceManager com.ibm.ws.javax.activity.coordination.SignalSet com.ibm.ws.javax.activity.coordination.SubordinateSignalSet com.ibm.ws.javax.activity.propertygroup.PropertyGroup com.ibm.ws.javax.activity.propertygroup.PropertyGroupManager com.ibm.ws.javax.ejb.ActivityCompletedLocalException com.ibm.ws.javax.ejb.ActivityRequiredLocalException com.ibm.ws.javax.ejb.InvalidActivityLocalException
admin	com.ibm.websphere.management.application.EarUtils
als	com.ibm.websphere.als.BufferManager
anttasks	com.ibm.websphere.ant.tasks.endptEnabler.Property com.ibm.websphere.ant.tasks.Java2WSDL.Mapping com.ibm.websphere.ant.tasks.Messages com.ibm.websphere.ant.tasks.WSDL2Java.Mapping
dynacache	com.ibm.websphere.servlet.cache.CacheConfig
ras	com.ibm.ras.RASConsoleHandler com.ibm.ras.RASEnhancedMessageFormatter com.ibm.ras.RASEnhancedTraceFormatter com.ibm.ras.RASErrorHandler com.ibm.ras.RASFileHandler com.ibm.ras.RASFormatter com.ibm.ras.RASHandler com.ibm.ras.RASMessageFormatter com.ibm.ras.RASMultiFileHandler com.ibm.ras.RASSerialFileHandler com.ibm.ras.RASSocketHandler com.ibm.ras.RASTextAreaHandler com.ibm.ras.RASTraceFormatter com.ibm.websphere.ras.WsOrbRasManager
security	com.ibm.websphere.security.AuthorizationTable com.ibm.websphere.security.FileRegistrySample com.ibm.websphere.security.SecurityProviderException com.ibm.websphere.security.WASPrincipal com.ibm.websphere.security.auth.AuthDataFileEnc
userprofile	com.ibm.websphere.userprofile.UserProfile com.ibm.websphere.userprofile.UserProfileCreateException com.ibm.websphere.userprofile.UserProfileExtender com.ibm.websphere.userprofile.UserProfileFinderException com.ibm.websphere.userprofile.UserProfileManager com.ibm.websphere.userprofile.UserProfileProperties com.ibm.websphere.userprofile.UserProfileRemoveException
Scheduler API	com.ibm.websphere.scheduler.pmi.SchedulerPmiModule com.ibm.websphere.scheduler.pmi.SchedulerPerf
Scheduler API	com.ibm.websphere.scheduler.MessageTaskInfo.setJMSPriority()
ObjectPool APIs	com/ibm/websphere/objectpool/pmi/ObjectPoolPerf.java com/ibm/websphere/objectpool/pmi/ObjectPoolPmiModule.java
Asynchronous Beans APIs	com/ibm/websphere/asynchbeans/pmi/AlarmManagerPerf.java com/ibm/websphere/asynchbeans/pmi/AsynchBeanPerf.java com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorManagerPerf.java com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorPerf.java com/ibm/websphere/asynchbeans/pmi/AlarmManagerPmiModule.java com/ibm/websphere/asynchbeans/pmi/AsynchBeanPmiModule.java com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorManagerPmiModule.java com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorPmiModule.java