Removed features of WebSphere Application Server traditional
If you are migrating your configuration from an earlier release of WebSphere® Application Server traditional, review the various features that were removed from this and earlier releases.
- V = version
- R = release
- M = modification
- F = fix pack
If a feature is listed in Deprecated features of WebSphere Application Server traditional 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 of WebSphere Application Server traditional. Typically, a feature is not deprecated unless an equivalent alternative is provided. A feature is not removed until at least two full years from the release in which that feature is deprecated. 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 topic.
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 9.0
Feature | Recommended Migration Action |
---|---|
Centralized Installation Manager for Version 7.0 and earlier | Manually install, update, or uninstall the product. For new installations, install the product by running the install command. For updating the product with fix packs or interim fixes, use the Update Installer for WebSphere Software. For more information, see the documentation for that version of the product. Centralized Installation Manager for WebSphere Application Server Version 8.0 and later continues to be available. |
Communications Enabled Applications | There is no alternative for CEA. If you are deploying your application on Liberty, consider using the Rtcomm feature which provides a set of real-time communications tools. |
Common Event Infrastructure (CEI) module and all related application
programming interfaces (APIs) and files:
|
For applications that require event-based models, use Service Integration Bus
(SIBus). Design your applications to use SIBus-provided APIs for sending and receiving events. For
information about the com.ibm.websphere.sib APIs, see the IBM WebSphere Application Server API specification for Version 9.0. |
Edge Components: Load Balancer for IPv4 | Use the Edge Components: Load Balancer for IPv4 and IPv6. For information about how to migrate to Load Balancer for IPv4 and IPv6, see Migrate to Load Balancer IPv4 and IPv6. |
JavaServer Faces (JSF) 1.2 Sun Reference Implementation (RI) | Use the JSF 2.2 MyFaces implementation. For information about how to migrate to this implementation, see JavaServer Faces migration. |
Migration tools:
|
|
Pluggable Application Client | Use the IBM Thin Client for Enterprise JavaBeans. For more information, see Running the IBM Thin Client for Enterprise JavaBeans (EJB). |
Remote Installation Tool for IBM i (iRemoteInstall) | To install the product by using a GUI, use the IBM Web Administration for IBM
i GUI. . Alternatively, you can use the Installation Manager imclcommand or response files to install the produce and service from local or remote repositories. For more information, see Installing your application serving environment. |
Service Component Architecture (SCA) programming model and samples |
Update your applications to use different programming models. The programming models that you use vary depending on how you previously incorporated SCA in your application. If you used SCA for binding, consolidate the ways in which your application is exposed to a few standards, such as Java™ API for RESTful Web Services (JAX-RS) or Java Message Service (JMS). For example, use JAX-RS for application bindings; for more information, see Configuring JAX-RS web applications. To minimize the duplication of binding level implementation, structure your application to use shared code. If you want to continue to use SCA as part of your long-term strategy, consider hosting your applications on IBM Business Process Manager. |
Web 2.0 and Mobile Toolkit |
Note: The Web Messaging service, Ajax Proxy, and RPC Adapter application service, which are
installed with the product, were not removed but are deprecated. For information about recommended
alternatives for these items, see Deprecated features of WebSphere Application Server traditional.
|
WebSphere Customization Toolbox graphical user interface (GUI)
support on the HP-UX operating system Note: GUI support still available for other distributed
operating systems.
|
Instead of the Web Server Plug-ins Configuration Tool, use the wctcmd -tool pct command to configure your web server plug-in. For more information, see Configuring a web server plug-in using the pct tool. Instead of the Configuration Migration Tool, use a combination of the WASPreUpgrade, manageprofiles, and WASPostUpgrade command to migrate profiles. For more information, see Migrating, coexisting, and interoperating. Instead of the Profile Management Tool, use the manageprofiles command to create, delete, augment, back up, and restore profiles. For more information, see manageprofiles command. |
IBM Portlet Bridge for JavaServer Faces (JSF) 2.0 | IBM Portlet Bridge for JavaServer Faces (JSF) 2.0 only applies for WebSphere Application Server prior to Version 9.0.5.2. |
Features removed in Version 8.5
Feature | Recommended Migration Action |
---|---|
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. See information about migrating to Java Platform, Standard Edition 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. |
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. |
IBM Business Solutions applications on WebSphere Application Server Express® |
If you want to obtain a similar application that uses LDAP, you can purchase IBM Tivoli® Directory Server. There is no migration path from the IBM Business Solutions application provided in WebSphere Application Server to the alternative application provided in IBM Tivoli Directory Server. |
wasprofile command | Use the manageprofiles command. For more information, read manageprofiles command. |
crtjavapgm command | No migration action is necessary. |
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. |
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. |
Features removed in Version 8.0
Feature | Recommended Migration Action |
---|---|
Support for IBM Java Developer Kit for IBM i, which is also referred to as Classic JVM | Use IBM Technology for Java on IBM i, which includes IBM Java Standard Edition (SE) 32-bit and IBM Java SE 64-bit. |
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
|
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:
|
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. |
On a Windows platform, collocation for the dispatcher's MAC forwarding method. | Locate your web servers that were using collation to a different machine. |
Web server plug-in configuration scripts The following scripts were removed
on distributed operating systems:
|
Configure the web server plug-in by using the pct tool. To use the pct tool, run the
wctcmd.bat or wctcmd.sh script with Note: Since the introduction of the Plug-in Configuration Tool (PCT), several scripts that are
located in the web server plug-in's bin folder are no longer supported. If the (PCT) is available,
the use of the .sh and .bat configure plug-in scripts that are listed in the web server plug-in
configuration scripts column are no longer supported. For more information about PCT use, see Configuring a web server plug-in using the pct
tool.
|
Features removed in Version 7.0
Feature | Recommended Migration Action |
---|---|
Support for the following interfaces:
|
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:
|
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:
|
Use the DataDirect Connect JDBC driver or Microsoft SQL Server JDBC driver. Review Data source minimum required settings, by vendor for specific JDBC providers. |
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:
|
Use the following custom properties that are specified on the SAF
authorization options panel:
|
Features 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 Secure Authentication Service (SAS) IIOP security protocol | Use the Common Secure Interoperability Version 2 (CSIv2) protocols. |
Support for the Secure Authentication Service (SAS) CORBA security programming APIs | Migrate from the SAS programming APIs to the Java Authentication and Authorization Service (JAAS). For information on this migration, read Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service (CORBA and JAAS). |
Support for the Common Connector Framework (CCF) | Use the J2EE Connector Architecture (JCA) solution. For information on using the J2EE Connector Architecture, read Accessing data using Java EE Connector Architecture connectors. |
Support for the IBM Cloudscape Version 5.1.x database | Use the Apache Derby database. |
Profile creation wizard | Use the Profile Management tool. For information on using the Profile Management tool to create a profile, read Managing profiles by using the graphical user interface. |
Log Analyzer, the tool that was previously provided for viewing and analyzing the activity or service log file | Use the Log and Trace Analyzer tool for Eclipse in the Application Server Toolkit. 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. |
Class preloading function | No migration action is necessary. |
The following samples from the Samples Gallery:
The following technology samples from the Samples Gallery:
|
No migration action is necessary. |
Features 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 |