132 lines
4.7 KiB
HTML
132 lines
4.7 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
<html>
|
||
|
<head>
|
||
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
||
|
<title>API and Specifications for version 3.5.x</title>
|
||
|
</head>
|
||
|
|
||
|
<BODY>
|
||
|
<!-- Java sync-link -->
|
||
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
||
|
<h3><A NAME="migover356eval"></A>API and Specifications for version 3.5.x</h3>
|
||
|
|
||
|
<p>If your existing applications currently support different specification levels than are supported by this version of the product, it is likely you must update at least some aspects of the applications to comply with the new specifications.</p>
|
||
|
|
||
|
<p>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 WebSphere Application Server - Express. </p>
|
||
|
|
||
|
<p>From Version 3.5.x to WebSphere Application Server - Express, main migration areas concern IBM entensions and migrating the Java specifications to Java 2.</p>
|
||
|
<p>The following table summarizes potential migration areas due to changes in supported specifications:</p>
|
||
|
<table border="1" cellpadding="3" cellspacing="3">
|
||
|
<tr>
|
||
|
<th id="col1">Specification</th>
|
||
|
<th id="col2">Support in Version 3.5</th>
|
||
|
<th id="col3">Support in WebSphere Application Server - Express</th>
|
||
|
<th id="col4">Must migrate from Version 3.5?</th>
|
||
|
<th id="col5">Details</th>
|
||
|
</tr>
|
||
|
|
||
|
|
||
|
|
||
|
<tr>
|
||
|
<td headers="col1">JDBC</td>
|
||
|
<td headers="col2">JDBC 1.0</td>
|
||
|
<td headers="col3">JDBC 2.0</td>
|
||
|
<td headers="col4">Yes</td>
|
||
|
<td headers="col5">Many applications can run unchanged in WebSphere Application Server - Express although some changes may be required or recommended.</td>
|
||
|
</tr>
|
||
|
|
||
|
<tr>
|
||
|
<td rowspan="3" headers="col1">JavaServer Pages</td>
|
||
|
<td headers="col2">JSP .91</td>
|
||
|
<td rowspan="3" headers="col3">JSP 1.2</td>
|
||
|
<td headers="col4">Yes</td>
|
||
|
<td rowspan="3" headers="col5">JSP 1.0 and 1.1 APIs are a pure subset of JSP 1.2. For more information, see <a href="wappmig.htm">Migrate Web applications</a>.</td>
|
||
|
</tr>
|
||
|
|
||
|
<tr>
|
||
|
|
||
|
<td headers="col2">JSP 1.0</td>
|
||
|
|
||
|
<td headers="col4">No</td>
|
||
|
|
||
|
</tr>
|
||
|
|
||
|
<tr>
|
||
|
|
||
|
<td headers="col2">JSP 1.1</td>
|
||
|
|
||
|
<td headers="col4">No</td>
|
||
|
|
||
|
</tr>
|
||
|
|
||
|
<tr>
|
||
|
<td rowspan="2" headers="col1">Servlets</td>
|
||
|
<td headers="col2">Servlet 2.1</td>
|
||
|
<td rowspan="2" headers="col3">Servlet 2.3</td>
|
||
|
<td headers="col4">Yes</td>
|
||
|
<td headers="col5">Many Servlet 2.1 applications can run unchanged in WebSphere Application Server - Express although changes might be required or recommended. For more information, see <a href="wappmig.htm">Migrate Web applications</a>.</td>
|
||
|
</tr>
|
||
|
|
||
|
<tr>
|
||
|
<td headers="col2">Servlet 2.2</td>
|
||
|
<td headers="col4">No</td>
|
||
|
<td headers="col5">Servlet 2.2 APIs are a pure subset of Servlet 2.3. For more information, see <a href="wappmig.htm">Migrate Web applications</a>.</td>
|
||
|
</tr>
|
||
|
|
||
|
</table>
|
||
|
<p>The following table summarizes potential migration areas due to changes in supported APIs:</p>
|
||
|
<table border="1" cellpadding="3" cellspacing="3">
|
||
|
<tr>
|
||
|
<th id="col6">API</th>
|
||
|
<th id="col7">Must migrate from Version 3.5?</th>
|
||
|
<th id="col8">Details</th>
|
||
|
</tr>
|
||
|
|
||
|
<!--<tr>
|
||
|
<td>Security</td>
|
||
|
<td>Yes</td>
|
||
|
<td>Changes may be required due to J2EE security. For more information, see <a href="secmig.htm">Migrate security configurations from previous releases</a> in the <em>Securty</em> topic. <font color="red">check link</font></td>
|
||
|
|
||
|
</tr>-->
|
||
|
|
||
|
<tr>
|
||
|
<td headers="col6">Sessions</td>
|
||
|
<td headers="col7">Yes</td>
|
||
|
<td headers="col8">Many applications can run unchanged in WebSphere Application Server - Express, although changes may be required or recommended. For more information, see <a href="mighttpses.htm">Migrate HTTP sessions</a>.</td>
|
||
|
</tr>
|
||
|
|
||
|
|
||
|
|
||
|
</table>
|
||
|
|
||
|
<p>The following table summarizes potential migration areas due to changes in supported tools:</p>
|
||
|
<table border="1" cellpadding="3" cellspacing="3">
|
||
|
<tr>
|
||
|
<th id="col9">Tool</th>
|
||
|
<th id="col10">Must migrate from Version 3.5?</th>
|
||
|
<th id="col11">Details</th>
|
||
|
</tr>
|
||
|
|
||
|
<tr>
|
||
|
<td headers="col9">XML Configuration Tool</td>
|
||
|
<td headers="col10">Yes</td>
|
||
|
<td headers="col11">Use JMX support provided by WSAdmin. For more information, see <a href="../admin/wsa.htm">The wsadmin administrative tool</a> in the <em>Administration</em> topic.</td>
|
||
|
</tr>
|
||
|
|
||
|
<tr>
|
||
|
<td headers="col9">WebSphere Control Program</td>
|
||
|
<td headers="col10">Yes</td>
|
||
|
<td headers="col11">Use JMX support provided by WSAdmin. For more information, see <a href="../admin/wsa.htm">The wsadmin administrative tool</a> in the <em>Administration</em> topic.</td>
|
||
|
</tr>
|
||
|
|
||
|
</table>
|
||
|
|
||
|
|
||
|
|
||
|
</body>
|
||
|
</html>
|