Removed features

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

WebSphere Application Server uses the following naming scheme:
V.R.M.F
where
  • V = version
  • R = release
  • M = modification
  • F = fix pack
For example, 8.5.0.1 refers to version 8, release 5, modification 0, and fix-pack 1. It is also common to use "version" to prefix a particular release, modification, or fix pack—"version 8.5" when referring to a release, for example, or "version 8.5.0.1" when referring to a fix pack.

If a feature is listed in Deprecated features 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 in Deprecated features. 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 features in this article.

If a removal notice is issued for an item, the item can be removed in a future release, typically two years from the time the notice was issued.

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

Features removed in Version 8.5

Table 1. Features removed in Version 8.5 . This table describes the features that are removed in Version 8.5.
Feature Recommended Migration Action
[8.5.5.23 or later]DataPower® appliance manager DataPower appliance manager was deprecated in WebSphere Application Server Version 8.0, which supported the following appliances:
  • 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 Lifecycle dates for IBM DataPower and IBM MQ appliances.

New appliances not on the previous list are managed through a separate DataPower appliance management offering that is also capable of managing existing appliances.
Java SE 6 and Java SE 7 support

Removal of Java™ SE 6 and 7 support aligns with the announced end of service date for the IBM SDK and JRE for Java 6 and Java 7. For more information, see IBM SDK, Java Technology Edition and IBM developer kits lifecycle dates.

For WebSphere Application Server full profile, install the IBM Java 8 SDK for your operating system, and use the managesdk command to change the SDK that your product profiles use. For more information, see Migrating to Java Platform, Standard Edition 7 or 8.

For Liberty, use a more recent Java SDK or Java runtime environment (JRE). Liberty can run with any supported and compliant Java SDK or JRE, including IBM Java SDKs.
[8.5.5.17 or later] IBM Portlet Bridge for JavaServer Faces (JSF) 2.0 IBM Portlet Bridge for JavaServer Faces (JSF) 2.0 only applies for WebSphere Application Server versions before Version 8.5.5.17.
The waslogbr and wcslogbr tools, and associated scripts to launch the tools No migration action is necessary. Log files can be viewed using the administrative console or any text editor.
The asynchronous administrative procedure and the RACF® definitions for the asynchronous administrative user ID in the customization jobs that are generated by the Profile Management Tool for z/OS® when configuring WebSphere Application Server Version 8.5 No migration action is necessary.
Support for the IBM WebSphere Application Server Feature Pack for Dynamic Scripting Migrate IBM WebSphere sMash applications to the Liberty profile, where they can take advantage of the small-footprint runtime and industry-standard RESTful services using JAX-RS as well as gain access to significant updates in DOJO support.
Intelligent Management support for configuring the following middleware server types using the administrative console:
  • Apache Tomcat
  • BEA WebLogic
  • JBoss
  • External WebSphere application server (application servers that run outside the Intelligent Management cell)
 Use wsadmin scripting to manage these resources.

Features removed in Version 8.0

[z/OS]
Table 2. Features removed in Version 8.0 . This table describes the features that are removed in Version 8.0.
Feature Recommended Migration Action
Apache SOAP channel in web services gateway Gateway services should be deployed to the SOAP HTTP channel instead of the Apache SOAP channel. The endpoint (URL) of the service will be different for this channel; and therefore ,client programs that are talking to the gateway will need to use the new service endpoint.
Apache SOAP, WEBSJAVA.SOAP
  • soap.jar
  • wssoap.jar
 Migrate web services that were developed using Apache SOAP to Java API for XML-based RPC (JAX-RPC) web services that are developed based on the Web Services for Java Platform, Enterprise Edition (Java EE) specification.

See Migrating Apache SOAP web services to JAX-RPC web services based on Java EE standards for more information.
The following classes and fields of the WebSphere relational resource adapter:
  • Class com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper
  • Field com.ibm.websphere.rsadapter.DataStoreHelper.ORACLE_10G_HELPER
  • Class com.ibm.websphere.rsadapter.OracleDataStoreHelper
  • Field com.ibm.websphere.rsadapter.DataStoreHelper.ORACLE_HELPER
 If you are using the Oracle10gDataStoreHelper, ORACLE_10G_HELPER, OracleDataStoreHelper, or ORACLE_HELPER, switch to the Oracle 11g JDBC driver and use the Oracle11gDataStoreHelper or ORACLE_11G_HELPER instead.
