Deprecated features of WAS traditional

If we are migrating the configuration from an earlier release of WebSphere Application Server, we should be aware of the various features that were deprecated in this and earlier releases.

WAS uses the following naming scheme:

V.R.M.F

where

• V = version
• R = release
• M = modification
• F = fix pack

For example, 9.0.0.1 refers to version 9, release 0, modification 0, and fix-pack 1. It is also common to use "version" to prefix a particular release, modification, or fix pack-"version 9.0" when referring to a release, for example, or "version 9.0.0.1" when referring to a fix pack.

If a feature is listed here as deprecated, IBM might remove this capability in a subsequent release of the product. Future investment will be focused on the strategic function listed under Recommended Migration Actions. Typically, a feature is not deprecated unless an equivalent alternative is provided. A feature is not removed until at least two major releases or three full years, whichever time period is longer, from the release in which that feature is deprecated. Looking at a sequence of releases including 6.0, 6.1, and 7.0, for example, features deprecated in release 6.0 first become eligible for removal in 7.0. In rare cases, it might become necessary to remove features sooner; such cases are indicated clearly and explicitly in the descriptions of these removed features.

The following tables summarize deprecated features by version and release. The tables indicate what is deprecated-such as 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 v9.0
• Features deprecated in v8.5.5
• Features deprecated in v8.5
• Features deprecated in v8.0.0.1
• Features deprecated in v8.0
• Features deprecated in v7.0
• Features deprecated in v6.1
• Features deprecated in v6.0.2

• Features deprecated in v6.0.1
• 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 v9.0

Category	Deprecation	Recommended Migration Action
Application programming model and container	The following optional Java Platform, Enterprise Edition (Java EE) 7 technologies: EJB entity beans Important: Only the entity bean portion of the EJB specification is deprecated. JAX-RPC 1.1 The following optional Java EE 7 technologies continue to be deprecated: Java API for XML Registries (JAXR) 1.0 Java EE Application Deployment 1.2	EJB entity beans: Use the Java Persistence API (JPA) for new database and other persistence-related operations. JAX-RPC 1.1: Use JAX-WS or Java API for RESTful Web Services (JAX-RS). The focus to ensure interoperability for the subset of capabilities that map to the JAX-RPC and JAX-WS intersection will be maintained, but all new enhancements related to updating to support new standards are only in the JAX-WS runtime. JAXR 1.0: Use UDDI Version 3. Java EE Application Deployment 1.2: Use another way to deploy applications to the server, such as wsadmin scripting and JMX MBeans. The closest method to using the Java EE Deployment API is to use WebSphere JMX MBeans. See Ways to install enterprise applications or modules.
	The following asynchronous programming models: Asynchronous beans CommonJ timer and work manager	Use Concurrency Utilities for Java EE (JSR 236). Concurrency Utilities for Java EE provides a standardized approach for performing concurrent operations in an application server. For information about how to migrate from asynchronous beans and CommonJ, see Examples to migrate to EE Concurrency from Asynchronous beans and CommonJ.
	OSGi applications OSGi application support in WAS traditional is deprecated because OSGi applications depend on a technology that is no longer included in Equinox 4.4.0 and later.	There is no strategic alternative in WAS traditional. To continue to use OSGi applications, migrate the applications to Liberty. In Liberty, OSGi applications run as Subsystems, which are a standard form of OSGi application.
Balancing workloads	Backup clusters	Instead of using IIOP-based Backup clusters across multiple cells using core group bridges, we should consider wrapping EJB capabilities with REST interfaces . Then use front-end load balancing, such as on demand router, to balance the load.
Databases	WAS Version 4.0 data sources	Use the data sources for WAS v5.0 and later. These data sources are based on a standard JCA architecture. Settings for these data sources are described in Data source collection. The deprecated Version 4.0 data sources are based on a single connection manager (CM) architecture. Settings for these data sources are described in Data source (WAS V4) collection (deprecated). For more information about the differences between these data sources, see Data sources.
	WAS Version 4.0 datasource Bean	Use the DataSource Mbean. See DataSource MBean
Intelligent Management	Assisted and Complete Lifecycle servers	Migrate WebSphere Liberty servers to a Liberty Management Servers Collective configuration. There is no recommended migration action for other server types.
Intermediary services	DMZ Secure Proxy Server	If we use the proxy server as a front end to WAS, use IBM HTTP Server and the WebSphere Web Server Plug-ins, on demand router, or IBM DataPower appliances. If we use the proxy server separately from WAS, use IBM HTTP Server and the WebSphere Web Server Plug-in with Intelligent Management, on demand router, or IBM DataPower. For more information about intermediary services, see Select a front end for our WAS topology.
Migration	migrateConfigTo85.py script for migrating Compute Grid or Feature Pack for odern Batch to WAS v8.5	In WAS v9.0, Compute Grid and Feature Pack for Modern Batch are migrated as part of the standard migration processes, so you no longer need to run a separate script. See Migrate, coexist, and interoperate.
System administration	Jython 2.1	Migrate to Jython 2.7
System administration	wsadmin scripting with Jacl	Use the Jython language to create wsadmin scripts. For more information, see Use wsadmin scripting with Jython.
(iSeries) System administration	(iSeries) updwashost command	(iSeries) Use the AdminTask object changeHostName command to change the host name of a node. See Utility command group of the AdminTask object.
System administration	IBM Support Assistant (ISA) Data Collector tool that gathers information from our WAS environment for IBM Software Support.	Use the Collector tool (collector.bat or collector.sh). See Collector tool.
Web server plug-in configuration	Topology-centric, or global, plug-in configuration	Use application-centric plug-in configuration. An application-centric plugin-cfg.xmlconfiguration file has an application that is mapped to both web server and application server definitions. See Implement a web server plug-in.
Service integration bus	Interoperation through IBM MQ server For more details, see Interoperation using an IBM MQ server.	Use the IBM MQ resource adapters or IBM MQ link to connect to the IBM MQ network for interoperation. See Interoperation using the IBM MQ messaging provider and Use IBM MQ links to connect a bus to an IBM MQ network.

Features deprecated in v8.5.5

Category	Deprecation	Recommended Migration Action
Application assembly and deployment	IBM Assembly and Deploy Tools for WebSphere Administration	For programming models that use Java EE 5 and later, use the IBM WebSphere Developer Tools. To modify the bindings and extensions deployment descriptors for Java EE programming models prior to Java EE 5, use the WebSphere administrative console when we install your application. See Install enterprise application files with the console. To generate deployment code for Enterprise JavaBean (EJB) 2.x, use the ejbdeploy command or choose to deploy enterprise beans when we install the application. There are no replacements for the editors for the ibm-webservices-bnd.xml and Programming Model Extensions deployment descriptors.
Edge components	WebSphere Edge Components Load Balancer for IPv4 Features not available in the Load Balancer for IPv4 and IPv6 were deprecated as of v6.1 and then stabilized. See Stabilized features.	Migrate to WebSphere Edge Components Load Balancer for IPv4 and IPv6.
(ZOS) Edge components	(ZOS) DMZ Secure Proxy Server for IBM WAS for z/OS This feature was removed in v9.0.	(ZOS) If we use the proxy server as a front end to WAS, use IBM HTTP Server and the WebSphere Web Server Plug-ins, which are included with the product at no additional charge. For additional capability, consider using IBM DataPower appliances. If we use the proxy server separately from WAS, basic HTTP proxy functionality is available with the HTTP servers bundled with z/OS: V2R2 and later: IBM HTTP Server (powered by Apache) V2R1 and earlier: IBM HTTP Server for z/OS V5R3 (DGW) For additional capability, consider using IBM DataPower appliances.
IBM HTTP Server	Certificate Revocation List (CRL) protocol support	Use Online Certificate Status Protocol (OCSP) with TLS certificates. In IBM HTTP Server, CRL support is enabled with the SSLCRLHostname and SSLCRLUserid directives. CRL support is also controlled by the CRLDistributionPoint extension in TLS certificates. TLS specifications now favor OCSP, which is enabled with the SSLOCSPEnable and SSLOCSPResponderURL directives. In TLS certificates, OCSP support is controlled by the AuthorityInformationAccess extension. See SSL certificate revocation list and Online Certificate Status Protocol.
Web 2.0 and Mobile Toolkit	Dojo Toolkit, including Dojo Diagrammer	Dojo desktop and mobile applications will continue to function but are no longer supported. We can continue to develop Dojo applications using the open source Dojo Toolkit.
	Web Messaging service	Migrate applications that use the Web Messaging service to use Servlet 3.0 asynchronous servlets or the WebSocket protocol. See Developing servlets with extensions.
	Ajax Proxy	Migrate the Ajax Proxy applications to use cross-origin resource sharing (CORS) for cross-domain requests.
	Support for the following server-side services: RPC Adapter Analytics Graphics	Rearchitect the applications to use Java API for RESTful Web Services (JAX-RS). When we migrate the graphics service, we can use the open source Apache Batik project to convert images.
	Support for the following application services: Optimizer WebDAV extension Map Conversion Dojo Diagrammer	There is no recommended migration action.

Features deprecated in v8.5

Category	Deprecation	Recommended Migration Action
Application services	The com.ibm.websphere.management.application.client.EnvEntry_processAnnotations property	Use the com.ibm.websphere.management.application.client.EnvEntry_processBindings property
	The DOJO widgets associated with the Communications Enabled Applications (CEA) feature	Use the CEA DOJO 1.5 widget source and description available from the publicly accessible developerWorks article at Developing WAS Communication Enabled Application (CEA) widgets.
	All APIs related to the Common Event Infrastructure (CEI) module The following files are used by the CEI module and are deprecated: Files in app_server_root/bin/: eventbucket.sh/eventbucket.bat eventcatalog.sh/eventcatalog.bat eventemit.sh/eventemit.bat eventpurge.sh/eventpurge.bat eventpurgepool.sh/eventpurgepool.bat eventquery.sh/eventquery.bat Files in app_server_root/systemApps/: EventService.ear/META-INF EventService.ear/DataStoreEjb.jar EventService.ear/EventCatalogEjb.jar EventService.ear/EventServerEjb.jar EventService.ear/EventServerMdb.jar Files in app_server_root/plugins/: com.ibm.events.client.jar com.ibm.events.service.jar File in app_server_root/features/: com.ibm.events.service_6.1.0.0 Files in app_server_root/properties/schemas/: cei.xsd ceiservice.xs Files in app_server_root/util/event/: ceiconfigreload.jacl eventbucket.jacl eventcatalog.jacl eventemit.jacl eventpurge.jacl eventpurgepool.jacl eventquery.jacl Files in app_server_root/web/configDocs/packages/cei/: classes-frame.html DataStoreProfile.html DistributionQueue.html EmitterFactoryProfile.html EventBusTransmissionProfile.html EventGroupProfile.html EventGroupProfileList.html EventInfrastructureProvider.html EventServerProfile.html FilterFactoryProfile.html JMSTransmissionProfile.html	For new applications that require event-based models, use Service Integration Bus (SIBus). Design new applications using SIBus-provided APIs for sending and receiving events.
	The com.ibm.portal.* packages: com.ibm.portal com.ibm.portal.dynamicui com.ibm.portal.help com.ibm.portal.jndi com.ibm.portal.portlet.service com.ibm.portal.propertybroker.property com.ibm.portal.propertybroker.service com.ibm.portal.state com.ibm.portal.state.exceptions	There is no recommended migration action.
	The revokeSSOCookies(HttpServletRequest, HttpServletResponse) method from the WSSecurityHelper class This method is not supported in the Liberty profile.	Use the functionality provided by the Java Servlet-3.0 logout() method. Read Servlet security methods.
	The getLTPACookieFromSSOToken() method from the WSSecurityHelper class This method is not supported in the Liberty profile.	Use the functionality provided by the getSSOCookieFromSSOToken() method from the WebSecurityHelper class.
Application assembly and deployment	Communucations Enabled Applications	There is no alternative to CEA. If we are deploying the application on Liberty, consider using the Rtcomm feature which provides a set of real-time communications tools. See WebRTC Application Development with Rtcomm.
Edge components	Wide-Area Network Dispatcher (WAND) feature provided by WebSphere Edge Components Load Balancer for IPv4	Use the Network address translation (NAT) forwarding method on IPv4, or use the Media Access Control (MAC) encapsulation forwarding method on IPv6.
	The following two components of WebSphere Edge Components Load Balancer for IPv4 that work in conjunction with these vendors' switches to provide Simple Network Management Protocol (SNMP) statistics on server availability: Cisco Consultant (CCO) Nortel-Alteon Consultant (NAL)	Use an IBM Load Balancer.
	WebSphere Edge Components Load Balancer for IPv4 support for the token-ring interface	Use an Ethernet interface.
System administration	Intelligent Management support for the following assisted lifecycle middleware server types: Apache Tomcat BEA WebLogic JBoss External WebSphere application server (application servers that run outside the Intelligent Management cell) This support was undeprecated and stabilized in v8.5.5.	Use wsadmin scripting to manage these middleware server resources.
	The defaultXD and defaultXDZOS server templates used when creating a dynamic cluster	Use the default or defaultZOS server template.
	(Dist) (ZOS) Support for WebSphere Virtual Enterprise v7.x and earlier nodes	(Dist) (ZOS) Migrate the nodes to WebSphere Application Server Network Deployment. Read Migrate, coexist, and interoperate.

