Migrating APIs and specifications

Migrating APIs and specifications involves moving to the current Java component level as well as to other technologies that WAS v6.x supports.

Migrating APIs and specifications also includes moving to the most contemporary open specification levels. If your existing applications currently support different specification levels than those supported by this product version, you should review your applications for required changes to comply with the new specifications.

The following table summarizes potential migration areas.

Functional area Support in V4.0.x Must migrate from V4.0.x? Must migrate from Version 5.x? Details
Enterprise beans EJB 1.0 Not applicable Not applicable Many EJB 1.0 applications can run unchanged in v6.x although some changes might be required or recommended. See Migrating enterprise bean code to the supported specification .
EJB 1.1 No No Full support for EJB 1.1 is provided. See Migrating enterprise bean code to the supported specification .
Java 2 Connectors Java 2 Connectors Yes No The preliminary Java 2 Connector support in V4.0 is completed in v6. Some changes might be necessary to take full advantage of this support. See Connection management architecture , Connection considerations when migrating servlets, JavaServer Pages, or enterprise session beans , and Data source settings .
Java Database Connectivity (JDBC) API JDBC API Not applicable No Many applications can run unchanged in v6.x although some changes might be required or recommended. See Migrating applications to use data sources of the current J2EE Connector Architecture (JCA) .
JSP files JSP 1.0 Specification No No JSP 1.0 APIs are a pure subset of JSP 1.2.
JSP 1.1 Specification No No JSP 1.1 APIs are a pure subset of JSP 1.2.
Security IBM security Yes No Changes might be required due to J2EE security. See Migrating, coexisting, and interoperating – Security considerations and Migrating Java 2 security policy .
Servlets Servlet 2.1 Specification and IBM extensions Yes No Many Servlet 2.1 applications can run unchanged in v6.x although changes might be required or recommended. See Developing servlets with WAS extensions .
Servlets Servlet 2.2 Specification No No Servlet 2.2 APIs are a pure subset of Servlet 2.3. See Developing servlets with WAS extensions .
Sessions IBM sessions Yes No Many applications can run unchanged in v6.x although changes might be required or recommended. See Developing session management in servlets .
Transactions IBM transactions No No A change in the import statement. Also, one datasource connection cannot be used across multiple user transactions. See Requirements for setting isolation level .
Web services Apache (SOAP) 2.2 Yes No Many applications can run unchanged although changes to use new support are recommended.
XML parser XML 2.0.x supported Not applicable Not applicable Changes to move to the supported API XML4J V4.0.6 level are required. See XML parser for Java code .
XML parser XML4J V3.1 Yes Not applicable Recompilation is required to convert to XML4J V4.0.6.
XML parser XML4J V4.0.6 Not applicable Yes Recompilation is required to convert to XML4J 4.2.2.
XML configuration tool XMLConfig Yes No Use the JMX support provided by wsadmin. See Migrating administrative scripts .
WebSphere Control Program WSCP Yes No Use the JMX support provided by wsadmin. See Migrating administrative scripts .
Notes on the use of JDK 1.4:


Related tasks
Migrating and coexisting

 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.