Various features have been either deprecated or removed in WebSphere Application Server product offerings since Version 5.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 WebSphere Application Server Version 5.0, Version 5.0.1, or Version 5.0.2 will not be removed from the product until after Version 6.0 because both Version 5.0.x and Version 5.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
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.
Application Programming Model Features | |
Deprecation | Recommended Migration Action |
The following methods from class com.ibm.websphere.runtime.ServerName
are deprecated: 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 WebSphere Application Server runtime use only. Applications should not call these methods. |
Support for HTTP transport configuration is deprecated. | Begin moving to channel-based transport. |
Performance Features | |
Deprecation | Recommended Migration Action |
The com.ibm.websphere.cache.DistributedLockingMap interface is deprecated. | Do not use the com.ibm.websphere.cache.DistributedLockingMap interface because this interface has never been supported by the WebSphere Application Server run time. |
The TYPE_DISTRIBUTED_LOCKING_MAP constant that is defined in the com.ibm.websphere.cache.DistributedObjectCache class is deprecated. | Do not use the TYPE_DISTRIBUTED_LOCKING_MAP constant that is defined in the com.ibm.websphere.cache.DistributedObjectCache class because this constant has never been supported by the WebSphere Application Server run time. |
Application Programming Model and Container Support Features | |||||||||||||||||
Deprecation | Recommended Migration Action | ||||||||||||||||
Support for the following tsx tags in the JavaServer
Pages (JSP) engine is deprecated:
|
Instead of using the tsx tags, you should
use equivalent tags from the JavaServer Pages Standard Tag Library (JSTL).
JSTL is supported in WebSphere Application Server Version 6.0, and the tag
library is shipped with the product. Use the following table as a guideline
for converting tsx tags to JSTL tags:
|
||||||||||||||||
The following back-end IDs are deprecated:
|
Use other back-end IDs. See EJB query to SQL syntax to help determine which back-end IDs you should use. | ||||||||||||||||
Application Services Features | |||||||||||||||||
Deprecation | Recommended Migration Action | ||||||||||||||||
The WebSphere JRAS Extensions API is deprecated. No further enhancements are planned for JRAS support. | Use the equivalent function in the java.util.logging package (JSR47). | ||||||||||||||||
The UDDI Version 2 EJB interface to the UDDI Registry is deprecated. | There is no replacement for the EJB interface. This interface is included in WebSphere Application Server Version 6.0 for compatibility with Version 5.x. Users do not need to take any specific actions and can continue to use the Version 2 EJB API, but they should be aware that it does not include any UDDI functionality that is new to UDDI Version 3 and the interface might be removed in a future release of WebSphere Application Server. | ||||||||||||||||
The UDDI4J Version 2 class library, uddi4jv2.jar, is deprecated. | Start using the Version 3 UDDI APIs. A client library is provided to simplify constructing and sending UDDI Version 3 requests from Java. This is the IBM UDDI Version 3 Client for Java, provided in uddiv3client.jar. The UDDI4J APIs can still be used, but you should be aware that they do not provide access to any of the new UDDI Version 3 functionality and they might be removed in a future release of WebSphere Application Server. | ||||||||||||||||
All of the low-level UDDI Utility Tools (UUT) APIs, such as BusinessStub, ServiceStub, and so on, are deprecated. 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 WebSphere Application Server. The PromoterAPI provides the same functionality at a higher level of abstraction. | ||||||||||||||||
The following methods in the J2EE Connector Architecture
runtime are deprecated:
Also, container-managed authentication aliases on a J2C Connection Factory or Datasource are deprecated. |
The methods are replaced as follows:
For container-managed authentication aliases, specify the container-managed credentials in the application's resource binding information. |
||||||||||||||||
The ApplicationProfile property on the WorkManager panel in the administrative console is deprecated. | See the articles in the Overview of application profiling section for the differences between application profiling in Version 5.x and Version 6.0.x. | ||||||||||||||||
Two items from the DataSource panel in the administrative
console are deprecated:
|
Define Container-Managed Authentication Alias and DefaultPrincipleMapping properties on the Resource Reference. | ||||||||||||||||
All classes in the com.ibm.websphere.servlet.filter
package are deprecated:
|
Re-architect your legacy 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/or truncating responses. | ||||||||||||||||
MIME filtering is deprecated. MIME filters were first introduced in WebSphere Application Server Version 3.5 as a way for servlets to embellish, truncate, and/or modify the responses generated by other servlets, based on the MIME types of the output content. | 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. javax.servlet.filters maintain all the functionality of MIME filters. javax.servlet.filters are standard APIs, and are supported by all compliant application servers. Refer to the Servlet 2.3 specification or Servlet filtering for more information. |
||||||||||||||||
Container-managed persistence (CMP) entity beans configured with method level access intent might run into data access problems, like deadlock. Therefore, the method level access intent is deprecated. | Re-configure CMP entity beans to use bean level access intent, or re-configure Application profiles with WebSphere Application Server Tool (AST). | ||||||||||||||||
All the methods and fields in com.ibm.websphere.product.product
and com.ibm.websphere.product.buildInfo classes are deprecated. Hence, 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:
|
Use the following supported methods from com.ibm.websphere.product.WASDirectory:
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:
|
||||||||||||||||
Data Access Beans, which are shipped with WebSphere Application Server in databeans.jar, are deprecated. | Instead of using Data Access Beans, you should use Service Data Objects (SDO). | ||||||||||||||||
The reloadInterval and reloadingEnabled attributes of the IBM deployment descriptor extensions are deprecated, 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. | ||||||||||||||||
The com.ibm.websphere.servlet.session.UserTransactionWrapper API is deprecated. | There is no replacement for this API. The UserTransaction object can be placed directly into the HTTP session without using a wrapper. | ||||||||||||||||
Security Features | |||||||||||||||||
Deprecation | Recommended Migration Action | ||||||||||||||||
SOAP-Security (XML digital signature) based on Apache SOAP implementation is deprecated. | 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. Hence, you need to 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 Version 6.0; the migration has to be done manually. The
following SPI has also been deprecated:
com.ibm.wsspi.wssecurity.config.KeyLocator You need to migrate your implementation to the new SPI for WSS 1.0 support in Version 6.0:com.ibm.wsspi.wssecurity.keyinfo.KeyLocator Finally, the Java Authentication and Authorization Service (JAAS) LoginModule implementation needs to be migrated to the new programming model for JAAS LoginModule in Version 6.0. |
||||||||||||||||
The Secure Authentication Service (SAS) IIOP security protocol is deprecated. | Use the Common Secure Interoperability Version 2 (CSIv2) protocols. | ||||||||||||||||
The Secure Authentication Service (SAS) CORBA security programming APIs are deprecated | 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. | ||||||||||||||||
System Administration Features | |||||||||||||||||
Deprecation | Recommended Migration Action | ||||||||||||||||
Configuring resources under cell scope is deprecated. | 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. | ||||||||||||||||
The depl.extension.reg and installdir options for the install command in the AdminApp scripting object are deprecated. | There is no replacement for the depl.extension.reg option. In Version 5.x, this option was a no-op. For the installdir option, use the installed.ear.destination option instead. | ||||||||||||||||
Performance Features | |||||||||||||||||
Deprecation | Recommended Migration Action | ||||||||||||||||
The PMI Client API, which was introduced in Version 4.0 to programmatically gather performance data from WebSphere Application Server, is deprecated. | The Java Management Extension (JMX) interface, which is part of the J2EE specification, is the recommended way to gather WebSphere Application Server performance data. PMI data can be gathered from the J2EE-managed object 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 WebSphere Application Server PMI service, and provides access to the performance data for all the components. |
Application Programming Model and Container Support Features | |
Deprecation | Recommended Migration Action |
The Web services gateway customization API is deprecated. | The Web services gateway API will be removed in a future release. You should plan over time to replace your existing filters with a combination of JAX-RPC handlers and service integration bus mediations. |
Application Services Features | |
Deprecation | Recommended Migration Action |
The following Java Database Connectivity (JDBC) drivers
are deprecated:
|
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 shipped with WebSphere Application Server, which is free for use with WebSphere Application Server. |
Installation and Migration Tools | |
Deprecation | Recommended Migration Action |
The Application Assembly Tool (AAT) 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. |
JDOM (a Java representation of an XML document that provides an API for efficient reading, manipulating and writing documentation) is deprecated. The currently packaged version of JDOM in WebSphere Application Server will not be packaged in future releases of WebSphere. | Go to JDOM and
get the latest copy of JDOM and bundle it inside your application. Note: Customers
running WebSphere Studio Application Developer Integration Edition Version
4.1 applications will need to migrate them to WebSphere Studio Application
Developer Integration Edition Version 5.0.
|
The C++ Object Request Broker (ORB), the C++ library
for IDL value types and the WebSphere Application Server C++ security client
are deprecated. 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 Java 2 Platform Enterprise Edition (J2EE) and WebSphere
Application Server environment. In addition to the preceding information, the CORBA C++ client feature will be removed from the Application Clients installation image in future releases. |
It is recommended that customers migrate to the
Object Request Broker (ORB) service for Java technology that ships with WebSphere
Application Server. However, there is no equivalent J2EE functionality for
the C++ security client or the C++ value-type library. Customers that require
such functionality must provide or develop their own. For information on the
ORB service for Java technology, see Managing Object Request Brokers. The deprecation of the CORBA C++ Developer Kit does
not affect support for CORBA interoperability with vendor software for CORBA
services. View the following links for additional information about interoperability:
|
IBM Cloudscape Version 5.1.x is deprecated. | Use the Cloudscape Network Server JDBC driver. |
Servers and Clustering Features | |
Deprecation | Recommended Migration Action |
IBM HTTP Server (IHS) Version 1.3.x is deprecated. | If you are using IHS Version 1.3.x with modules
that:
|
Application Programming Model and Container Support Features | |
Deprecation | Recommended Migration Action |
Bean Scripting Framework (BSF) JavaServer Pages (JSP) execution and debugging functionality is deprecated. | The functionality will need to be re-architected
if you are using the JavaScript, Tcl, and Python languages. If using BSF scripting
in your own custom applications, they will be unaffected. Custom scripts written
for the WebSphere Application Server administrative console will also be unaffected. This functionality will continue to exist in WebSphere Application Server Version 5.1 and succeeding releases until Version 6.0. If debugging JSP files, you might have to restart the application server during JavaScript debugging sessions. |
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. Note: You will not need to implement these
deprecated methods in their subclasses if you have the subclass of OracleDataStoreHelper
class. Those deprecated methods will not be called by the WebSphere Application
Server runtime.
|
Web container API modifications: Note: There are no declared
deprecations. The only changes are caused because of a Java API that changed
between 1.3 and 1.4.
The changed class is com.ibm.websphere.servlet.error.ServletErrorReport. The return signature for getStackTrace( ) is changed because java.lang.Throwable now defines the same method with a different return signature.
|
If you are using com.ibm.websphere.servlet.error.ServletErrorReport.getStackTrace( ) and expecting a return type of String, you need to change your application to use the replacement method. |
Application Services Features | |
Deprecation | Recommended Migration Action |
Data access binaries -- Common Connector Framework: The following JAR files are deprecated:
|
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 Data access from J2EE Connector Architecture applications. |
Setting the XA partner log directory using the TRANLOG_ROOT variable is deprecated. | The setting currently stored in the TRANLOG_ROOT variable (if any) will need to be added to the Transaction Service panel for all servers that need to use the XA partner log. If the default location is to be used, then no action is required. The Transaction Service panel can be found on the Administrative Console by selecting Application Servers on the left, choosing the application server to be modified, and selecting Transaction Service on the panel that is displayed. The directory currently in TRANLOG_ROOT should be entered in the Logging Directory box on the panel. |
Security Features | |
Deprecation | Recommended Migration Action |
The API is deprecated 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:
|
Security programming interface deprecations:
|
Use Java Authentication and Authorization Service (JAAS) for all authentication related functionality. |
System Administration Features | |
Deprecation | Recommended Migration Action |
The following class is deprecated: 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 driver when you are accessing data, you should now use the DB2UniversalDataStoreHelper class. |
Application Programming Model and Container Support Features | |
Deprecation | Recommended Migration Action |
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:
|
See Migrating Apache SOAP Web services to Web Services for J2EE standards for more information. |
Application Services Features | |
Deprecation | Recommended Migration 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.DataStoreHelper public int processSQL(java.lang.String.sqlString, int isolevel, boolean addForUpdate, boolean addextendedForUpdateSyntax); public DataStoreAdatperException mapException(DataStoreAdapterException e); com.ibm.websphere.rsadapter.GenericDataStoreHelper public int processSQL(java.lang.String.sqlString, int isolevel, boolean addForUpdate, boolean addextendedForUpdateSyntax); public DataStoreAdatperException mapException(DataStoreAdapterException e); com.ibm.websphere.rsadapter.WSCallHelper public static DataStoreHelper createDataStoreHelper(String dsClassName) |
These relational resource adapter deprecated methods
do not impact the application. Note: You will not need to implement these
deprecated methods in their subclasses if you have the subclass of GenericDataStoreHelper.
Those deprecated methods will not be called by the WebSphere Application Server
runtime.
For com.ibm.websphere.rsadapter.WSCallHelper, use the getDataStoreHelper(datasource) method to get a DataStoreHelper object. |
System Administration Features | |
Deprecation | Recommended Migration Action |
The testConnection command
in the AdminControl scripting object ($AdminControl TestConnection configId
props) is deprecated. Running this command in WebSphere Application Server,
Version 5.0.2 or later returns the following message: WASX7390E: Operation not supported - testConnection command with config id and properties arguments is not supported. Use testConnection command with config id argument only. |
As of WebSphere Application Server, Version 5.0.2 or later, the preferred way to test a data source connection is the testConnection command passing in the data source configuration ID as the only parameter. |
The getPropertiesForDataSource command
in the AdminControl scripting object ($AdminControl getPropertiesForDataSource
configId) is deprecated. This command incorrectly assumes the availability
of the configuration service when you run it in the connected mode. Running
this command in WebSphere Application Server, Version 5.0.2 or later returns
the following message: WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported. |
There is no replacement for this command. |
Application Services Features | |
Deprecation | Recommended Migration 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.DataStoreHelper public int processSQL(java.lang.String sqlString, int isolevel); com.ibm.websphere.rsadapter.GenericDataStoreHelper public int processSQL(java.lang.String sqlString, int isolevel); com.ibm.websphere.rsadapter.DB2390DataStoreHelper public int processSQL(java.lang.String sqlString, int isolevel); |
These relational resource adapter deprecated methods
do not impact the application. Note: You will not need to implement these
deprecated methods in their subclasses if you have the subclass of com.ibm.websphere.rsadapter.GenericDataStoreHelper.
Those deprecated methods will not be called by the WebSphere Application Server
runtime.
|
Application Services Features | |
Deprecation | Recommended Migration Action |
The following three methods from com.ibm.websphere.appprofile.accessintent.AccessIntent
are deprecated: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 | |
Performance Features | |
Deprecation | Recommended Migration Action |
Performance Monitoring Infrastructure -- Various Version
5.x public methods in:
|
These methods are replaced as follows:
|
The following table describes what is removed.
Component | Classes and interfaces |
---|---|
activity | com.ibm.ws.activity.ActivityConstants |
admin | com.ibm.websphere.management.application.EarUtils |
als | com.ibm.websphere.als.BufferManager |
anttasks | com.ibm.websphere.ant.tasks.endptEnabler.Property |
dynacache | com.ibm.websphere.servlet.cache.CacheConfig |
ras | com.ibm.ras.RASConsoleHandler |
security | com.ibm.websphere.security.AuthorizationTable |
userprofile | com.ibm.websphere.userprofile.UserProfile |
Scheduler API | com.ibm.websphere.scheduler.pmi.SchedulerPmiModule |
Scheduler API | com.ibm.websphere.scheduler.MessageTaskInfo.setJMSPriority() |
ObjectPool APIs | com/ibm/websphere/objectpool/pmi/ObjectPoolPerf.java |
Asynchronous Beans APIs | com/ibm/websphere/asynchbeans/pmi/AlarmManagerPerf.java |
Related tasks
Migrating and coexisting