Features deprecated in v8.0.0.1

Category	Deprecation	Recommended Migration Action
System administration	Support for the following software, which reached end of life: Sybase Adaptive Server Enterprise (ASE) 12.5.X Sybase jConnect 5.5	Move to the following: Sybase Adaptive Server Enterprise (ASE) 15.X Sybase jConnect 6.05 or jConnect 7.0

Features deprecated in v8.0

(ZOS)

Category	Deprecation	Recommended Migration Action
Application programming model	The JavaServer Faces (JSF) 1.2 Sun Reference Implementation (RI) This feature was removed in v9.0.	Use the JSF 2.0 MyFaces implementation, which is the default implementation for WAS Version 8.0. For information about how to migrate to the JSF 2.0 MyFaces implementation, see JavaServer Faces migration and the Migrate JavaServer Faces 1.x applications to JavaServer Faces 2.0 topic on IBM developerWorks.
Application services	The following historyInfo utility command-line arguments: -components -maintenancePackageID	Be aware of the following when using the historyInfo utility: -component Do not use this argument. It now performs no action. -maintenancePackageID This argument now performs an action that is equivalent to -offeringID. Use -offeringID.
	The following versionInfo utility command-line arguments: -componentDetail -components -maintenancePackageDetail -maintenancePackages	Be aware of the following when using the versionInfo utility: -componentDetail Do not use this argument. It now performs no action. -components Do not use this argument. It now performs no action. -maintenancePackageDetail This argument now performs an action that is equivalent to -fixpackDetail plus -ifixDetail. Use -fixpackDetail and -ifixDetail. -maintenancePackages This argument now performs an action that is equivalent to -fixpacks plus -ifixes. Use -fixpacks and -ifixes.
	The following methods in the com.ibm.websphere.product.WASDirectory class: public WASComponent getInstalledComponentByName(String componentName) public WASComponent[] getInstalledComponentList() public boolean isComponentInstalled(String componentName) public WASMaintenancePackage[] getHistoryMaintenancePackageList() public WASMaintenancePackage getInstalledMaintenancePackageByID(String mpID) public WASMaintenancePackage[] getInstalledMaintenancePackageList() public boolean isMaintenancePackageInstalled(String ID)	Do not use these methods. public WASComponent getInstalledComponentByName(String componentName) This method now returns a null object. public WASComponent[] getInstalledComponentList() This method now returns an empty list. public boolean isComponentInstalled(String componentName) This method now returns as false. public WASMaintenancePackage[] getHistoryMaintenancePackageList() This method is replaced by public IMEvent[] getHistoryEventList(). public WASMaintenancePackage getInstalledMaintenancePackageByID(String mpID) This method is replaced by public IMOffering getInstalledOfferingByID(String productID). public WASMaintenancePackage[] getInstalledMaintenancePackageList() This method is replaced by public IMOffering[] getInstalledOfferingList(). public boolean isMaintenancePackageInstalled(String ID) This method is replaced by public boolean isThisProductInstalled(String id).
Application services	The following classes under the com.ibm.websphere.product.* package: com.ibm.websphere.product.metadata.WASComponent com.ibm.websphere.product.metadata.WASComponentUpdate com.ibm.websphere.product.metadata.WASMaintenancePackage com.ibm.websphere.product.WASProductException com.ibm.websphere.product.history.WASHistoryException com.ibm.websphere.product.WASProduct. com.ibm.websphere.product.history.WASHistory	Use the following guidelines: com.ibm.websphere.product.metadata.WASComponent Do not use this class. All public methods in this class now return either null objects or empty lists. com.ibm.websphere.product.metadata.WASComponentUpdate Do not use this class. All public methods in this class now return either null objects or empty lists. com.ibm.websphere.product.metadata.WASMaintenancePackage Do not use this class. com.ibm.websphere.product.WASProductException Do not use this class. Use the com.ibm.websphere.product.WASDirectoryException class. com.ibm.websphere.product.history.WASHistoryException Do not use this class. Use the com.ibm.websphere.product.WASDirectoryException class. com.ibm.websphere.product.WASProduct. Do not use this class. Use the com.ibm.websphere.product.WASDirectory class. com.ibm.websphere.product.history.WASHistory Do not use this class. Use the com.ibm.websphere.product.WASDirectory class.
	The following constants under the com.ibm.websphere.product.WASDirectory class: ID_BASE ID_EXPRESS ID_ND The following constants under the com.ibm.websphere.product.WASDirectory and com.ibm.websphere.product.utils.WASDirectoryHelper classes: ID_PME ID_WBI ID_JDK ID_EMBEDDED_EXPRESS ID_XD ID_CLIENT ID_PLG ID_IHS ID_WXD ID_NDDMZ ID_UPDI	WASDirectory interfaces are independent of product IDs and treat them as a string. Any product-specific callers should specify product IDs by themselves.
	Support for Java API for XML Registries (JAXR)	Use UDDI Version 3.
Security	com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus Security Access Manager (TAM) trust association interceptor (TAI) interface	Get the latest version of Tivoli code from the ISAM Trust Association Interceptor Plus website.
System administration	createServerType command in the ServerManagement command group for the AdminTask object	Do not create new server types.
	The following commands in the ManagedNodeGroup . createManagedNodeGroup deleteManagedNodeGroup addMemberToManagedNodeGroup deleteMemberFromManagedNodeGroup queryManagedNodeGroups getManagedNodeGroupMembers getManagedNodeGroupInfo modifyManagedNodeGroupInfo The following commands in the JobManagerNode . cleanupManagedNode queryManagedNodes getManagedNodeProperties modifyManagedNodeProperties getManagedNodeKeys	Use the following commands in the TargetGroup command group for the AdminTask object: createTargetGroup deleteTargetGroup addMemberToTargetGroup deleteMemberFromTargetGroup queryTargetGroups getTargetGroupMembers getTargetGroupInfo modifyTargetGroupInfo Use the following commands in the JobManagerNode . cleanupTarget queryTargets getTargetProperties modifyTargetProperties getTargetKeys
	Service log, commonly named activity.log	Using one of the following to access log content: SystemOut.log file when the system is configured to use basic log and trace mode HPEL logViewer command when the system is configured to use HPEL log and trace mode Configure servers to use HPEL to merge log file content from multiple servers. Use the HPEL log and trace mode and use the HPEL logViewer command if we need to be able to render log content in Common Base Event XML format.
	Support for deploying Java Platform, Enterprise Edition (Java EE) modules or applications on an application server using the Java EE Application Deployment API specification JSR-88	Use any of a number of other options to deploy applications to the server, including wsadmin scripting and JMX MBeans. The closest method to using the Java EE Deployment API would be using WebSphere JMX MBeans. Read Ways to install enterprise applications or modules for more information.
	DataPower appliance manager	We can continue to use the DataPower appliance manager to manage existing supported DataPower appliances until it is removed from the product or until the appliances are out of service. In WebSphere Application Server v8.0, the following appliances are supported: 9001 9002 9003/7993 9004/9235 - XS40, XI50, XB60, XM70 9004/9235 - XA35, XM70FC The end-of-service dates for the appliances are documented in IBM WebSphere DataPower SOA Appliances End of Service dates. New appliances not on the previous list are managed through a separate DataPower appliance management offering that is also capable of managing existing appliances.
Tivoli Performance Viewer	Use of the Scalable Vector Graphics (SVG) format by the Tivoli Performance Viewer to plot graphs	No action is required. The Tivoli Performance Viewer now uses the Dojo format to plot graphs. To go back to the earlier style of graph, which supports SVG and image formats, set the com.ibm.websphere.tpv.DojoGraph JVM system property to false.

(Dist)

Category	Deprecation	Recommended Migration Action
Application programming model	The JavaServer Faces (JSF) 1.2 Sun Reference Implementation (RI) This feature was removed in v9.0.	Use the JSF 2.0 MyFaces implementation, which is the default implementation for WAS Version 8.0. For information about how to migrate to the JSF 2.0 MyFaces implementation, see JavaServer Faces migration and the Migrate JavaServer Faces 1.x applications to JavaServer Faces 2.0 topic on IBM developerWorks.
Application services	The following historyInfo utility command-line arguments: -components -maintenancePackageID	Be aware of the following when using the historyInfo utility: -component Do not use this argument. It now performs no action. -maintenancePackageID This argument now performs an action that is equivalent to -offeringID. Use -offeringID.
	The following versionInfo utility command-line arguments: -componentDetail -components -maintenancePackageDetail -maintenancePackages	Be aware of the following when using the versionInfo utility: -componentDetail Do not use this argument. It now performs no action. -components Do not use this argument. It now performs no action. -maintenancePackageDetail This argument now performs an action that is equivalent to -fixpackDetail plus -ifixDetail. Use -fixpackDetail and -ifixDetail. -maintenancePackages This argument now performs an action that is equivalent to -fixpacks plus -ifixes. Use -fixpacks and -ifixes.
	The following methods in the com.ibm.websphere.product.WASDirectory class: public WASComponent getInstalledComponentByName(String componentName) public WASComponent[] getInstalledComponentList() public boolean isComponentInstalled(String componentName) public WASMaintenancePackage[] getHistoryMaintenancePackageList() public WASMaintenancePackage getInstalledMaintenancePackageByID(String mpID) public WASMaintenancePackage[] getInstalledMaintenancePackageList() public boolean isMaintenancePackageInstalled(String ID)	Do not use these methods. public WASComponent getInstalledComponentByName(String componentName) This method now returns a null object. public WASComponent[] getInstalledComponentList() This method now returns an empty list. public boolean isComponentInstalled(String componentName) This method now returns as false. public WASMaintenancePackage[] getHistoryMaintenancePackageList() This method is replaced by public IMEvent[] getHistoryEventList(). public WASMaintenancePackage getInstalledMaintenancePackageByID(String mpID) This method is replaced by public IMOffering getInstalledOfferingByID(String productID). public WASMaintenancePackage[] getInstalledMaintenancePackageList() This method is replaced by public IMOffering[] getInstalledOfferingList(). public boolean isMaintenancePackageInstalled(String ID) This method is replaced by public boolean isThisProductInstalled(String id).
Application services	The following classes under the com.ibm.websphere.product.* package: com.ibm.websphere.product.metadata.WASComponent com.ibm.websphere.product.metadata.WASComponentUpdate com.ibm.websphere.product.metadata.WASMaintenancePackage com.ibm.websphere.product.WASProductException com.ibm.websphere.product.history.WASHistoryException com.ibm.websphere.product.WASProduct. com.ibm.websphere.product.history.WASHistory	Use the following guidelines: com.ibm.websphere.product.metadata.WASComponent Do not use this class. All public methods in this class now return either null objects or empty lists. com.ibm.websphere.product.metadata.WASComponentUpdate Do not use this class. All public methods in this class now return either null objects or empty lists. com.ibm.websphere.product.metadata.WASMaintenancePackage Do not use this class. com.ibm.websphere.product.WASProductException Do not use this class. Use the com.ibm.websphere.product.WASDirectoryException class. com.ibm.websphere.product.history.WASHistoryException Do not use this class. Use the com.ibm.websphere.product.WASDirectoryException class. com.ibm.websphere.product.WASProduct. Do not use this class. Use the com.ibm.websphere.product.WASDirectory class. com.ibm.websphere.product.history.WASHistory Do not use this class. Use the com.ibm.websphere.product.WASDirectory class.
	The following constants under the com.ibm.websphere.product.WASDirectory class: ID_BASE ID_EXPRESS ID_ND The following constants under the com.ibm.websphere.product.WASDirectory and com.ibm.websphere.product.utils.WASDirectoryHelper classes: ID_PME ID_WBI ID_JDK ID_EMBEDDED_EXPRESS ID_XD ID_CLIENT ID_PLG ID_IHS ID_WXD ID_NDDMZ ID_UPDI	WASDirectory interfaces are independent of product IDs and treat them as a string. Any product-specific callers should specify product IDs by themselves.
	Support for Java API for XML Registries (JAXR)	Use UDDI Version 3.
