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.
This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.
sptcfgThe 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 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. |
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. 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 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.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:
|
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 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. |
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 file) | Use the Rhino code available from Mozilla. Go to the Rhino: JavaScript for Java website for the latest copy of Rhino. |
Java Document Object Model (JDOM) | Use the code available from the JDOM organization. Go to the JDOM website, download 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 |