API and Specifications for version 4.x

API and Specifications for version 4.x

If your existing applications currently support different specification levels than are supported by this version of the product, it is likely 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 5.

The following table summarize potential migration areas due to changes in supported specifications:

Specification Support in Version 4.0.x Support in Version 5 Must migrate from Version 4.0.x? Details

Enterprise beans EJB 1.1 EJB 2.0 No Full support for EJB 1.1 is provided. For more information, see Migrate enterprise bean code to the supported specification in the Application Development topic.

JavaServer Pages JSP 1.1 JSP 1.2 No JSP 1.1 APIs are a pure subset of JSP 1.2. For more information, see Migrate Web applications in the Application Development topic.

Servlets Servlet 2.2 Servlet 2.3 No Servlet 2.2 APIs are a pure subset of Servlet 2.3. For more information, see Migrate Web applications in the Application Development topic.

The following table summarize potential migration areas due to changes in supported APIs:

API Must migrate from Version 4.0.x? Details

Java 2 Connectors Yes The preliminary Java2 Connector support in Version 4 has been completed in Version 5. Some changes may be necessary to take full advantage of this support. For more information, see Migrate J2EE Connector Architecture.

Security Yes Changes may be required due to J2EE security. For more information, see Migrate security configurations from previous releases in the Securty topic.

Sessions Yes Many applications can run unchanged in Version 5, although changes may be required or recommended. For more information, see Migrate HTTP sessions.

Web Services Yes Changes may be required to migrate from Apache SOAP 2.1 that was supported in Version 4 to Apache SOAP 2.2. For more information, see Migrate web services.

XML Parser Yes XML4J V3.1 was supported in 4.0.x. Changes are required to move to the supported API XML4J Version 4.0.6 level.

The following table summarize potential migration areas due to changes in supported tools:

Tool Must migrate from Version 4? Details

XML Configuration Tool Yes Use JMX supported provided by WSAdmin. For more information, see The wsadmin administrative tool in the Administration topic.

WebSphere Control Program Yes Use JMX supported provided by WSAdmin. For more information, see Migrate from wscp to wsadmin in the Administration topic.

Specification	Support in Version 4.0.x	Support in Version 5	Must migrate from Version 4.0.x?	Details
Enterprise beans	EJB 1.1	EJB 2.0	No	Full support for EJB 1.1 is provided. For more information, see Migrate enterprise bean code to the supported specification in the Application Development topic.
JavaServer Pages	JSP 1.1	JSP 1.2	No	JSP 1.1 APIs are a pure subset of JSP 1.2. For more information, see Migrate Web applications in the Application Development topic.
Servlets	Servlet 2.2	Servlet 2.3	No	Servlet 2.2 APIs are a pure subset of Servlet 2.3. For more information, see Migrate Web applications in the Application Development topic.

API	Must migrate from Version 4.0.x?	Details
Java 2 Connectors	Yes	The preliminary Java2 Connector support in Version 4 has been completed in Version 5. Some changes may be necessary to take full advantage of this support. For more information, see Migrate J2EE Connector Architecture.
Security	Yes	Changes may be required due to J2EE security. For more information, see Migrate security configurations from previous releases in the Securty topic.
Sessions	Yes	Many applications can run unchanged in Version 5, although changes may be required or recommended. For more information, see Migrate HTTP sessions.
Web Services	Yes	Changes may be required to migrate from Apache SOAP 2.1 that was supported in Version 4 to Apache SOAP 2.2. For more information, see Migrate web services.
XML Parser	Yes	XML4J V3.1 was supported in 4.0.x. Changes are required to move to the supported API XML4J Version 4.0.6 level.

Tool	Must migrate from Version 4?	Details
XML Configuration Tool	Yes	Use JMX supported provided by WSAdmin. For more information, see The wsadmin administrative tool in the Administration topic.
WebSphere Control Program	Yes	Use JMX supported provided by WSAdmin. For more information, see Migrate from wscp to wsadmin in the Administration topic.