Security	com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus ISAM (TAM) trust association interceptor (TAI) interface	Get the latest version of Tivoli code from the ISAM Trust Association Interceptor Plus website.
System administration	createServerType command in the ServerManagement command group for the AdminTask object	Do not create new server types.
	The following commands in the ManagedNodeGroup . createManagedNodeGroup deleteManagedNodeGroup addMemberToManagedNodeGroup deleteMemberFromManagedNodeGroup queryManagedNodeGroups getManagedNodeGroupMembers getManagedNodeGroupInfo modifyManagedNodeGroupInfo The following commands in the JobManagerNode . cleanupManagedNode queryManagedNodes getManagedNodeProperties modifyManagedNodeProperties getManagedNodeKeys	Use the following commands in the TargetGroup command group for the AdminTask object: createTargetGroup deleteTargetGroup addMemberToTargetGroup deleteMemberFromTargetGroup queryTargetGroups getTargetGroupMembers getTargetGroupInfo modifyTargetGroupInfo Use the following commands in the JobManagerNode . cleanupTarget queryTargets getTargetProperties modifyTargetProperties getTargetKeys
	The following commands used to launch the Profile Management Tool: (UNIX) app_server_root/bin/ProfileManagement/pmt.sh (Windows) app_server_root\bin\ProfileManagement\pmt.bat The following commands used to launch the Migration Management Tool: (UNIX) app_server_root/bin/migration.sh (Windows) app_server_root\bin\migration.bat	Use the following commands to launch the WebSphere Customization Toolbox: (UNIX) profile_root/bin/wct.sh (Windows) profile_root\bin\wct.bat Use the following commands to launch the Profile Management Tool (z/OS only) contained in the WebSphere Customization Toolbox: (UNIX) profile_root/bin/wct.sh -perspective com.ibm.ws.pmt.views.standalone.perspectives.standAlonePerspective (Windows) profile_root\bin\wct.bat -perspective com.ibm.ws.pmt.views.standalone.perspectives.standAlonePerspective Use the following commands to launch the Migration Management Tool contained in the WebSphere Customization Toolbox: (UNIX) profile_root/bin/wct.sh -perspective com.ibm.ws.mmt.perspective (Windows) profile_root\bin\wct.bat -perspective com.ibm.ws.mmt.perspective
	Service log, commonly named activity.log	Using one of the following to access log content: SystemOut.log file when the system is configured to use basic log and trace mode High Performance Extensible Logging (HPEL) logViewer command when the system is configured to use HPEL log and trace mode Configure the servers to use HPEL log and trace mode and use the HPEL API if we need to be able to merge log file content from multiple servers. Use the HPEL log and trace mode and use the HPEL logViewer command if we need to be able to render log content in Common Base Event XML format.
	Support for deploying Java Platform, Enterprise Edition (Java EE) modules or applications on an application server using the Java EE Application Deployment API specification JSR-88	Use any of a number of other options to deploy applications to the server, including wsadmin scripting and JMX MBeans. The closest method to using the Java EE Deployment API would be using WebSphere JMX MBeans. Read Ways to install enterprise applications or modules for more information.
	DataPower appliance manager	We can continue to use the DataPower appliance manager to manage existing supported DataPower appliances until it is removed from the product or until the appliances are out of service. In WebSphere Application Server v8.0, the following appliances are supported: 9001 9002 9003/7993 9004/9235 - XS40, XI50, XB60, XM70 9004/9235 - XA35, XM70FC The end-of-service dates for the appliances are documented in IBM WebSphere DataPower SOA Appliances End of Service dates. New appliances not on the previous list are managed through a separate DataPower appliance management offering that is also capable of managing existing appliances.
Tivoli Performance Viewer	Use of the Scalable Vector Graphics (SVG) format by the Tivoli Performance Viewer to plot graphs	No action is required. The Tivoli Performance Viewer now uses the Dojo format to plot graphs. To go back to the earlier style of graph, which supports SVG and image formats, set the com.ibm.websphere.tpv.DojoGraph JVM system property to false.

(iSeries)

Category	Deprecation	Recommended Migration Action
Application programming model	The JavaServer Faces (JSF) 1.2 Sun Reference Implementation (RI) This feature was removed in v9.0.	Use the JSF 2.0 MyFaces implementation, which is the default implementation for WAS Version 8.0. For information about how to migrate to the JSF 2.0 MyFaces implementation, see JavaServer Faces migration and the Migrate JavaServer Faces 1.x applications to JavaServer Faces 2.0 topic on IBM developerWorks.
Application services	The following historyInfo utility command-line arguments: -components -maintenancePackageID	Be aware of the following when using the historyInfo utility: -component Do not use this argument. It now performs no action. -maintenancePackageID This argument now performs an action that is equivalent to -offeringID. Use -offeringID.
	The following versionInfo utility command-line arguments: -componentDetail -components -maintenancePackageDetail -maintenancePackages	Be aware of the following when using the versionInfo utility: -componentDetail Do not use this argument. It now performs no action. -components Do not use this argument. It now performs no action. -maintenancePackageDetail This argument now performs an action that is equivalent to -fixpackDetail plus -ifixDetail. Use -fixpackDetail and -ifixDetail. -maintenancePackages This argument now performs an action that is equivalent to -fixpacks plus -ifixes. Use -fixpacks and -ifixes.
	The following methods in the com.ibm.websphere.product.WASDirectory class: public WASComponent getInstalledComponentByName(String componentName) public WASComponent[] getInstalledComponentList() public boolean isComponentInstalled(String componentName) public WASMaintenancePackage[] getHistoryMaintenancePackageList() public WASMaintenancePackage getInstalledMaintenancePackageByID(String mpID) public WASMaintenancePackage[] getInstalledMaintenancePackageList() public boolean isMaintenancePackageInstalled(String ID)	Do not use these methods. public WASComponent getInstalledComponentByName(String componentName) This method now returns a null object. public WASComponent[] getInstalledComponentList() This method now returns an empty list. public boolean isComponentInstalled(String componentName) This method now returns as false. public WASMaintenancePackage[] getHistoryMaintenancePackageList() This method is replaced by public IMEvent[] getHistoryEventList(). public WASMaintenancePackage getInstalledMaintenancePackageByID(String mpID) This method is replaced by public IMOffering getInstalledOfferingByID(String productID). public WASMaintenancePackage[] getInstalledMaintenancePackageList() This method is replaced by public IMOffering[] getInstalledOfferingList(). public boolean isMaintenancePackageInstalled(String ID) This method is replaced by public boolean isThisProductInstalled(String id).
Application services	The following classes under the com.ibm.websphere.product.* package: com.ibm.websphere.product.metadata.WASComponent com.ibm.websphere.product.metadata.WASComponentUpdate com.ibm.websphere.product.metadata.WASMaintenancePackage com.ibm.websphere.product.WASProductException com.ibm.websphere.product.history.WASHistoryException com.ibm.websphere.product.WASProduct. com.ibm.websphere.product.history.WASHistory	Use the following guidelines: com.ibm.websphere.product.metadata.WASComponent Do not use this class. All public methods in this class now return either null objects or empty lists. com.ibm.websphere.product.metadata.WASComponentUpdate Do not use this class. All public methods in this class now return either null objects or empty lists. com.ibm.websphere.product.metadata.WASMaintenancePackage Do not use this class. com.ibm.websphere.product.WASProductException Do not use this class. Use the com.ibm.websphere.product.WASDirectoryException class. com.ibm.websphere.product.history.WASHistoryException Do not use this class. Use the com.ibm.websphere.product.WASDirectoryException class. com.ibm.websphere.product.WASProduct. Do not use this class. Use the com.ibm.websphere.product.WASDirectory class. com.ibm.websphere.product.history.WASHistory Do not use this class. Use the com.ibm.websphere.product.WASDirectory class.
	The following constants under the com.ibm.websphere.product.WASDirectory class: ID_BASE ID_EXPRESS ID_ND The following constants under the com.ibm.websphere.product.WASDirectory and com.ibm.websphere.product.utils.WASDirectoryHelper classes: ID_PME ID_WBI ID_JDK ID_EMBEDDED_EXPRESS ID_XD ID_CLIENT ID_PLG ID_IHS ID_WXD ID_NDDMZ ID_UPDI	WASDirectory interfaces are independent of product IDs and treat them as a string. Any product-specific callers should specify product IDs by themselves.
	Support for Java API for XML Registries (JAXR)	Use UDDI Version 3.
Security	com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus ISAM (TAM) trust association interceptor (TAI) interface	Get the latest version of Tivoli code from the ISAM Trust Association Interceptor Plus website.
System administration	enableJvm command	Use the managesdk command.
	createServerType command in the ServerManagement command group for the AdminTask object	Do not create new server types.
	The following commands in the ManagedNodeGroup . createManagedNodeGroup deleteManagedNodeGroup addMemberToManagedNodeGroup deleteMemberFromManagedNodeGroup queryManagedNodeGroups getManagedNodeGroupMembers getManagedNodeGroupInfo modifyManagedNodeGroupInfo The following commands in the JobManagerNode . cleanupManagedNode queryManagedNodes getManagedNodeProperties modifyManagedNodeProperties getManagedNodeKeys	Use the following commands in the TargetGroup command group for the AdminTask object: createTargetGroup deleteTargetGroup addMemberToTargetGroup deleteMemberFromTargetGroup queryTargetGroups getTargetGroupMembers getTargetGroupInfo modifyTargetGroupInfo Use the following commands in the JobManagerNode . cleanupTarget queryTargets getTargetProperties modifyTargetProperties getTargetKeys
	Service log, commonly named activity.log	Using one of the following to access log content: SystemOut.log file when the system is configured to use basic log and trace mode High Performance Extensible Logging (HPEL) logViewer command when the system is configured to use HPEL log and trace mode Configure the servers to use HPEL log and trace mode and use the HPEL API if we need to be able to merge log file content from multiple servers. Use the HPEL log and trace mode and use the HPEL logViewer command if we need to be able to render log content in Common Base Event XML format.
	Support for deploying Java Platform, Enterprise Edition (Java EE) modules or applications on an application server using the Java EE Application Deployment API specification JSR-88	Use any of a number of other options to deploy applications to the server, including wsadmin scripting and JMX MBeans. The closest method to using the Java EE Deployment API would be using WebSphere JMX MBeans. Read Ways to install enterprise applications or modules for more information.
	DataPower appliance manager	We can continue to use the DataPower appliance manager to manage existing supported DataPower appliances until it is removed from the product or until the appliances are out of service. In WebSphere Application Server v8.0, the following appliances are supported: 9001 9002 9003/7993 9004/9235 - XS40, XI50, XB60, XM70 9004/9235 - XA35, XM70FC The end-of-service dates for the appliances are documented in IBM WebSphere DataPower SOA Appliances End of Service dates. New appliances not on the previous list are managed through a separate DataPower appliance management offering that is also capable of managing existing appliances.
Tivoli Performance Viewer	Use of the Scalable Vector Graphics (SVG) format by the Tivoli Performance Viewer to plot graphs	No action is required. The Tivoli Performance Viewer now uses the Dojo format to plot graphs. To go back to the earlier style of graph, which supports SVG and image formats, set the com.ibm.websphere.tpv.DojoGraph JVM system property to false.

Features deprecated in v7.0

(ZOS)

Category	Deprecation	Recommended Migration Action
Application programming model	registerSynchronizationCallbackForCurrentTran method in the com.ibm.websphere.jtaextensions.ExtendedJTATransaction interface	Use the registerInterposedSynchronization method of the TransactionSynchronizationRegistry interface instead. For more information, read JTA support.
	com.ibm.ws.extensionhelper.TransactionControl interface	Use the com.ibm.wsspi.uow.UOWManager interface instead. For more information, read JTA support.
	HttpServletRequestProxy class in the com.ibm.websphere.servlet.request package	Use the HttpServletRequestWrapper class instead of the HttpServletRequestProxy class. Use the subclasses of this class to overload or enhance the functionality of a server-provided HttpServletRequest.
	HttpServletResponseProxy class in the com.ibm.websphere.servlet.response package	Use the HttpServletResponseWrapper class instead of the HttpServletResponseProxy class. Use the subclasses of this class to overload or enhance the functionality of a server-provided HttpServletResponse.
	The following classes, interfaces, methods, and fields of the WebSphere relational resource adapter: Classes: com.ibm.websphere.rsadapter.JdbcAccessorImpl com.ibm.websphere.rsadapter.OracleDataStoreHelper Interfaces: com.ibm.websphere.rsadapter.Beginnable com.ibm.websphere.rsadapter.HandleStates com.ibm.websphere.rsadapter.Reassociateable com.ibm.websphere.rsadapter.WSNativeConnectionAccessor Methods: com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn) com.ibm.websphere.rsadapter.WSCallHelper.call com.ibm.websphere.rsadapter.WSConnection.getClientInformation com.ibm.websphere.rsadapter.WSConnection.setClientInformation com.ibm.ws.rsadapter.cci.WSResourceAdapterBase.getNativeConnection (javax.resource.cci.Connection) com.ibm.ws.rsadapter.cci.WSResourceAdapterBase.getNativeConnection (com.ibm.ws.rsadapter.jdbc.WSJdbcConnection) com.ibm.ws.rsadapter.jdbc.WSJdbcUtil.getNativeConnection (com.ibm.ws.rsadapter.jdbc.WSJdbcConnection) Fields: com.ibm.websphere.rsadapter.DataStoreHelper.ORACLE_HELPER com.ibm.websphere.rsadapter.WSConnection.CLIENT_ACCOUNTING_INFO com.ibm.websphere.rsadapter.WSConnection.CLIENT_APPLICATION_NAME com.ibm.websphere.rsadapter.WSConnection.CLIENT_ID com.ibm.websphere.rsadapter.WSConnection.CLIENT_LOCATION com.ibm.websphere.rsadapter.WSConnection.CLIENT_OTHER_INFO com.ibm.websphere.rsadapter.WSConnection.CLIENT_TYPE	If we are using the OracleDataStoreHelper, switch to the Oracle 11g JDBC driver and use the Oracle11gDataStoreHelper instead. Instead of using getNativeConnection, use the JDBC 4.0 wrapper pattern. Instead of WSConnection client information, use JDBC 4.0 client-information APIs. Instead of com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn), use the com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn, boolean logEvent) method. The new method provides a boolean parameter that allows us to control whether or not connection error events are logged to system out. Instead of WSCallHelper.call, use standard Java reflections APIs. If we are using the ORACLE_HELPER, switch to the Oracle 11g JDBC driver and use the ORACLE_11G_HELPER instead.
