Migrate the classloader Module Visibility Mode setting

Note: This topic does not describe how to migrate your entire configuration to Version 5. For more information about migrating your configuration, see Migration for migration instructions and tools.

WAS Version 4.0.x had a server-wide configuration setting called Module Visibility Mode. For Version 5.0, you use application or WAR classloader policies instead of module visibility modes. For more information on classloader policies, see Classloader policies. The Version 5.0 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.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 classloader policy	Version 5.0 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.