Migrating APIs and specifications means moving to the current Java component level and to other technologies that IBM WebSphere Application Server Version 6.0 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, updating at least some aspects of the applications to comply with the new specifications is recommended.
Functional area | Support in V4.x | Must migrate from V4.x? | Must migrate from V5.x? | Details |
---|---|---|---|---|
Enterprise beans | EJB 1.0 | Not applicable | Not applicable | Many EJB 1.0 applications can run unchanged in Version 6 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.x is completed in V6. Some changes might be necessary to take full advantage of this support. See J2EE Connector Architecture migration tips, Connection management architecture, Connection considerations when migrating servlets, JavaServer Pages, or enterprise session beans, and Data source settings. |
JDBC API | JDBC API | Not applicable | No | Many applications can run unchanged in V6 although some changes might be required or recommended. See Migrating a Version 4.0 data access application to Version 6.0. |
JavaServer Pages (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 security configurations from previous releases 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 Version 6 although changes might be required or recommended. See Developing servlets with WebSphere Application Server extensions. |
Servlets | Servlet 2.2 Specification | No | No | Servlet 2.2 APIs are a pure subset of Servlet 2.3. See Developing servlets with WebSphere Application Server extensions. |
Sessions | IBM sessions | Yes | No | Many applications can run unchanged in Version 6 although changes might be required or recommended. See Developing session management in servlets and Migrating HTTP sessions. |
Transactions | IBM transactions | No | No | A change in the import statement. Also, one datasource connection cannot be used across multiple user transactions. See Using the transaction service and Isolation level and resource reference. |
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. |
WebSphere Control Program | WSCP | Yes | No | Use the JMX support provided by wsadmin. See Migrating administrative scripts. |