Application programming model	The following session-management function: Global session sharing through the Servlet21SessionCompatibility property Support for any session-manager properties as system properties Support for any session-manager properties as web container custom properties	For session sharing, redesign the applications so that the session is appropriately scoped at the web module as specified in the Java Servlet Specification v2.2 and later. If data must be shared across the Web-module boundary, use the Websphere Extension, shared session context = true, or use the IBMApplicationSession API. Rather than specifying session manager properties as system or web container custom properties, use session-manager custom properties.
	Connection validation by SQL query	Use the timeout-based validation introduced with JDBC 4.0.
	Classes: SERV1\ws\code\admin.thinclient\build\classes\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgr*.class SERV1\ws\code\admin.thinclient\build\classes\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgrImpl*.class Interface: SERV1\ws\code\admin.thinclient\src\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgr.java Methods: All methods in the RemoteCommandMgr interface and MBean xml, SERV1\ws\code\admin.jmx\src\com\ibm\ws\management\ descriptor\xml\RemoteCommandMgr.xml Constructor: RemoteCommandMgrImpl()	No migration action is necessary.
	The following proprietary classes used to represent and manipulate WS-Addressing endpoint references in Java API for XML Web Services (JAX-WS) 2.0: com.ibm.websphere.wsaddressing.jaxws.W3CEndpointReference com.ibm.websphere.wsaddressing.jaxws.SubmissionEndpointReference com.ibm.websphere.wsaddressing.jaxws.EndpointReferenceConverter	Use the following classes instead: javax.xml.ws.wsaddressing.W3CEndpointReference com.ibm.websphere.wsaddressing.jaxws21.SubmissionEndpointReference com.ibm.websphere.wsaddressing.jaxws21.EndpointReferenceConverter
	The following WebSphere Common Configuration Model (WCCM) types: SIBJMSProvider SIBJMSConnectionFactory SIBJMSQueueConnectionFactory SIBJMSTopicConnectionFactory SIBJMSQueue SIBJMSTopic	If one of our Jython or Jacl wsadmin scripts uses any of these types, modify the script to use the correct AdminTask command to complete the equivalent function. For example: AdminTask.listSIBJMSQueues()
Environment	IBM HTTP Server (IHS) mod_file_cache module	Migrate the IHS configuration directives from mod_file_cache to the appropriate provided cache mechanism-either mod_mem_cache or mod_cache.
	IHS mod_ibm_ldap module	Migrate the mod_ibm_ldap configuration directives to the equivalent mod_ldap directives.
	IHS mod_mime_magic module	Remove any IHS configuration directives associated with this module.
	IHS mod_proxy_ftp module	Remove any IHS configuration directives associated with this module.
	IHS mod_afpa_cache module Adaptive Fast Path Architecture (AFPA) is being deprecated for both AIX and Windows operating systems for both static and dynamically generated content caching.	Remove any IHS configuration directives associated with this module.
J2EE resources	The following features: Support for using Java Message Service (JMS) providers that are not compliant with the J2EE Connector Architecture 1.5 specification is deprecated. The WAS v5 default messaging provider was deprecated in v6.1. The IBM MQ messaging provider was updated in v7.0 to support the J2EE Connector Architecture 1.5. Support for other usages of this provider are deprecated.	Use JMS providers that are compliant with the J2EE Connector Architecture 1.5 specification.
Data access	disablePK54589 system property	Configure the data source custom property isConnectionSharingBasedOnCurrentState. If we are using disablePK54589=true, we can replace it with isConnectionSharingBasedOnCurrentState=false.
Programming	Shipment of JavaServer Faces widget library (JWL) with WAS	Manually create a shared library for JWL using the jar from Rational Application Developer.
Profile management	Deployment manager profile template	Use the management profile template with a deployment manager server.
Security	Support for using the Simple and Protected GSS-API Negotiation Mechanism trust association interceptor (SPNEGO TAI) to securely negotiate and authenticate HTTP requests for secured resources	Use the imbedded SPNEGO web authentication to provide dynamic reload of the SPNEGO filters and to enable fallback to the application login method.
Servers	WAS for z/OS support for 31-bit addressing mode	Start migrating to 64-bit support. The default in v7.0 is to create new servers to run in 64-bit addressing mode; however, servers that are migrate to Version 7.0 from an earlier release can still be configured to run in 31-bit mode.
	Shipment of Apache Struts 1.1, 1.2.4, and 1.2.7 as optional libraries within WAS	If we would like to continue using these versions of Apache Struts, they are available from the Apache Struts website.
	For core group transport, the following configuration options: Unicast Multicast	Move to channel framework transport. For more information, read Core group transports.
System administration	Option to install the Pluggable application client feature for the IBM Application Client for WAS	Use the new EJB Thin Application Client feature instead.
	The following service integration bus (SIBus) security features: -secure flag on the createSIBus and the modifySIBus commands listInheritSenderForTopic, listInheritReceiverForTopic, and listInheritDefaultsForDestination commands Inter-engine authentication alias	Perform the following actions: Use the -busSecurity flag instead of the -secure flag. Replace usages of the listInheritSenderForTopic, listInheritReceiverForTopic, and listInheritDefaultsForDestination commands with the isInheritSenderForTopic, isInheritReceiverForTopic, and isInheritDefaultsForDestinaton commands respectively. Remove any usage of the -interEngineAuthenticationAlias option on the createSIBus and modifySIBus commands.
	Collector tool (collector.bat or collector.sh) that gathers information about the WAS installation and packages it in a JAR file that we can send to IBM Software Support This feature was undeprecated.	Use IBM Support Assistant (ISA) Lite.
	Protocol-based proxy server templates	Use the administrative console or the wsadmin commands in the ServerManagement command group to select one or multiple protocols for proxy servers. For more information, read ServerManagement
	WebSphere Touchpoint (WAS.admin.wstp component-all classes and methods)	Use the other standard management interfaces in WAS.
	Commands in the SecureConversation .	Use the commands in the WSSCacheManagement command group to manage Web Services Security (WS-Security) distributed-cache configurations.
	The following LDAP configuration names in the virtual member manager (VMM) federated repository: SECUREWAY, IDS4, IDS51, and IDS6 DOMINO5, DOMINO6, and DOMINO65 AD2000 and AD2003	Use the following configuration names: IDS rather than SECUREWAY, IDS4, IDS51, or IDS6 DOMINO rather than DOMINO5, DOMINO6, or DOMINO65 AD rather than AD2000 or AD2003
Web services	Support for the '2006/02' WS-Addressing Web Services Description Language (WSDL) binding namespace	Replace any uses of the '2006/02' namespace in WSDL files with uses of the '2006/05' namespace
	Web Services Distributed Management (WSDM) interface	Use the other standard management interfaces in WAS.
	IBM proprietary SOAP over Java Message Service (JMS) protocol for JAX-WS or JAX-RPC applications	Use the standard SOAP over JMS protocol. For more information, read SOAP over JMS protocol and SOAP over Java Message Service. Restriction: If our client application invokes enterprise-bean based web services supported by a release of WAS that is earlier than v7.0, we must continue to use the IBM proprietary SOAP over JMS protocol to access those web services.

Category	Deprecation	Recommended Migration Action
Application programming model	registerSynchronizationCallbackForCurrentTran method in the com.ibm.websphere.jtaextensions.ExtendedJTATransaction interface	Use the registerInterposedSynchronization method of the TransactionSynchronizationRegistry interface instead. For more information, read JTA support.
	com.ibm.ws.extensionhelper.TransactionControl interface	Use the com.ibm.wsspi.uow.UOWManager interface instead. For more information, read JTA support.
	HttpServletRequestProxy class in the com.ibm.websphere.servlet.request package	Use the HttpServletRequestWrapper class instead of the HttpServletRequestProxy class. Use the subclasses of this class to overload or enhance the functionality of a server-provided HttpServletRequest.
	HttpServletResponseProxy class in the com.ibm.websphere.servlet.response package	Use the HttpServletResponseWrapper class instead of the HttpServletResponseProxy class. Use the subclasses of this class to overload or enhance the functionality of a server-provided HttpServletResponse.
	The following classes, interfaces, methods, and fields of the WebSphere relational resource adapter: Classes: com.ibm.websphere.rsadapter.JdbcAccessorImpl com.ibm.websphere.rsadapter.OracleDataStoreHelper Interfaces: com.ibm.websphere.rsadapter.Beginnable com.ibm.websphere.rsadapter.HandleStates com.ibm.websphere.rsadapter.Reassociateable com.ibm.websphere.rsadapter.WSNativeConnectionAccessor Methods: com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn) com.ibm.websphere.rsadapter.WSCallHelper.call com.ibm.websphere.rsadapter.WSConnection.getClientInformation com.ibm.websphere.rsadapter.WSConnection.setClientInformation com.ibm.ws.rsadapter.cci.WSResourceAdapterBase.getNativeConnection (javax.resource.cci.Connection) com.ibm.ws.rsadapter.cci.WSResourceAdapterBase.getNativeConnection (com.ibm.ws.rsadapter.jdbc.WSJdbcConnection) com.ibm.ws.rsadapter.jdbc.WSJdbcUtil.getNativeConnection (com.ibm.ws.rsadapter.jdbc.WSJdbcConnection) Fields: com.ibm.websphere.rsadapter.DataStoreHelper.ORACLE_HELPER com.ibm.websphere.rsadapter.WSConnection.CLIENT_ACCOUNTING_INFO com.ibm.websphere.rsadapter.WSConnection.CLIENT_APPLICATION_NAME com.ibm.websphere.rsadapter.WSConnection.CLIENT_ID com.ibm.websphere.rsadapter.WSConnection.CLIENT_LOCATION com.ibm.websphere.rsadapter.WSConnection.CLIENT_OTHER_INFO com.ibm.websphere.rsadapter.WSConnection.CLIENT_TYPE	If we are using the OracleDataStoreHelper, switch to the Oracle 11g JDBC driver and use the Oracle11gDataStoreHelper instead. Instead of using getNativeConnection, use the JDBC 4.0 wrapper pattern. Instead of WSConnection client information, use JDBC 4.0 client-information APIs. Instead of com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn), use the com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn, boolean logEvent) method. The new method provides a boolean parameter that allows us to control whether or not connection error events are logged to system out. Instead of WSCallHelper.call, use standard Java reflections APIs. If we are using the ORACLE_HELPER, switch to the Oracle 11g JDBC driver and use the ORACLE_11G_HELPER instead.
Application programming model	The following session-management function: Global session sharing through the Servlet21SessionCompatibility property Support for any session-manager properties as system properties Support for any session-manager properties as web container custom properties	For session sharing, redesign the applications so that the session is appropriately scoped at the web module as specified in the Java Servlet Specification v2.2 and later. If data must be shared across the Web-module boundary, use the Websphere Extension, shared session context = true, or use the IBMApplicationSession API. Rather than specifying session manager properties as system or web container custom properties, use session-manager custom properties.
	Connection validation by SQL query	Use the timeout-based validation introduced with JDBC 4.0.
	Classes: SERV1\ws\code\admin.thinclient\build\classes\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgr*.class SERV1\ws\code\admin.thinclient\build\classes\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgrImpl*.class Interface: SERV1\ws\code\admin.thinclient\src\com\ibm\ws\management\ cmdframework\impl\RemoteCommandMgr.java Methods: All methods in the RemoteCommandMgr interface and MBean xml, SERV1\ws\code\admin.jmx\src\com\ibm\ws\management\ descriptor\xml\RemoteCommandMgr.xml Constructor: RemoteCommandMgrImpl()	No migration action is necessary.
	The following proprietary classes used to represent and manipulate WS-Addressing endpoint references in Java API for XML Web Services (JAX-WS) 2.0: com.ibm.websphere.wsaddressing.jaxws.W3CEndpointReference com.ibm.websphere.wsaddressing.jaxws.SubmissionEndpointReference com.ibm.websphere.wsaddressing.jaxws.EndpointReferenceConverter	Use the following classes instead: javax.xml.ws.wsaddressing.W3CEndpointReference com.ibm.websphere.wsaddressing.jaxws21.SubmissionEndpointReference com.ibm.websphere.wsaddressing.jaxws21.EndpointReferenceConverter
	The following WebSphere Common Configuration Model (WCCM) types: SIBJMSProvider SIBJMSConnectionFactory SIBJMSQueueConnectionFactory SIBJMSTopicConnectionFactory SIBJMSQueue SIBJMSTopic	If one of our Jython or Jacl wsadmin scripts uses any of these types, modify the script to use the correct AdminTask command to complete the equivalent function. For example: AdminTask.listSIBJMSQueues()
Environment	IBM HTTP Server (IHS) mod_file_cache module	Migrate the IHS configuration directives from mod_file_cache to the appropriate provided cache mechanism-either mod_mem_cache or mod_cache.
	IHS mod_ibm_ldap module	Migrate the mod_ibm_ldap configuration directives to the equivalent mod_ldap directives.
	IHS mod_mime_magic module	Remove any IHS configuration directives associated with this module.
	IHS mod_proxy_ftp module	Remove any IHS configuration directives associated with this module.
	IHS mod_afpa_cache module Adaptive Fast Path Architecture (AFPA) is being deprecated for both AIX and Windows operating systems for both static and dynamically generated content caching.	Remove any IHS configuration directives associated with this module.
