Use this page to configure an instance of Web module deployment.
To view this administrative console page, click Applications > Enterprise Applications > application_instance > Web modules.
Removes a module from the deployed application. The module is deleted from the application in the WebSphere Application Server configuration repository and also from all the nodes where the application is installed and running (or expected to run). If the application is running on a node when the module file is deleted from the node as a result of configuration synchronization then the Web module is stopped before deleting it from the file system of the node. The entire application continues to run without any interruption. An exception to this rule is if the class loader setting for the application is marked as "application" instead of "module", the default setting. If the class loader setting is application, the entire application is stopped and restarted during module file deletion on the node. Also if the security provider configured for the Application Server cell does not support dynamic module updates, then the entire application is stopped and restarted.
Opens a wizard that helps you update a module in an application. If a module has the same URI as a module already existing in the application, the new module replaces the existing module. If the new module does not exist in the application, it is added to the deployed application. If the application is running on a node when the module file is updated on the node as a result of configuration synchronization then only that Web module is stopped, the module file is updated on the node's file system, and then the application is restarted. The rest of the application continues to run without any interruption. An exception to this rule is if the class loader setting for the application is marked as "application" instead of "module", the default setting. If the class loader setting is application, the entire application is stopped and restarted during module file update on the node. Also if the security provider configured for Application Server cell does not support dynamic module updates, then the entire application is stopped and restarted.
Deletes a file from a module of a deployed application. The file is also deleted from all the nodes where the module is installed after configuration is synchronized with nodes. If this file belongs to the META-INF or WEB-INF directory of the Web module then the Web module is stopped and restarted when the file is deleted from the node. If this is a non-metadata file (such as .class, .jsp files or static content such as.htm, .gif files) then nothing in the application is stopped for changes to take effect.
Specifies a URI that, when resolved relative to the application URL, specifies the location of the module archive contents on a file system. The URI must match the ModuleRef URI in the deployment descriptor of an application if the module was packaged as part of a deployed application or enterprise archive (EAR) file.
Specifies the file name for an alternative deployment descriptor file to use instead of the original deployment descriptor file in the module JAR file.
This file is the post-assembly version of the deployment descriptor file. You can edit the original deployment descriptor file to resolve dependencies and security information. Specifying the use of the alternative deployment descriptor keeps the original deployment descriptor file intact.
The value of the Alternate deployment descriptor property must be the full path name of the deployment descriptor file, relative to the module root directory. By convention, the file is in the ALT-INF directory. If this property is not specified, the deployment descriptor file is read from the module JAR file.
Specifies the order in which modules are started. Lower weighted modules are started before higher weighted modules.
Specifies whether the class loader should search in the parent class loader or in the application class loader first to load a class. The standard for JDK class loaders and WebSphere class loaders is Parent First. By specifying Parent Last, your application can override classes contained in the parent class loader, but this action can potentially result in ClassCastException or LinkageErrors if you have mixed use of overriden classes and non-overriden classes.
The options are Parent First and Parent Last. The default is to search in the parent class loader before searching in the application class loader to load a class.
Data type | String |
Default | Parent First |
Related concepts
Web modules
Class loaders
Related reference
Web applications: Resources for learning