If you are migrating 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.
If a feature is listed as deprecated in Deprecated features, IBM® might remove this capability in a subsequent release of the product. Future investment will be focussed on the strategic function listed under "Recommended Migration Actions" in Deprecated features. Typically, a feature is not removed until at least two major releases or three full years (whichever time period is longer) after the release in which that feature is deprecated. For example, features that are deprecated in Version 6.0, Version 6.0.1, or Version 6.0.2 are not removed from the product until after Version 7.0 because both Version 6.0.x and Version 6.1.x are major releases. In rare cases, it might become necessary to remove features sooner; such cases are indicated clearly and explicitly in the descriptions of these deprecated features in Deprecated features.
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.
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 2005 JDBC driver. Review Data source minimum required settings, by vendor for specific JDBC providers. Read the "Migrating from the WebSphere Connect JDBC driver" article in the information center. |
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.
Use the z/OS Migration Management Tool
or the zmmt command to generate migration definitions.
Note: Both the Profile Management Tool (z/OS only)
and the z/OS Migration Management Tool are contained
in WebSphere Customization Tools Version 7.0.
Read the "Installing and updating WebSphere Customization
Tools" article in the information center.
|
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.MSSQLDataStoreHelper 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: |
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 2005 JDBC driver. Review Data source minimum required settings, by vendor for specific JDBC providers. Read the "Migrating from the WebSphere Connect JDBC driver" article in the information center for information on using the WebSphereConnectJDBCDriverConversion command to convert data sources from the WebSphere Connect JDBC driver to the DataDirect Connect JDBC driver or the Microsoft SQL Server 2005 JDBC driver.. |
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.MSSQLDataStoreHelper 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: |
Feature | Recommended Migration Action |
---|---|
com.ibm.websphere.security.CustomRegistry interface | Use the com.ibm.websphere.security.UserRegistry
interface. For more information, read Migrating custom user registries. |
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 IBM Cloudscape Version
10.1 database. This database provides Derby Version 10.1 binaries, NLS enablement, QA, and IBM problem support. Tthe term "Derby" rather than "Cloudscape" is used in places such as the administrative console, the ejbdeploy command, and others. |
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 Web site, and get the latest copy of Rhino. |
Java Document Object Model (JDOM) | Use the code available from the JDOM organization. Go to the JDOM Web site, 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 Information Center. |
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. |
The following Multiple Virtual Storage (MVS)
console display commands related to existing sessions: |
Modify all automation or other processing that
uses these commands to use the following new set of commands: |
The following configuration variables: |
No migration action is necessary. |
Feature | Recommended Migration Action |
---|---|
com.ibm.websphere.security.CustomRegistry interface | Use the com.ibm.websphere.security.UserRegistry
interface. For more information, read Migrating custom user registries. |
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 IBM Cloudscape Version
10.1 database. This database provides Derby Version 10.1 binaries, National Language Support (NLS) enablement, quality assurance, and product support. The term "Derby" rather than "Cloudscape" is used in places such as the administrative console, the ejbdeploy command, and others. |
Profile creation wizard | Use the Profile Management tool. For information on using the Profile Management tool to create a profile, read Managing profiles 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 Web site, and get the latest copy of Rhino. |
Java Document Object Model (JDOM) | Use the code available from the JDOM organization. Go to the JDOM Web site, 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. |
Component | Classes and Interfaces |
---|---|
Activity | com.ibm.ws.activity.ActivityConstants |
ALS | com.ibm.websphere.als.BufferManager |
Ant tasks | com.ibm.websphere.ant.tasks.endptEnabler.Property |
Asynchronous Beans APIs | com/ibm/websphere/asynchbeans/pmi/AlarmManagerPerf.java |
Dynacache | com.ibm.websphere.servlet.cache.CacheConfig |
Management | com.ibm.websphere.management.application.EarUtils |
ObjectPool APIs | com/ibm/websphere/objectpool/pmi/ObjectPoolPerf.java |
RAS | com.ibm.ras.RASConsoleHandler |
Scheduler API | com.ibm.websphere.scheduler.pmi.SchedulerPmiModule |
Security | com.ibm.websphere.security.AuthorizationTable |
Userprofile | com.ibm.websphere.userprofile.UserProfile |