Installation and maintenance tools	Support for using IBM Update Installer for WebSphere Software v6.x to apply maintenance on WAS v6.0.2.21+ and v6.1.0.x	Use IBM Update Installer for WebSphere Software v7.0. Update Installer Version 7.0 supports applying maintenance on WAS Version 6.0.2.21+, v6.1.0.x, and v7.0.
	Support for using IBM WebSphere Installation Factory v6.1 to create installation packages for WAS v6.1	Use IBM WebSphere Installation Factory v7.0. WebSphere Installation Factory v7.0 supports creating installation packages for WAS v6.1 and v7.0.
J2EE resources	The following features: Support for using JMS providers that are not compliant with the J2EE Connector Architecture 1.5 specification is deprecated. The WAS v5 default messaging provider was deprecated in v6.1. The IBM MQ messaging provider was updated in v7.0 to support the J2EE Connector Architecture 1.5. Support for other usages of this provider are deprecated.	Use JMS providers that are compliant with the J2EE Connector Architecture 1.5 specification.
Data access	disablePK54589 system property	Configure the data source custom property isConnectionSharingBasedOnCurrentState. If we are using disablePK54589=true, we can replace it with isConnectionSharingBasedOnCurrentState=false.
Programming	Shipment of JavaServer Faces widget library (JWL) with WAS	Manually create a shared library for JWL using the jar from Rational Application Developer.
Profile management	Deployment manager profile template	Use the management profile template with a deployment manager server.
Security	Support for using the Simple and Protected GSS-API Negotiation Mechanism trust association interceptor (SPNEGO TAI) to securely negotiate and authenticate HTTP requests for secured resources	Use the imbedded SPNEGO web authentication to provide dynamic reload of the SPNEGO filters and to enable fallback to the application login method.
Servers	Shipment of Apache Struts 1.1, 1.2.4, and 1.2.7 as optional libraries within WAS	If we would like to continue using these versions of Apache Struts, they are available from the Apache Struts website.
	For core group transport, the following configuration options: Unicast Multicast	Move to channel framework transport. For more information, read Core group transports.
System administration	Option to install the Pluggable application client feature for the IBM Application Client for WAS	Use the new EJB Thin Application Client feature instead.
	The following service integration bus (SIBus) security features: -secure flag on the createSIBus and the modifySIBus commands listInheritSenderForTopic, listInheritReceiverForTopic, and listInheritDefaultsForDestination commands Inter-engine authentication alias	Perform the following actions: Use the -busSecurity flag instead of the -secure flag. Replace usages of the listInheritSenderForTopic, listInheritReceiverForTopic, and listInheritDefaultsForDestination commands with the isInheritSenderForTopic, isInheritReceiverForTopic, and isInheritDefaultsForDestinaton commands respectively. Remove any usage of the -interEngineAuthenticationAlias option on the createSIBus and modifySIBus commands.
	Collector tool (collector.bat or collector.sh) that gathers information about the WAS installation and packages it in a JAR file that we can send to IBM Software Support This feature was undeprecated.	Use IBM Support Assistant (ISA) Lite.
	Protocol-based proxy server templates	Use the administrative console or the wsadmin commands in the ServerManagement command group to select one or multiple protocols for proxy servers. For more information, read ServerManagement
	WebSphere Touchpoint (WAS.admin.wstp component-all classes and methods)	Use the other standard management interfaces in WAS.
	Commands in the SecureConversation .	Use the commands in the WSSCacheManagement command group to manage Web Services Security (WS-Security) distributed-cache configurations.
	The following LDAP configuration names in the virtual member manager (VMM) federated repository: SECUREWAY, IDS4, IDS51, and IDS6 DOMINO5, DOMINO6, and DOMINO65 AD2000 and AD2003	Use the following configuration names: IDS rather than SECUREWAY, IDS4, IDS51, or IDS6 DOMINO rather than DOMINO5, DOMINO6, or DOMINO65 AD rather than AD2000 or AD2003
Web services	Support for the '2006/02' WS-Addressing Web Services Description Language (WSDL) binding namespace	Replace any uses of the '2006/02' namespace in WSDL files with uses of the '2006/05' namespace
	Web Services Distributed Management (WSDM) interface	Use the other standard management interfaces in WAS.
	IBM proprietary SOAP over Java Message Service (JMS) protocol for JAX-WS or JAX-RPC applications	Use the standard SOAP over JMS protocol. For more information, read SOAP over JMS protocol and SOAP over Java Message Service. Restriction: If our client application invokes enterprise-bean based web services supported by a release of WAS that is earlier than v7.0, we must continue to use the IBM proprietary SOAP over JMS protocol to access those web services.

Features deprecated in v6.1

(ZOS)

Category	Deprecation	Recommended Migration Action
Application programming model	setDatabaseDefaultIsolationLevel(int) method in the com.ibm.websphere.rsadapter.DataStoreHelperMetaData class	Start using the following method 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. Replace all uses of the com.ibm.websphere.sib.mediation.messagecontext.SIMediationBean MessageContext interface with an equivalent interface. WAS does not provide an implementation of this interface.
	Support for HTTP transport configuration	Begin moving to channel-based transport.
	The following web container message bean functions: startTransports stopTransports restartWebApplication	Begin moving to the channel framework. The channel framework provides the TransportChannelService message bean, which is more flexible and has more methods than the current web container transport-related methods.
	Support for deploying container-managed entity beans to a generic SQL database	If an application uses SQL92 or SQL99 because the application has to run with different relational databases, use the IBM tooling to generate deployed code for each database vendor or version that the application might use. At installation time, specify the database vendor or version that will used with WAS.
	IBM WebSphere Studio tools runtime support provided by the following classes (which were used to leverage Visual Age for Java tooling): com.ibm.webtools.runtime.AbstractStudioServlet com.ibm.webtools.runtime.BuildNumber com.ibm.webtools.runtime.NoDataException com.ibm.webtools.runtime.StudioPervasiveServlet com.ibm.webtools.runtime.TransactionFailureException com.ibm.webtools.runtime.WSUtilities	Rearchitect the applications to use standard J2EE coding conventions.
	CUSTOM_HELPER constant field in the com.ibm.websphere.rsadapter.DataStoreHelper class API	If we create our own DataStoreHelper implementation class, do not invoke setHelperType(DataStoreHelper.CUSTOM_HELPER). Instead, let the HelperType value be set by the implementation class from which it inherits.
J2EE resources	Support for the ability to connect from either an application server or a J2EE application client to the JMS Server component of the embedded messaging feature in WAS v5 This deprecation includes the following capabilities: Define JMS resource definitions for the v5 default messaging provider 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 any JMS Server messaging providers that are hosted on WAS v5.1 application servers are moved onto v6.0 or later application servers. This task is handled automatically when we 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	Customization Dialog, the set of Interactive System Productivity Facility (ISPF) panels used to create jobs and instructions for configuring and migrating the WAS for z/OS environment	Use the Profile Management Tool (z/OS only) or the zpmt command to generate the jobs and instructions for creating profiles. For information on using the Profile Management Tool (z/OS only), read the Configure z/OS application-serving environments with the Profile Management Tool article in the information center. For information on using the zpmt command, read the Configure z/OS application-serving environments with the zpmt command article in the documentation. Use the z/OS Migration Management Tool to generate migration definitions. For information on using the z/OS Migration Management Tool, read the Use the z/OS Migration Management Tool to manage migration definitions article in the documentation.
	clientUpgrade command	No migration action is necessary.
	Cloudscape datastore helper (com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper) and Cloudscape Network Server datastore helper (com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper) as well as their types in DataStoreHelper	For existing configurations, no migration action is necessary. The migration utility changes the deprecated Cloudscape helpers to Derby helpers. For new configurations, use the Derby datastore helpers and types instead of the Cloudscape datastore helpers. For more information, read Data source minimum required settings, by vendor.
	DB2 Legacy CLI-based Type 2 JDBC Driver provider	Start using the DB2 Universal JDBC Driver Provider.
	Logical pool distribution support (com.ibm.websphere.csi.ThreadPoolStrategy.LogicalPoolDistribution)	No migration action is necessary. When this function is removed, however, all custom Object Request Broker (ORB) properties specified for it will be ignored. The custom ORB properties of interest are com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.*. For more information, read 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.
	The protocol_http_transport_class_mapping_file configuration variable that specifies the transaction class mapping file name	Use the wlm_classification_file configuration variable to specify the name of the XML file that maps HTTP requests to WLM transaction classes. The deprecated mapping file supported specifying multiple transaction classes per row. This allowed the creation of an artificial round-robin work-dispatch effect. Although the XML file pointed to by wlm_classification_file does not support specifying multiple transaction classes per row, we can better achieve this same effect using zWLM's round-robin option. Select this option by specifying wlm_stateful_session_placement_on=1.
	The following configuration variables: protocol_http_backlog protocol_https_backlog protocol_iiop_backlog protocol_iiop_backlog_ssl The protocol_iiop_backlog and protocol_iiop_backlog_ss configuration variables are not deprecated for the daemon.	Use the TCP transport channel listenBacklog custom property. For information on using this property, read TCP transport channel custom properties
	SSL certificate mapping file specified by the protocol_https_cert_mapping_file environment variable The following related configuration variables are also deprecated: protocol_https_cert_mapping_file protocol_https_default_cert_label	No migration action is necessary at this time. In a subsequent version of WAS for z/OS, a new configuration mechanism will be provided that will allow us to choose a different SSL server certificate to be used for the SSL handshake depending on the server IP address of the socket connection. This new administrative mechanism will replace the current file format of the file pointed to by the protocol_http_cert_mapping_file variable.
	JVM system property com.ibm.websphere.sendredirect.compatibility	Begin modifying the applications to redirect non-relative URLs, those starting with a forward slash ("/"), relative to the servlet container root (web_server_root) instead of the web application context root. Read the Java Servlet 2.4 Specification, which is available for download at http://jcp.org/aboutJava/communityprocess/final/jsr154/, for information on how sendRedirect should behave.
	Web container PageList Servlet custom extension, including the following classes: com.ibm.servlet.ClientList com.ibm.servlet.ClientListElement com.ibm.servlet.MLNotFoundException com.ibm.servlet.PageListServlet com.ibm.servlet.PageNotFoundException	Rearchitect the applications to use javax.servlet.filter classes rather than com.ibm.servlet classes. Starting with the Java Servlet 2.3 specification, javax.servlet.filter classes give you the capability to intercept requests and examine responses. They also allow provide chaining functionality as well as functionality for embellishing or truncating responses.
	The following custom properties for a data source: validateNewConnection validateNewConnectionRetryCount validateNewConnectionRetryInterval	The product now offers these properties as pre-configured options, which are the replacement properties in the following list. To avoid runtime error messages, permanently disable the original custom properties by deleting them from the list of custom properties. validateNewConnection is replaced by Pretest new connection validateNewConnectionRetryCount is replaced by Number of retries validateNewConnectionRetryInterval is replaced by Retry interval If the new properties and old properties coexist, the new properties take precedence.
System administration	Peer restart and recovery (PRR)	For transaction recovery, migrate from using PRR functionality to using high availability manager functionality. Read Transactional high availability for information on configuring the high availability manager to perform transaction recovery.
Security	Simple WebSphere Authentication echanism (SWAM)	Use the LTPA mechanism. For more information, read 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, read Migrate Common Object Request Broker Architecture programmatic login to JAAS (CORBA and JAAS).
	com.ibm.ws.security.web.WebSealTrustAssociationInterceptor trust association interceptor (TAI) interface This Tivoli TAI interceptor that implements the WAS TAI interface was provided to support WebSEAL Version 4.1.	If we plan to use WebSEAL 5.1 or later, we should migrate to use the com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus interceptor.
	z/OS System SSL support for all server types except Daemon	Begin converting existing wsadmin scripts that use z/OS System SSL security settings to scripts that use JSSE security settings.
Performance	Support for the Java Virtual Machine Profiler Interface (JVMPI) is deprecated along with the following related JVM runtime counters: ObjectMovedCount ObjectFreedCount ObjectAllocateCount	Begin moving to the Java Virtual achine Tool Interface (JVMTI). For more information, read JVM Tool Interface (JVMTI).
	Support for the Java Virtual Machine Debugger Interface (JVMDI)	Begin moving to the Java Virtual achine Tool Interface (JVMTI). For more information, read JVM Tool Interface (JVMTI).
