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: