Migrating API and specifications

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 7.0 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 7.0.

Notes on the use of Java SE Development Kit 6:
  • WebSphere Application Server began supporting Java SE Development Kit (JDK) 6 in Version 7.0.

    Read JSR 270: Java SE 6 Release Contents and Java SE 6 for more information about JDK 6.

  • In general, existing Version 5.1.x and 6.x application binaries that were developed using JDK 1.4 and 5 are highly compatible and typically do not require modifications to run. However, recompilation of the JDK 1.4 or 5 applications at the JDK 6 level might necessitate modifications of the source code to conform to incompatible changes that are present in JDK 6. As part of your migration planning, you should review the JDK compatibility restrictions that are documented by Sun Microsystems at Java SE 6 Release Notes®: Compatibility.
  • A mixed cell containing Version 5.1.x or Version 6.x and Version 7.0 nodes requires that all application binaries deployed on Version 5.1.x or Version 6.x remain at the lowest JDK level associated with the Version 5.1.x or Version 6.x nodes. Although you can successfully migrate Version 5.1.x or Version 6.x applications to Version 7.0, this is only meant to be a temporary state as you transition to Version 7.0. After you begin migration to Version 7.0, plan to complete the migration of the entire cell, update your tooling to Version 7.0, and update your applications to conform to JDK 6 requirements. Complete this action before any further application changes. After you have completely migrated your cell to Version 7.0, upgrade your application binaries to the JDK 6 level the next time that you make application modifications that require recompiling. This action might require source code changes to your application to conform to the JDK 6 API changes as documented by Sun Microsystems.
Deprecated feature: The Java Virtual Machine Debug Interface (JVMDI) and the Java Virtual Machine Profiler Interface (JVMPI) were deprecated in JDK 5 and removed in JDK 6. Read Java SE 6 Release Deprecated API for more information.depfeat

Read the "Specifications and API documentation" article in the information center for a summary of the specifications and API documentation supported in current and prior product releases.

For more information on the items deprecated in WebSphere Application Server Version 7.0, read the "Deprecated, stabilized, and removed features" article in the information center.




Related tasks
Migrating and coexisting application servers
Concept topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 2:45:02 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=cmig_apispec
File name: cmig_apispec.html