Migrate the classloader Module Visibility Mode setting

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 Classloader policies in the Application Development 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.

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.

Version 4.0.x module visibility mode Version 5.1 application classloader policy Version 5.1 WAR classloader policy
Server SINGLE APPLICATION
Compatibility SINGLE MODULE
Application MULTIPLE APPLICATION
Module* MULTIPLE MODULE
J2EE MULTIPLE MODULE

*There is no exact equivalent for the Version 4.0.x Module mode because it isolated EJB modules within an application.

To migrate the classloader settings with the administrative console, perform these steps:

  1. Start the administrative console.
  2. In the topology tree, expand Servers and click Application Servers.
  3. Click the name of your application server.
  4. For the Application server policy, select Single or Multiple.
  5. In the topology tree, expand Applications and click Enterprise Applications.
  6. Click the name of the application for which you want to change the classloader policy.
  7. For the WAR Classloader Policy, select Module or Application.
  8. Save the configuration.