Migrating the class-loader Module Visibility Mode setting: WAS

Migrating the class-loader Module Visibility Mode setting

WebSphere Application Server Version 4.0.x had a server-wide configuration setting called Module Visibility Mode. For Version 5.0, you use application or WAR class-loader policies instead of module visibility modes. The Version 5.0 policies provide additional flexibility because you can configure applications running in a server for an application class-loader policy of SINGLE or MULTIPLE and for a WAR class-loader policy of APPLICATION or MODULE.
To migrate module visibility modes in your Version 4.0.x applications to their equivalents in Version 5.0, change the settings for your Version 4.0.x applications and modules to the Version 5.0 values shown in the table below.

Version 4.0.x module visibility mode Version 5.0 application class-loader policy Version 5.0 WAR class-loader 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.
Class loaders
Class loading

Version 4.0.x module visibility mode	Version 5.0 application class-loader policy	Version 5.0 WAR class-loader policy
Server	SINGLE	APPLICATION
Compatibility	SINGLE	MODULE
Application	MULTIPLE	APPLICATION
Module*	MULTIPLE	MODULE
J2EE	MULTIPLE	MODULE