Problem determination	Message ID format used in WAS v6.0.x and earlier The message prefixes for log files were not previously registered with the primary message registry. WAS v6.1.x and later use compliant message prefixes in the output logs.	Use the convertlog command and the MessageConverter class to assist us in migrating tools that rely on the older message format. For more information, read Converting log files to use IBM unique Message IDs.
	com.ibm.etools.logging.util plug-in, the logutil.jar file Logging facility Logging facility used for logging Java primitives and complex objects to named loggers; configurable with predefined filtering levels, Logging Agent and file sinks, and output formats through an API, Eclipse plug-in manifest, or Eclipse preference panel Logging agent XML-based messaging agent used in conjunction with the IBM Agent Controller to write log and trace XML records to a logging service remotely attachable through an API or Test and Performance Tools Platform (TPTP), formally Hyades, Eclipse workbench Problem determination artifacts and messages Original implementation of the Manageability (M12) Model Problem Determination Architecture Version 1.5 and Problem Determination Artifacts Common Data Model specification used for capturing and encoding log and trace data Distributed correlator service (DCS) Distributed correlator service used for instrumenting correlation identifiers for correlating log and trace data across one or more hosts Java client bindings Java client bindings used to communicate with the IBM Agent Controller to launch local and remote processes, attach to running processes, and monitor active agents in a secure client environment	Begin moving plug-ins and application code using configuration files, classes, methods, or variables in the com.ibm.etools.logging.util plug-in to the following replacements: Logging facility Replacement: Java Logging APIs in Java Version 1.4.0+; Logging Agent support for the Java Logging APIs provided in TPTP and Common Logging (com.ibm.etools.common.logging/logging.jar) Logging agent Replacement: TPTP Logging Agent (org.eclipse.hyades.logging.core/hlcore.jar) Problem determination artifacts and messages Replacement: Common Base Event Version 1.0.1 specification and TPTP implementation (org.eclipse.hyades.logging.core/hlcbe101.jar) Distributed correlator service (DCS) Replacement: TPTP Correlation Service (org.eclipse.hyades.execution.correlation/hcorrelation.jar) Java client bindings Replacement: TPTP Java Client Bindings (org.eclipse.hyades.execution/hexl.jar) For more information, read the com.ibm.etools.logging.util\doc\IBM_Logging_Utilities_Migration_Guide.html document.

(Dist)

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. Replace all uses of the com.ibm.websphere.sib.mediation.messagecontext.SIMediationBean MessageContext interface with an equivalent interface. WAS does not provide an implementation of this interface.
	The following web container message bean functions: startTransports stopTransports restartWebApplication	Begin moving to the channel framework. The channel framework provides the TransportChannelService message bean, which is more flexible and has more methods than the current web container transport-related methods.
	Support for deploying container-managed entity beans to a generic SQL database	If an application uses SQL92 or SQL99 because the application has to run with different relational databases, use the IBM tooling to generate deployed code for each database vendor or version that the application might use. At installation time, specify the database vendor or version that will used with WAS.
	IBM WebSphere Studio tools runtime support provided by the following classes (which were used to leverage Visual Age for Java tooling): com.ibm.webtools.runtime.AbstractStudioServlet com.ibm.webtools.runtime.BuildNumber com.ibm.webtools.runtime.NoDataException com.ibm.webtools.runtime.StudioPervasiveServlet com.ibm.webtools.runtime.TransactionFailureException com.ibm.webtools.runtime.WSUtilities	Rearchitect the applications to use standard J2EE coding conventions.
	CUSTOM_HELPER constant field in the com.ibm.websphere.rsadapter.DataStoreHelper class API	If we create our own DataStoreHelper implementation class, do not invoke setHelperType(DataStoreHelper.CUSTOM_HELPER). Instead, let the HelperType value be set by the implementation class from which it inherits.
J2EE resources	Support for the ability to connect from either an application server or a J2EE application client to the JMS Server component of the embedded messaging feature in WAS v5 This deprecation includes the following capabilities: Define JMS resource definitions for the v5 default messaging provider 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 any JMS Server messaging providers that are hosted on WAS v5.1 application servers are moved onto v6.0 or later application servers. This task is handled automatically when we 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	setup command	Use the install command.
	clientUpgrade command	No migration action is necessary.
	wasprofile command	Use the manageprofiles command. For more information, read manageprofiles command.
	The following WASPostUpgrade command parameters: -import xmi_data_file -substitute "key1=value1[;key2=value2;[...]]"	No migration action is necessary.
	Cloudscape datastore helper (com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper) and Cloudscape Network Server datastore helper (com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper) as well as their types in DataStoreHelper	For existing configurations, no migration action is necessary. The migration utility changes the deprecated Cloudscape helpers to Derby helpers. For new configurations, use the Derby datastore helpers and types instead of the Cloudscape datastore helpers. For more information, read Data source minimum required settings, by vendor.
	DB2 Legacy CLI-based Type 2 JDBC Driver provider	Start using the DB2 Universal JDBC Driver Provider.
	Logical pool distribution support (com.ibm.websphere.csi.ThreadPoolStrategy.LogicalPoolDistribution)	No migration action is necessary. When this function is removed, however, all custom Object Request Broker (ORB) properties specified for it will be ignored. The custom ORB properties of interest are com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.*. For more information, read Logical pool distribution and Object Request Broker custom properties.
	ORB thread pool configuration as part of the Server object in the server.xml file	Use the thread pool configuration that is part of the ServerIndex object in the serverindex.xml file.
	JVM system property com.ibm.websphere.sendredirect.compatibility	Begin modifying the applications to redirect non-relative URLs, those starting with a forward slash ("/"), relative to the servlet container root (web_server_root) instead of the web application context root. Read the Java Servlet 2.4 Specification, which is available for download at http://jcp.org/aboutJava/communityprocess/final/jsr154/, for information on how sendRedirect should behave.
	Web container PageList Servlet custom extension, including the following classes: com.ibm.servlet.ClientList com.ibm.servlet.ClientListElement com.ibm.servlet.MLNotFoundException com.ibm.servlet.PageListServlet com.ibm.servlet.PageNotFoundException	Rearchitect the applications to use javax.servlet.filter classes rather than com.ibm.servlet classes. Starting with the Java Servlet 2.3 specification, javax.servlet.filter classes give you the capability to intercept requests and examine responses. They also allow provide chaining functionality as well as functionality for embellishing or truncating responses.
	The following custom properties for a data source: validateNewConnection validateNewConnectionRetryCount validateNewConnectionRetryInterval	The product now offers these properties as pre-configured options, which are the replacement properties in the following list. To avoid runtime error messages, permanently disable the original custom properties by deleting them from the list of custom properties. validateNewConnection is replaced by Pretest new connection validateNewConnectionRetryCount is replaced by Number of retries validateNewConnectionRetryInterval is replaced by Retry interval If the new properties and old properties coexist, the new properties take precedence.
	DISABLE_FILE_LOCKING transaction service custom property	Clear the Enable file locking check box on the Transaction Service panel of the administrative console. For more information, read Disable file locking.
	Simple WebSphere Authentication echanism (SWAM)	Use the LTPA mechanism. For more information, read LTPA.
Security	LoginHelper CORBA authentication helper function (com.ibm.ws.security.util.LoginHelper)	Migrate to the Java Authentication and Authorization Service (JAAS) programming model. For information on this migration, read Migrate Common Object Request Broker Architecture programmatic login to JAAS (CORBA and JAAS).
	com.ibm.ws.security.web.WebSealTrustAssociationInterceptor trust association interceptor (TAI) interface This Tivoli TAI interceptor that implements the WAS TAI interface was provided to support WebSEAL Version 4.1.	If we plan to use WebSEAL 5.1 or later, we should migrate to use the com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus interceptor.
	Support for the Java Virtual Machine Profiler Interface (JVMPI) is deprecated along with the following related JVM runtime counters: ObjectMovedCount ObjectFreedCount ObjectAllocateCount	Begin moving to the Java Virtual achine Tool Interface (JVMTI). For more information, read JVM Tool Interface (JVMTI).
Performance	Support for the Java Virtual Machine Debugger Interface (JVMDI)	Begin moving to the Java Virtual achine Tool Interface (JVMTI). For more information, read JVM Tool Interface (JVMTI).
	Message ID format used in WAS v6.0.x and earlier The message prefixes for log files were not previously registered with the primary message registry. WAS v6.1.x and later use compliant message prefixes in the output logs.	Use the convertlog command and the MessageConverter class to assist us in migrating tools that rely on the older message format. For more information, read Converting log files to use IBM unique Message IDs.
Problem determination	The com.ibm.etools.logging.util plug-in, the logutil.jar file Logging facility Logging facility used for logging Java primitives and complex objects to named loggers; configurable with predefined filtering levels, Logging Agent and file sinks, and output formats through an API, Eclipse plug-in manifest, or Eclipse preference panel Logging agent XML-based messaging agent used in conjunction with the IBM Agent Controller to write log and trace XML records to a logging service remotely attachable through an API or Test and Performance Tools Platform (TPTP), formally Hyades, Eclipse workbench Problem determination artifacts and messages Original implementation of the Manageability (M12) Model Problem Determination Architecture Version 1.5 and Problem Determination Artifacts Common Data Model specification used for capturing and encoding log and trace data Distributed correlator service (DCS) Distributed correlator service used for instrumenting correlation identifiers for correlating log and trace data across one or more hosts Java client bindings Java client bindings used to communicate with the IBM Agent Controller to launch local and remote processes, attach to running processes, and monitor active agents in a secure client environment	Begin moving plug-ins and application code using configuration files, classes, methods, or variables in the com.ibm.etools.logging.util plug-in to the following replacements: Logging facility Replacement: Java Logging APIs in Java Version 1.4.0+; Logging Agent support for the Java Logging APIs provided in TPTP and Common Logging (com.ibm.etools.common.logging/logging.jar) Logging agent Replacement: TPTP Logging Agent (org.eclipse.hyades.logging.core/hlcore.jar) Problem determination artifacts and messages Replacement: Common Base Event Version 1.0.1 specification and TPTP implementation (org.eclipse.hyades.logging.core/hlcbe101.jar) Distributed correlator service (DCS) Replacement: TPTP Correlation Service (org.eclipse.hyades.execution.correlation/hcorrelation.jar) Java client bindings Replacement: TPTP Java Client Bindings (org.eclipse.hyades.execution/hexl.jar) For more information, read the com.ibm.etools.logging.util\doc\IBM_Logging_Utilities_Migration_Guide.html document.

(iSeries)

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. Replace all uses of the com.ibm.websphere.sib.mediation.messagecontext.SIMediationBean MessageContext interface with an equivalent interface. WAS does not provide an implementation of this interface.
	The following web container message bean functions: startTransports stopTransports restartWebApplication	Begin moving to the channel framework. The channel framework provides the TransportChannelService message bean, which is more flexible and has more methods than the current web container transport-related methods.
	Support for deploying container-managed entity beans to a generic SQL database	If an application uses SQL92 or SQL99 because the application has to run with different relational databases, use the IBM tooling to generate deployed code for each database vendor or version that the application might use. At installation time, specify the database vendor or version that will used with WAS.
	IBM WebSphere Studio tools runtime support provided by the following classes (which were used to leverage Visual Age for Java tooling): com.ibm.webtools.runtime.AbstractStudioServlet com.ibm.webtools.runtime.BuildNumber com.ibm.webtools.runtime.NoDataException com.ibm.webtools.runtime.StudioPervasiveServlet com.ibm.webtools.runtime.TransactionFailureException com.ibm.webtools.runtime.WSUtilities	Rearchitect the applications to use standard J2EE coding conventions.
	CUSTOM_HELPER constant field in the com.ibm.websphere.rsadapter.DataStoreHelper class API	If we create our own DataStoreHelper implementation class, do not invoke setHelperType(DataStoreHelper.CUSTOM_HELPER). Instead, let the HelperType value be set by the implementation class from which it inherits.
J2EE resources	Support for the ability to connect from either an application server or a J2EE application client to the JMS Server component of the embedded messaging feature in 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 any JMS Server messaging providers that are hosted on WAS v5.1 application servers are moved onto v6.0 or later application servers. This task is handled automatically when we 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	clientUpgrade command	No migration action is necessary.
	wasprofile command	Use the manageprofiles command. For more information, read manageprofiles command.
	The following WASPostUpgrade command parameters: -import xmi_data_file -substitute "key1=value1[;key2=value2;[...]]"	No migration action is necessary.
	Cloudscape datastore helper (com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper) and Cloudscape Network Server datastore helper (com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper) as well as their types in DataStoreHelper	For existing configurations, no migration action is necessary. The migration utility changes the deprecated Cloudscape helpers to Derby helpers. For new configurations, use the Derby datastore helpers and types instead of the Cloudscape datastore helpers. For more information, read Data source minimum required settings, by vendor.
	DB2 Legacy CLI-based Type 2 JDBC Driver provider	Start using the DB2 Universal JDBC Driver Provider.
	Logical pool distribution support (com.ibm.websphere.csi.ThreadPoolStrategy.LogicalPoolDistribution)	No migration action is necessary. When this function is removed, however, all custom Object Request Broker (ORB) properties specified for it will be ignored. The custom ORB properties of interest are com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.*. For more information, read Logical pool distribution and Object Request Broker custom properties.
	ORB thread pool configuration as part of the Server object in the server.xml file	Use the thread pool configuration that is part of the ServerIndex object in the serverindex.xml file.
	JVM system property com.ibm.websphere.sendredirect.compatibility	Begin modifying the applications to redirect non-relative URLs, those starting with a forward slash ("/"), relative to the servlet container root (web_server_root) instead of the web application context root. Read the Java Servlet 2.4 Specification, which is available for download at http://jcp.org/aboutJava/communityprocess/final/jsr154/, for information on how sendRedirect should behave.
	Web container PageList Servlet custom extension, including the following classes: com.ibm.servlet.ClientList com.ibm.servlet.ClientListElement com.ibm.servlet.MLNotFoundException com.ibm.servlet.PageListServlet com.ibm.servlet.PageNotFoundException	Rearchitect the applications to use javax.servlet.filter classes rather than com.ibm.servlet classes. Starting with the Java Servlet 2.3 specification, javax.servlet.filter classes give you the capability to intercept requests and examine responses. They also allow provide chaining functionality as well as functionality for embellishing or truncating responses.
	The following custom properties for a data source: validateNewConnection validateNewConnectionRetryCount validateNewConnectionRetryInterval	The product now offers these properties as pre-configured options, which are the replacement properties in the following list. To avoid runtime error messages, permanently disable the original custom properties by deleting them from the list of custom properties. validateNewConnection is replaced by Pretest new connection validateNewConnectionRetryCount is replaced by Number of retries validateNewConnectionRetryInterval is replaced by Retry interval If the new properties and old properties coexist, the new properties take precedence.
	DISABLE_FILE_LOCKING transaction service custom property	Clear the Enable file locking check box on the Transaction Service panel of the administrative console. For more information, read Disable file locking.
	Simple WebSphere Authentication echanism (SWAM)	Use the LTPA mechanism. For more information, read LTPA.
