43 lines
2.8 KiB
HTML
43 lines
2.8 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>Migrate the classloader Module Visibility Mode setting</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h3><A NAME="clsmig">Migrate the classloader Module Visibility Mode setting</A></h3>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server Version 4.0.x had a server-wide configuration setting called Module Visibility Mode. For Version 5.1, you use application or WAR classloader policies instead of module visibility modes. For more information on classloader policies, see <a href="clsiso.htm">Classloader policies</a> in the <em>Application Development</em> topic. The Version 5.1 policies provide additional flexibility because you can configure applications running in a server for an application classloader policy of SINGLE or MULTIPLE and for a WAR classloader policy of APPLICATION or MODULE.</p>
|
||
|
|
<p>To migrate module visibility modes in your Version 4.0.x applications to their equivalents in Version 5.1, change the settings for your Version 4.0.x applications and modules to the Version 5.1 values shown in the table below.</p>
|
||
|
|
<table border="1">
|
||
|
|
<tr><th>Version 4.0.x module visibility mode</th> <th>Version 5.1 application classloader policy</th> <th>Version 5.1 WAR classloader policy</th></tr>
|
||
|
|
<tr><td>Server</td> <td>SINGLE</td> <td>APPLICATION</td> </tr>
|
||
|
|
<tr><td>Compatibility</td> <td>SINGLE</td> <td>MODULE</td></tr>
|
||
|
|
<tr><td>Application</td> <td>MULTIPLE</td> <td>APPLICATION</td></tr>
|
||
|
|
<tr><td>Module*</td> <td>MULTIPLE</td> <td>MODULE</td></tr>
|
||
|
|
<tr><td>J2EE</td> <td>MULTIPLE</td> <td>MODULE</td></tr>
|
||
|
|
</table>
|
||
|
|
<p>*There is no exact equivalent for the Version 4.0.x Module mode because it isolated EJB modules within an application.</p>
|
||
|
|
|
||
|
|
<p>To migrate the classloader settings with the administrative console, perform these steps:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><a href="../admin/acstart.htm">Start the administrative console</a>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Servers</strong> and click <strong>Application Servers</strong>.</li>
|
||
|
|
<li>Click the name of your application server.</li>
|
||
|
|
<li>For the <strong>Application server policy</strong>, select <strong>Single</strong> or <strong>Multiple</strong>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Applications</strong> and click <strong>Enterprise Applications</strong>.</li>
|
||
|
|
<li>Click the name of the application for which you want to change the classloader policy.</li>
|
||
|
|
<li>For the <strong>WAR Classloader Policy</strong>, select <strong>Module</strong> or <strong>Application</strong>.</li>
|
||
|
|
<li><a href="../admin/acsave.htm">Save the configuration</a>.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|