InfoCenter Home >
3: Migration overview >
3.3: Migrating APIs and specifications
3.3: Migrating APIs and specifications
IBM WebSphere Application Server supports a wide variety of
technologies for building powerful enterprise applications. As
technology advances, particularly in the area of Java components,
new Application Server product versions advance to support and
extend the most contemporary open specification levels.
If your existing applications currently support different specification
levels than are supported by this version of the product, it
is likely you will need to update at least a few
aspects of the applications to comply with the new specifications.
In many cases, IBM extends the specification levels that are currently
supported by the product to provide additional
features and customization options. If your existing applications
use extensions from earlier product versions, mandatory
or optional migration could be necessary to utilize the same
kinds of extensions in the current version.
From Version 3.0x to
Version 3.5,
the main migration areas
concern the IBM extensions and the JDK. In contrast, migrating
from Version 2.0x requires updating applications with respect
to the open specifications, such as the Java Servlet API.
The table summarizes potential migration areas. See the
Related information below for instructions pertaining to each area.
Functional area |
Support in current version |
Need to migrate from V3.x? |
Need to migrate from V2.0x? |
Details |
Enterprise beans |
EJB 1.0 Specification |
No*
|
Yes** |
* Although there are no EJB API changes for Version 3.x, changes in the
underlying JDK 1.2 prerequisite require enterprise beans to be deployed again.
** Version 2.0x offered only limited EJB 1.0 Specification support |
Servlets |
Servlet 2.1 Specification and IBM
extensions |
Yes
|
Yes |
Article 4.2.1.2.1a describes the Servlet 2.2 APIs.
Version 2.0x supported the Servlet 2.0 Specification and
IBM extensions that were updated in Version 3.0x
|
Servlets |
Servlet 2.2 Specification |
No |
not applicable |
Article 4.2.1.2.1a describes the new Servlet 2.2 APIs.
Version 2.0x supported the Servlet 2.0 Specification.
|
JSP files |
JSP .91 Specification |
Yes |
Yes |
Version 2.0x only supported the JSP .91 Specification.
It is recommended you migrate to JSP 1.1.
|
JSP files |
JSP 1.0 Specification |
No**
|
Yes |
Version 2.0x only supported the JSP .91 Specification.
** If you did not already migrate JSP .91 files for use with Version 3.x,
it is recommended you migrate to JSP 1.1.
|
JSP files |
JSP 1.1
Specification |
No |
not applicable |
Version 2.0x only supported the JSP .91 Specification.
|
XML |
XML 2.0.x supported
XML 1.1.x supported with restrictions
|
No
|
No
|
Migration from 1.1.x to 2.0.x is not
required, but you might decide to migrate based
on criteria and 1.1.x restrictions described in
article 3.3.4.
|
JDBC and IBM database connection support APIs |
JDBC 2.0; connection pooling model |
No
|
Yes |
V2.0x supported JDBC 1.0 and a connection manager model.
If still using Connection Manager,
it is recommended that you
switch to connection pooling.
Do not forget to switch to supported JDBC 2.0 drivers.
|
User profiles |
IBM user profile APIs |
No |
Yes |
Need to migrate from V2.0x deprecated
classes for use with V3.0x or V3.5
|
Sessions |
IBM session support APIs |
No |
Yes |
Need to migrate from V2.0x deprecated
classes,
changes to clustering, URL encoding
for use with V3.0x or V3.5
|
Security |
IBM security support |
No |
No |
No action required.
|
Transactions |
Java 1.2 transactions support |
Yes |
Yes |
Version 3.0x provided proprietary IBM packages to simulate
Java 1.2 functionality. Version 2.0x did not provide any
support.
Migrate to Version 3.5 if your applications require this
kind of support.
|
XML configuration |
XMLConfig tool |
Yes |
Yes |
The XML Configuration Management Tool (XMLConfig) was
introduced in Version 3.02.
Some of the interfaces have
changed in Version 3.5.
|
|
|