The protocol_http_transport_class_mapping_file configuration variable that specifies the transaction class mapping file name
Note: This is a removal for Version 8 and later servers only. This variable is still supported and deprecated for any downlevel servers (Version 7 and earlier) that Version 8 manages.
 Use the wlm_classification_file configuration variable to specify the name of the XML file that maps HTTP requests to WLM transaction classes.

Features removed in Version 7.0

[z/OS]
Table 3. Features removed in Version 7.0 . This table describes the features that are removed in Version 7.0.
Feature Recommended Migration Action
Support for the following interfaces:
  • Java Virtual Machine Profiler Interface (JVMPI)
  • Java Virtual Machine Debug Interface (JVMDI)
 Use the Java Virtual Machine Tool Interface (JVMTI).

For more information, read JVM Tool Interface (JVMTI).
All classes in the com.ibm.websphere.servlet.filter package:
  • ChainedRequest
  • ChainedResponse
  • ChainerServlet
  • ServletChain
 Rearchitect your applications to use javax.servlet.filter classes rather than com.ibm.websphere.servlet.filter classes. Starting from the Servlet 2.3 specification, javax.servlet.filter classes give you the capability to intercept requests and examine responses. You can also chain functionality as well as embellish and truncate responses.
Integrated Cryptographic Services Facility (ICSF) authentication mechanism Use the Lightweight Third-Party Authentication (LTPA) mechanism.

For more information, read Lightweight Third Party Authentication.
The following Java Database Connectivity (JDBC) drivers:
  • WebSphere Connect JDBC driver
  • Microsoft SQL Server 2000 Driver for JDBC
  • WebSphere SequeLink JDBC driver for Microsoft SQL Server
 Use the DataDirect Connect JDBC driver or Microsoft SQL Server JDBC driver.

Review Data source minimum required settings, by vendor for specific JDBC providers.

Read the Migrating from the WebSphere Connect JDBC drive topic.
Customization Dialog, the set of Interactive System Productivity Facility (ISPF) panels used to create jobs and instructions for configuring and migrating the WebSphere Application Server for z/OS environment
Use the Profile Management Tool or the zpmt command to generate the jobs and instructions for creating profiles.
  • For information on using the Profile Management Tool, read the Configuring z/OS application-serving environments with the Profile Management Tool topic.
  • For information on using the zpmt command, read the Configuring z/OS application-serving environments with the zpmt command topic.
Use the z/OS Migration Management Tool or the zmmt command to generate migration definitions.
  • For information on using the z/OS Migration Management Tool, read the Using the z/OS Migration Management Tool to create and manage migration definition topic.
  • For information on using the zmmt command, read the Using the zmmt command to create migration definitions topic.
Support for the DB2® legacy CLI-based Type 2 JDBC Driver and the DB2 legacy CLI-based Type 2 JDBC Driver (XA)

For more information, read Support for DB2 legacy CLI-based Type 2 JDBC Drivers is removed from IBM WebSphere Application Server Version 7.0.

 Use the DB2 Universal JDBC Driver.
mb2mdb command-line utility No migration action is necessary.
Web services gateway customization API

Replace your existing filters with a combination of JAX-RPC handlers and service integration bus mediations.
com.ibm.websphere.servlet.session.UserTransactionWrapper class Store a UserTransaction directly into the HTTP session without wrapping it in the removed class.
com.ibm.websphere.rsadapter.DataDirectDataStoreHelper class Use the com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper class.
com.ibm.websphere.rsadapter.MSSQLServerDataStoreHelper class Use the com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper class.
Derby Network Server Provider using the Universal JDBC driver Use the Derby Network Server using Derby Client instead.

For more information, read JDBC providers.
Support for the following custom properties:
  • com.ibm.security.SAF.unauthenticatedId
  • com.ibm.security.SAF.useEJBROLEAuthz
  • com.ibm.security.SAF.useEJBROLEDelegation
 Use the following custom properties that are specified on the SAF authorization options panel:
  • com.ibm.security.SAF.unautheticated
  • com.ibm.security.SAF.authorization
  • com.ibm.security.SAF.delegation

Features removed in Version 6.1

[z/OS]
Table 4. Features removed in Version 6.1 . This table describes the features that are removed in Version 6.1.
Feature Recommended Migration Action
com.ibm.websphere.security.CustomRegistry interface Use the com.ibm.websphere.security.UserRegistry interface.
Support for the z/OS Secure Authentication Service (z/SAS) IIOP security protocol Use the Common Secure Interoperability Version 2 (CSIv2) protocols.
Support for the Common Connector Framework (CCF) Use the J2EE Connector Architecture (JCA) solution.