Security	LoginHelper CORBA authentication helper function (com.ibm.ws.security.util.LoginHelper)	Migrate to the Java Authentication and Authorization Service (JAAS) programming model. For information on this migration, read Migrate Common Object Request Broker Architecture programmatic login to JAAS (CORBA and JAAS).
	com.ibm.ws.security.web.WebSealTrustAssociationInterceptor trust association interceptor (TAI) interface This Tivoli TAI interceptor that implements the WAS TAI interface was provided to support WebSEAL Version 4.1.	If we plan to use WebSEAL 5.1 or later, we should migrate to use the com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus interceptor.
	Support for the Java Virtual Machine Profiler Interface (JVMPI) is deprecated along with the following related JVM runtime counters: ObjectMovedCount ObjectFreedCount ObjectAllocateCount	Begin moving to the Java Virtual achine Tool Interface (JVMTI). For more information, read JVM Tool Interface (JVMTI).
Performance	Support for the Java Virtual Machine Debugger Interface (JVMDI)	Begin moving to the Java Virtual achine Tool Interface (JVMTI). For more information, read JVM Tool Interface (JVMTI).
	Message ID format used in WAS v6.0.x and earlier The message prefixes for log files were not previously registered with the primary message registry. WAS v6.1.x and later use compliant message prefixes in the output logs.	Use the convertlog command and the MessageConverter class to assist us in migrating tools that rely on the older message format. For more information, read Converting log files to use IBM unique Message IDs.
Problem determination	The com.ibm.etools.logging.util plug-in, the logutil.jar file Logging facility Logging facility used for logging Java primitives and complex objects to named loggers; configurable with predefined filtering levels, Logging Agent and file sinks, and output formats through an API, Eclipse plug-in manifest, or Eclipse preference panel Logging agent XML-based messaging agent used in conjunction with the IBM Agent Controller to write log and trace XML records to a logging service remotely attachable through an API or Test and Performance Tools Platform (TPTP), formally Hyades, Eclipse workbench Problem determination artifacts and Messages Original implementation of the Manageability (M12) Model Problem Determination Architecture Version 1.5 and Problem Determination Artifacts Common Data Model specification used for capturing and encoding log and trace data Distributed correlator service (DCS) Distributed correlator service used for instrumenting correlation identifiers for correlating log and trace data across one or more hosts Java client bindings Java client bindings used to communicate with the IBM Agent Controller to launch local and remote processes, attach to running processes, and monitor active agents in a secure client environment	Begin moving plug-ins and application code using configuration files, classes, methods, or variables in the com.ibm.etools.logging.util plug-in to the following replacements: Logging facility Replacement: Java Logging APIs in Java Version 1.4.0+; Logging Agent support for the Java Logging APIs provided in TPTP and Common Logging (com.ibm.etools.common.logging/logging.jar) Logging agent Replacement: TPTP Logging Agent (org.eclipse.hyades.logging.core/hlcore.jar) Problem determination artifacts and messages Replacement: Common Base Event Version 1.0.1 specification and TPTP implementation (org.eclipse.hyades.logging.core/hlcbe101.jar) Distributed correlator service (DCS) Replacement: TPTP Correlation Service (org.eclipse.hyades.execution.correlation/hcorrelation.jar) Java client bindings Replacement: TPTP Java Client Bindings (org.eclipse.hyades.execution/hexl.jar) For more information, read the com.ibm.etools.logging.util\doc\IBM_Logging_Utilities_Migration_Guide.html document.

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*!ENTITY!*cell, java.lang.String node, java.lang.String server) was390Initialize(byte[] a_stoken, String a_printable_stoken, String a_jsabpref, int a_pid, int an_asid, String a_jsabjbnm) was390Initialize(byte[] a_stoken, java.lang.String a_printable_stoken, java.lang.String a_jsabpref, int a_pid, int an_asid, java.lang.String a_jsabjbnm, java.lang.String a_smcasid)	These methods are for 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 WAS runtime.
	TYPE_DISTRIBUTED_LOCKING_MAP constant defined in the com.ibm.websphere.cache.DistributedObjectCache class	Do not use the TYPE_DISTRIBUTED_LOCKING_MAP constant defined in the com.ibm.websphere.cache.DistributedObjectCache class because this constant is not supported by the WAS runtime.
System Administration	The following custom properties for a data source: dbFailOverEnabled connRetriesDuringDBFailover connRetryIntervalDuringDBFailover	Replace the properties with the following: Use validateNewConnection instead of dbFailOverEnabled. Use validateNewConnectionRetryCount instead of connRetriesDuringDBFailover. Use validateNewConnectionRetryInterval instead of connRetryIntervalDuringDBFailover. If the new properties and old properties coexist, the new properties take precedence.

(ZOS)

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.
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 WAS runtime.
	TYPE_DISTRIBUTED_LOCKING_MAP constant defined in the com.ibm.websphere.cache.DistributedObjectCache class	Do not use the TYPE_DISTRIBUTED_LOCKING_MAP constant defined in the com.ibm.websphere.cache.DistributedObjectCache class because this constant is not supported by the WAS runtime.
System Administration	The following custom properties for a data source: dbFailOverEnabled connRetriesDuringDBFailover connRetryIntervalDuringDBFailover	Replace the properties with the following: Use validateNewConnection instead of dbFailOverEnabled. Use validateNewConnectionRetryCount instead of connRetriesDuringDBFailover. Use validateNewConnectionRetryInterval instead of connRetryIntervalDuringDBFailover. If the new properties and old properties coexist, the new properties take precedence.

(ZOS) Features deprecated in v6.0.1

Category	Deprecation	Recommended Migration Action
Security	z/OS Secure Authentication Service (z/SAS) IIOP security protocol	Use the CSIv2 protocols.

Features deprecated in v6.0

(ZOS)

Category	Deprecation	Recommended Migration Action
Application programming model and container support	Support for the following tsx tags in the JavaServer Pages (JSP) engine: repeat dbconnect dbquery getProperty userid passwd dbmodify	Instead of using the tsx tags, we should use equivalent tags from the JavaServer Pages Standard Tag Library (JSTL). JSTL is supported in WAS v6.0, and the tag library is included with the product. Use this table as a guideline for converting tsx tags to JSTL tags: tsx tag JSTL tag tsx:repeat c:forEach tsx:dbconnect sql:setDataSource tsx:dbquery sql:query tsx:getProperty Use standard EL syntax; c:out value="${book.title}" for example, where book is the current index in the result set tsx:userid Use the user attribute of the setDataSource tag tsx:passwd Use the password attribute of the setDataSource tag tsx:dbmodify sql:update
	The following backend IDs: SQL92 (1992 SQL Standard) SQL99 (1999 SQL Standard)	Use other backend IDs.
Application services	JRas Extensions API No further enhancements are planned for JRas support.	Use the equivalent function in the java.util.logging package (JSR47).
	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 Version 5.x. Users do not need to take any specific actions and can continue to use the v2 EJB API; however, they should be aware that it does not include any UDDI functionality that is new to UDDI Version 3 and the interface might be removed in a subsequent release of WAS.
	The UDDI4J v2 class library, the uddi4jv2.jar file	Start using the Version 3 UDDI APIs. A client library is provided to simplify constructing and sending UDDI Version 3 requests from Java. This is the IBM UDDI Version 3 Client for Java, provided in uddiv3client.jar. The UDDI4J APIs can still be used; however, we should be aware that they do not provide access to any of the new UDDI Version 3 functionality and they might be removed in a subsequent release of WAS.
	All of the low-level UDDI Utility Tools (UUT) APIs, such as BusinessStub, ServiceStub, and so on, These APIs are all replaced with the high-level PromoterAPI interface in the com.ibm.uddi.promoter package.	Start using the PromoterAPI interface in the com.ibm.uddi.promoter package in place of these low-level APIs, which will be removed in a subsequent release 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	The methods are replaced as follows: getPoolContents and getAllPoolContents are replaced with showPoolContents and showAllPoolContents. ConnectionManager interface is replaced with J2EE Connector Architecture 1.5 LazyAssociatableConnectionManager interface. ConnectionEventListener interface is replaced with J2EE Connector Architecture 1.5 LazyEnlistableConnectionManager interface. For container-managed authentication aliases, specify the container-managed credentials in the resource binding information for the application.
	ApplicationProfile property on the Work manager panel in the administrative console	Read the articles in the Application profiling section for the differences between application profiling in v5.x and v6.0.x.
	The following item from the Data source panel in the administrative console: DefaultPrincipleMapping	Define the DefaultPrincipleMapping property on the Resource Reference.
	All classes in the com.ibm.websphere.servlet.filter package, including the following: ChainedRequest ChainedResponse ChainerServlet ServletChain	Rearchitect the 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 us to achieve chaining functionality, as well as embellishing and truncating responses.
Application services	Multipurpose Internet Mail Extensions (MIME) filtering MIME filters were first introduced in WAS Version 3.5 as a way for servlets to embellish, truncate, and modify the responses generated by other servlets, based on the IME 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 of the functionality of MIME filters. javax.servlet.filters are standard APIs, and are supported by all compliant application servers. Refer to the Servlet 2.3 specification or Servlet filtering for more information.
	Container-managed persistence (CMP) entity beans configured with method level access intent might run into data access problems, like deadlock. Therefore, the method level access intent is deprecated.	Reconfigure CMP entity beans to use bean level access intent, or reconfigure application profiles with WAS Toolkit.
	All of 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), we should now use the following methods in the WASDirectory class to get that information: com.ibm.websphere.product.WASDirectory.getName(String) com.ibm.websphere.product.WASDirectory.getVersion(String) com.ibm.websphere.product.WASDirectory.getBuildLevel(String) com.ibm.websphere.product.WASDirectory.getBuildDate(String)
	Data access beans, which are included with WAS in the databeans.jar file	Instead of using data access beans, 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, we should use the reload enable and interval options provided during application deployment. Read Enterprise application settings for additional details.
	com.ibm.websphere.servlet.session.UserTransactionWrapper API	There is no replacement for this API. The UserTransaction object can be placed directly into the HTTP session without using a wrapper.
Security	SOAP-Security (XML digital signature) based on Apache SOAP implementation	Instead of using SOAP-Security, we should migrate the application to JSR-109 implementation of web service. Also, migrate (reconfigure the application) to use WSS (Web Services Security) 1.0 implementation.
	Web Service Security (WSS) draft 13 specification-level support	Applications should be migrated to the supported WSS 1.0 standard. The draft-level support does not provide interoperability with some third-party vendors, as the message level has been changed between the draft and the WSS 1.0 implementation. WSS 1.0 is only supported in J2EE 1.4 applications. Therefore, we need to migrate applications to J2EE 1.4 first. The next step is to use Application Server Toolkit or Rational Application Developer tooling to reconfigure WSS for the migrated application. There is no automatic migration of WSS in this release of Application Server Toolkit or Rational Application Developer tooling for 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 Version 6.0.
System administration	Configure resources under cell scope	We should configure resources under cluster scope instead. In previous releases, we configured cell scope resources to allow the cluster members to share the resource configuration definition. In v6, 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 Version 4.0 to programmatically gather performance data from WAS	The Java Management Extension (JMX) interface, which is part of the J2EE specification, is the recommended way to gather WAS performance data. PMI data can be gathered from the J2EE-managed object message beans, or from the WebSphere PMI Perf message bean. While the J2EE message beans provide performance data about a specific component, the Perf message bean acts as a gateway to the WAS PMI service, and provides access to the performance data for all of the components.

Category	Deprecation	Recommended Migration Action
Application programming model and container support	Support for the following tsx tags in the JavaServer Pages (JSP) engine: repeat dbconnect dbquery getProperty userid passwd dbmodify	Instead of using the tsx tags, we should use equivalent tags from the JavaServer Pages Standard Tag Library (JSTL). JSTL is supported in WAS v6.0, and the tag library is included with the product. Use this table as a guideline for converting tsx tags to JSTL tags: tsx tag JSTL tag tsx:repeat c:forEach tsx:dbconnect sql:setDataSource tsx:dbquery sql:query tsx:getProperty Use standard EL syntax; c:out value="${book.title}" for example, where book is the current index in the result set tsx:userid Use the user attribute of the setDataSource tag tsx:passwd Use the password attribute of the setDataSource tag tsx:dbmodify sql:update
	The following backend IDs: SQL92 (1992 SQL Standard) SQL99 (1999 SQL Standard)	Use other backend IDs.
