API and specification migration

Migrating application programming interfaces (APIs) and specifications involves moving to the current Java component level as well as to other technologies that WebSphere Application Server Version 6.1 supports. If your existing applications currently support different specification levels than are supported by this version of the product, it is likely that you must update at least some aspects of the applications to comply with the new specifications.

In many cases, IBM provides additional features and customization options that extend the specification level even further. If your existing applications use IBM extensions from earlier product versions, it might be necessary for you to perform mandatory or optional migration to use the same kinds of extensions in Version 6.1.

The following table summarizes potential migration areas.
Functional area Support in Version 5.0.x Support in Version 5.1 Support in Version 6.0.x Support in Version 6.1.x Migration details
Enterprise JavaBeans (EJB) EJB 2.0 EJB 2.0 EJB 2.1 EJB 2.1 Full support for EJB 2.0 and 2.1 is provided.
Java Connector Architecture (JCA) JCA 1.0 JCA 1.0 JCA 1.5 JCA 1.5 Java 2 Connector support was completed in Version 6.0. Some changes might be necessary to take full advantage of this support.
Java Database Connectivity (JDBC) API JDBC 2.0 JDBC 2.0 JDBC 3.0 JDBC 3.0 Many applications can run unchanged in Version 6.1 although some changes might be required or recommended.
JavaServer Pages (JSP) JSP 1.2 JSP 1.2 JSP 2.0 JSP 2.0 For more information, see the "Web applications" article in the information center.
Security IBM security IBM security IBM security IBM security Changes might be required due to J2EE security.
Java Servlets Servlet 2.3 Servlet 2.3 Servlet 2.4 Servlet 2.4 Many Servlet 2.3 and 2.4 applications can run unchanged in Version 6.1 although changes might be required or recommended.
Sessions IBM sessions IBM sessions IBM sessions IBM sessions Many applications can run unchanged in Version 6.1 although changes might be required or recommended.
Transactions IBM transactions IBM transactions IBM transactions IBM transactions There was a change in the import statement in Version 6.0.x. Also, one datasource connection cannot be used across multiple user transactions.
Web services Apache SOAP 2.3 in Version 5.0 and 5.0.1; Web Services for J2EE 1.1 in Version 5.0.2 Web Services for J2EE 1.1 Web Services for J2EE 1.1 Web Services for J2EE 1.1 The Apache SOAP Web services support provided in WebSphere Application Server Version 5.0 and 5.0.1 was deprecated in Version 5.0.2 and is not supported in Version 6.1. Applications that are using this SOAP implementation should migrate to Web Services for J2EE.
XML parser XML4J 2.0.x XML4J 4.0.6 XML4J 4.3.x XML4J 4.4.x Changes to move to the supported API XML4J Version 4.4.x level are required.
Recompilation is required to migrate a Version 5.x XML application to the Version 6.x level.
XML transformer XSLT4J 2.5.4 XSLT4J 2.5.4 XSLT4J 2.6.x XSLT4J 2.7.x Changes are required to move to the supported XSLT4J 2.7.x transformer levels.
Notes on the use of JDK 5:
  • WebSphere Application Server began supporting JDK 5 in Version 6.1.
  • In general, existing Version 5.x and 6.0.x application binaries that were developed using JDK 1.3 or 1.4 are highly compatible and usually do not require modifications to run. However, recompilation of the JDK 1.3 or 1.4 applications at the JDK 5 level might necessitate modifications of the source code to conform to incompatible changes present in JDK 5. As part of your migration planning, you should review the JDK compatibility restrictions that are documented by Sun Microsystems at Java 2 Platform Standard Edition 5.0 Compatibility with Previous Releases.
  • A mixed cell containing Version 5.x or 6.0.x and Version 6.1 nodes requires that all application binaries remain at the lowest JDK level used. Although you can successfully migrate Version 5.x or 6.0.x applications to Version 6.1, this is only meant to be a temporary state as you transition to Version 6.1. After you begin migration to Version 6.1, you should plan to complete the migration of the entire cell, update your tooling to Version 6.1, and update your applications to conform to JDK 5 requirements. This should be done before any further application changes. After you have completely migrated your cell to Version 6.1, you should upgrade your application binaries to the JDK 5 level the next time you make application modifications that require recompiling. This might require source code changes to your application to conform to the JDK 5 API changes as documented by Sun Microsystems.
  • The com.ibm.net.ssl.* classes, including the com.ibm.net.ssl.TrustManager class, were deprecated in JDK 1.4 and removed in JDK 5.

    See IBM JSSE Provider Class Documentation: Package com.ibm.net.ssl and IBM J2SE 5 SDK: Security information for more information.




Related tasks
Migrating and coexisting
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=cmig_apispec
File name: cmig_apispec.html