For information on using the J2EE Connector Architecture, read Accessing data using Java EE Connector Architecture connectors.
Support for the IBM Cloudscape Version 5.1.x database Use the Apache Derby database.
Log Analyzer, the tool that was previously provided for viewing and analyzing the activity or service log file Use the Log and Trace Analyzer tool for Eclipse in the Application Server Toolkit. This tool is installable from the Application Server Toolkit launchpad console.
Mozilla Rhino JavaScript (js.jar) Use the Rhino code available from Mozilla.

Go to the Rhino: JavaScript for Java website, and get the latest copy of Rhino.
Java Document Object Model (JDOM) Use the code available from the JDOM organization.

Go to the JDOM website, get the latest copy of JDOM, and bundle it inside your application.
DB2 for zOS Local JDBC Provider (RRS) Use the DB2 Universal JDBC Driver Provider.

For more information, read Using the DB2 Universal JDBC Driver to access DB2 for z/OS for more information. Also read Migrating from the JDBC/SQLJ Driver for OS/390® and z/OS to the DB2 Universal JDBC Driver in the Information Management Software for z/OS Solutions documentation.
Class preloading function No migration action is necessary.
The following samples from the Samples Gallery:
  • Adventure Builder
  • Greenhouse by WebSphere
  • WebSphere Bank
The following technology samples from the Samples Gallery:
  • Bean-Managed Persistence (BMP)
  • Container-Managed Persistence (CMP) 1.1
  • Container-Managed Persistence (CMP) 2.1
  • Container-Managed Relationships (CMR)
  • EJB Time
  • Filter Servlet
  • JavaServer Pages (JSP) 2.0
  • Message-Driven Beans (MDB)
  • Pagelist Servlet
  • Simple JavaServer Pages (JSP)
  • Simple Servlet
  • Stateful Session
  • TagLib
 No migration action is necessary.
The following Multiple Virtual Storage (MVS™) console display commands related to existing sessions:
  • DISPLAY,SESSIONS
  • DISPLAY,SESSIONS,LISTENERS
  • DISPLAY,SESSIONS,SERVER
  • DISPLAY,SESSIONS,SERVER,TCPIIOP
  • DISPLAY,SESSIONS,SERVER,TCPIIOP,LIST
  • DISPLAY,SESSIONS,SERVER,LOCALIIOP
  • DISPLAY,SESSIONS,SERVER,LOCALIIOP,LIST
  • DISPLAY,SESSIONS,SERVER,SSLIIOP
  • DISPLAY,SESSIONS,SERVER,SSLIIOP,LIST
  • DISPLAY,SESSIONS,SERVER,HTTP
  • DISPLAY,SESSIONS,SERVER,HTTP,LIST
  • DISPLAY,SESSIONS,SERVER,HTTPS
  • DISPLAY,SESSIONS,SERVER,HTTPS,LIST
 Modify all automation or other processing that uses these commands to use the following new set of commands:
  • DISPLAY,LISTENERS
  • DISPLAY,CONNECTIONS
  • DISPLAY,CONNECTIONS,NAME='name'
  • DISPLAY,CONNECTIONS,LIST
  • DISPLAY,CONNECTIONS,LIST,NAME='name'
The following configuration variables:
  • com_ibm_userRegistries_type
  • com_ibm_userRegistries_LDAPUserRegistry_ realm
  • com_ibm_userRegistries_CustomUserRegistry_ realm
  • control_region_ssl_thread_pool_size
  • control_region_security_enable_trusted_ applications
  • nonauthenticated_clients_allowed
  • security_zSAS_ssl_repertoire
  • security_sslType1
  • security_sslClientCerts_allowed
  • security_kerberos_allowed
  • security_userid_password_allowed
  • security_userid_passticket_allowed
  • security_assertedID_IBM_accepted
  • security_assertedID_IBM_sent
  • protocol_http_max_keep_alive_connections
  • protocol_http_max_connect_backlog
  • protocol_https_transport_class_mapping_file
  • protocol_https_max_keep_alive_connections
  • protocol_https_max_connect_backlog
  • protocol_iiop_no_local_copies
 No migration action is necessary.

Features removed in Version 6.0

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