Application services	JRas Extensions API No further enhancements are planned for JRas support.	Use the equivalent function in the java.util.logging package (JSR47).
	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 Version 5.x. Users do not need to take any specific actions and can continue to use the v2 EJB API; however, they should be aware that it does not include any UDDI functionality that is new to UDDI Version 3 and the interface might be removed in a subsequent release of WAS.
	The UDDI4J v2 class library, the uddi4jv2.jar file	Start using the Version 3 UDDI APIs. A client library is provided to simplify constructing and sending UDDI Version 3 requests from Java. This is the IBM UDDI Version 3 Client for Java, provided in uddiv3client.jar. The UDDI4J APIs can still be used; however, we should be aware that they do not provide access to any of the new UDDI Version 3 functionality and they might be removed in a subsequent release of WAS.
	All of the low-level UDDI Utility Tools (UUT) APIs, such as BusinessStub, ServiceStub, and so on, These APIs are all replaced with the high-level PromoterAPI interface in the com.ibm.uddi.promoter package.	Start using the PromoterAPI interface in the com.ibm.uddi.promoter package in place of these low-level APIs, which will be removed in a subsequent release 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	The methods are replaced as follows: getPoolContents and getAllPoolContents are replaced with showPoolContents and showAllPoolContents. ConnectionManager interface is replaced with J2EE Connector Architecture 1.5 LazyAssociatableConnectionManager interface. ConnectionEventListener interface is replaced with J2EE Connector Architecture 1.5 LazyEnlistableConnectionManager interface. For container-managed authentication aliases, specify the container-managed credentials in the resource binding information for the application.
	ApplicationProfile property on the Work manager panel in the administrative console	Read the articles in the Application profiling section for the differences between application profiling in v5.x and v6.0.x.
	The following item from the Data source panel in the administrative console: DefaultPrincipleMapping	Define the DefaultPrincipleMapping property on the Resource Reference.
	All classes in the com.ibm.websphere.servlet.filter package, including the following: ChainedRequest ChainedResponse ChainerServlet ServletChain	Rearchitect the 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 us to achieve chaining functionality, as well as embellishing and truncating responses.
Application services	Multipurpose Internet Mail Extensions (MIME) filtering MIME filters were first supported in WAS Version 3.5 as a way for servlets to embellish, truncate, and modify the responses generated by other servlets, based on the IME types of the output content.	The javax.servlet.filters, which were introduced in the Servlet 2.3 specification, allow users to plug in filters that can intercept requests to and responses from servlets. They also have the capability to modify content flowing in either direction. The javax.servlet.filters maintain all of the functionality of MIME filters. javax.servlet.filters are standard APIs, and are supported by all compliant application servers. Refer to the Servlet 2.3 specification or Servlet filtering for more information.
	Container-managed persistence (CMP) entity beans configured with method level access intent might run into data access problems, like deadlock. Therefore, the method level access intent is deprecated.	Reconfigure CMP entity beans to use bean level access intent, or reconfigure application profiles with WAS Toolkit.
	All of the methods and fields in the com.ibm.websphere.product.product and com.ibm.websphere.product.buildInfo classes Therefore, the following methods from com.ibm.websphere.product.WASProduct class (which involves com.ibm.websphere.product.product and com.ibm.websphere.product.buildInfo objects) are deprecated: public product getProductByFilename(String basename) public product getProductById(String id) public boolean productPresent(String id) public boolean addProduct(product aProduct) public boolean removeProduct(product aProduct) public Iterator getProducts() public Iterator getProductNames() public String loadVersionInfoAsXMLString(String filename) public String getProductDirName() public static String computeProductDirName()	Use the following supported methods from com.ibm.websphere.product.WASDirectory: public WASProductInfo getWASProductInfo(String id) public boolean isThisProductInstalled(String id) public WASProductInfo[] getWASProductInfoInstances() public String getWasLocation() Also, instead of getting product information (name, version, build level, build date) from the old WASProduct API (com.ibm.websphere.product.WASProduct), we should now use the following methods in the WASDirectory class to get that information: com.ibm.websphere.product.WASDirectory.getName(String) com.ibm.websphere.product.WASDirectory.getVersion(String) com.ibm.websphere.product.WASDirectory.getBuildLevel(String) com.ibm.websphere.product.WASDirectory.getBuildDate(String)
	Data access beans, which are included with WAS in the databeans.jar file	Instead of using data access beans, we should use Service Data Objects (SDO). Read Service Data Objects for additional details.
	reloadInterval and reloadingEnabled attributes of the IBM deployment descriptor extensions, including both the WAR file extension (WEB-INF/ibm-web-ext.xmi) and the application extension (META-INF/ibm-application-ext.xmi).	Instead of using deployment descriptor extensions, we should use the reload enable and interval options provided during application deployment. Read Enterprise application settings for additional details.
	com.ibm.websphere.servlet.session.UserTransactionWrapper API	There is no replacement for this API. The UserTransaction object can be placed directly into the HTTP session without using a wrapper.
Security	SOAP-Security (XML digital signature) based on Apache SOAP implementation	Instead of using SOAP-Security, we should migrate the application to JSR-109 implementation of web service. Also, migrate (reconfigure the application) to use WSS (Web Services Security) 1.0 implementation.
	Web Service Security (WSS) draft 13 specification-level support	Applications should be migrated to the supported WSS 1.0 standard. The draft-level support does not provide interoperability with some third-party vendors, as the message level has been changed between the draft and the WSS 1.0 implementation. WSS 1.0 is only supported in J2EE 1.4 applications. Therefore, we need to migrate applications to J2EE 1.4 first. The next step is to use Application Server Toolkit or Rational Application Developer tooling to reconfigure WSS for the migrated application. There is no automatic migration of WSS in this release of Application Server Toolkit or Rational Application Developer tooling for 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 Version 6.0.
	Secure Authentication Service (SAS) IIOP security protocol	Use the CSIv2 protocols.
	Secure Authentication Service (SAS) CORBA security programming APIs	Migrate from the SAS programming APIs to the JAAS. For information on this migration, read Migrate Common Object Request Broker Architecture programmatic login to JAAS (CORBA and JAAS).
System administration	Configure resources under cell scope	We should configure resources under cluster scope instead. In previous releases, we configured cell scope resources to allow the cluster members to share the resource configuration definition. In v6, 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 Version 4.0 to programmatically gather performance data from WAS	The Java Management Extension (JMX) interface, which is part of the J2EE specification, is the recommended way to gather WAS performance data. PMI data can be gathered from the J2EE-managed object message beans, or from the WebSphere PMI Perf message bean. While the J2EE message beans provide performance data about a specific component, the Perf message bean acts as a gateway to the WAS PMI service, and provides access to the performance data for all of 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 our existing filters with a combination of JAX-RPC handlers and service integration bus mediations.
Application services	The following Java Database Connectivity (JDBC) drivers: Microsoft SQL Server 2000 Driver for JDBC SequeLink JDBC driver for Microsoft SQL Server	If we are using either of these JDBC drivers and still want to use Microsoft SQL Server as the database, switch to the Connect JDBC driver. We can purchase the Connect JDBC driver from DataDirect Technologies.

Features deprecated in v5.1

Category	Deprecation	Recommended Migration Action
Installation and migration tools	The Application Assembly Tool used for developing J2EE applications is replaced with the Assembly Tool component of the Application Server Toolkit.	Instead of running the Application Assembly Tool, users will install and run the Assembly Toolkit component of the Application Server Toolkit. The Application Server Toolkit is based on the Eclipse framework. On starting the Application Server Toolkit, the J2EE function is found by opening the J2EE Perspective.
	Business processes modeled with WebSphere Studio Application Developer Integration Edition 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 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 subsequent releases.	Go to the JDOM website, get the latest copy of JDOM, and bundle it inside the 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 Support is no longer available for the Common Object Request Broker Architecture (CORBA) C++ Developer Kit. The CORBA technology is a bridge for migration to a Java 2 Platform Enterprise Edition (J2EE) and WAS environment. In addition to the preceding information, the CORBA C++ client feature will be removed from the Application Clients installation image in subsequent releases.	IBM recommends that customers migrate to the Object Request Broker (ORB) service for Java technology that ships with WAS. However, there is no equivalent J2EE functionality for the C++ security client or the C++ value-type library. Customers that require such functionality must provide or develop their own. For information on the ORB service for Java technology, read 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 WASs CORBA Interoperability white paper
	IBM Cloudscape v5.1.x	Use the Cloudscape Network Server JDBC driver.
Server	IBM HTTP Server (IHS) Version 1.3.x	If we are using IHS Version 1.3.x with modules that: are included as part of IHS Version 1.3.x packages, we 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, we need to port these modules to the new IHS/Apache 2 API.
Application programming model and container support	Bean Scripting Framework (BSF) JavaServer Pages (JSP) execution and debugging functionality	The functionality will need to be rearchitected if we are using the JavaScript, Tcl, and Python languages. If using BSF scripting in our own custom applications, they will be unaffected. Custom scripts written for the WAS administrative console will also be unaffected. This functionality will continue to exist in WAS v5.1 and succeeding releases until Version 6.0. If debugging JSP files, we might have to restart the application server during JavaScript debugging sessions.
	The following Business Rule Bean classes, methods, and attributes: Public classes: com.ibm.websphere.brb.RuleImporter com.ibm.websphere.brb.RuleExporter Public method: getLocalRuleManager() on class com.ibm.websphere.brb.TriggerPoint Protected attribute: ruleMgr on class com.ibm.websphere.brb.TriggerPoint	Users do not have to take any action.
	Data access programming interfaces in com.ibm.websphere.rsadapter. Relational resource adapter interface: (com.ibm.websphere.rsadapter). Methods are deprecated in the following types: com.ibm.websphere.rsadapter.OracleDataStoreHelper public void doSpecialBLobWork(ResultSet rset, InputStream[] data, String[] blobColumnNames) public String assembleSqlString(String[] blobColumnNames, StringBuffer whereClause, String[] varValues, String tableName)	These relational resource adapter deprecated methods do not impact the application. You will not need to implement these deprecated methods in their subclasses if we have the subclass of OracleDataStoreHelper class. Those deprecated methods will not be called by the WAS 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. Previous method signature public String getStackTrace(); // returns a String representation of the exception stack New method signature (Java Development Kit 1.4, WAS 5.1) public StackTraceElement[] getStackTrace(); // returns an array of stack trace elements Replacement method (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 we are using com.ibm.websphere.servlet.error.ServletErrorReport.getStackTrace() and expecting a return type of String, we need to change the application to use the replacement method.
Application services	Data access binaries -- Common Connector Framework, including the following JAR files: ccf.jar ccf2.jar recjava.jar eablib.jar	The J2EE Connector Architecture solution should be used instead of the Common Connector Framework. For more information on the usage (tools and runtime) of the J2EE Connector Architecture read Accessing data using Java EE Connector Architecture connectors.
	Setting the XA partner log directory using the TRANLOG_ROOT variable	The setting currently stored in the TRANLOG_ROOT variable (if any) will need to be added to the Transaction Service panel for all servers that need to use the XA partner log. If the default location is to be used, then no action is required. The Transaction Service panel can be found on the administrative console by selecting Application Servers, choosing the application server to be modified, and selecting Transaction Service on the panel 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, we should now use one of the following methods to get the Subject containing the WSCredential: The RunAs Subject is the Subject used for outbound requests. The Caller subject is the Subject that represents the authenticated caller for the current request. The methods to use to get the runAs and caller subjects are as follows: com.ibm.websphere.security.auth.WSSubject.getRunAsSubject() and com.ibm.websphere.security.auth.WSSubject.getCallerSubject() respectively.
	The following elements in the security programming interface: The interface is deprecated in com.ibm.websphere.security.auth.WSSecurityContext. The exception is deprecated in com.ibm.websphere.security.auth.WSSecurityContextException. The class is deprecated in com.ibm.websphere.security.auth.WSSecurityContextResult.	Use Java Authentication and Authorization Service (JAAS) for all authentication related functionality.
	Integrated Cryptographic Services Facility (ICSF) authentication mechanism	Use the LTPA mechanism. For more information, read LTPA.
System administration	The following class: com.ibm.websphere.rsadapter.DB2390DataStoreHelper	If we currently use the DB2390DataStoreHelper class for the DB2 Legacy CLI-based provider when we are accessing data, you should now use the DB2DataStoreHelper class. If we currently use the DB2390DataStoreHelper class for the DB2 Universal JDBC provider when we are accessing data, we should now use the DB2UniversalDataStoreHelper class.

Features deprecated in v5.0.2

(ZOS)

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 Migrate Apache SOAP web services to JAX-RPC web services based on Java EE 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 we 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 we 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.

(iSeries) (Dist)

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 Migrate Apache SOAP web services to JAX-RPC web services based on Java EE 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 we 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.
	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 we 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 we 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 v5.x methods in com.ibm.websphere.ServletErrorReport
Security	com.ibm.websphere.security.CustomRegistry interface	Use the com.ibm.websphere.security.UserRegistry interface.
Performance	Performance Monitoring Infrastructure -- Various v5.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).

Deprecated, stabilized, and removed features of WAS traditional

Stabilized features of WAS traditional

Removed features of WAS traditional