7.2. Disable Sub-Deployment Module Isolation for All Deployments

This task shows server administrators how to disable Subdeployment Module Isolation on the application server. This affects all deployments.


This task requires you to edit the XML configuration files of the server. The server must be halted before doing this. This is temporary as the final release administration tools will support this type of configuration.
  1. Stop the server

    Halt the JBoss Enterprise Application Platform server.
  2. Open the server configuration file

    Open the server configuration file in a text editor.
    This file will be different for a managed domain or standalone server. In addition, non-default locations and file names may be used. The default configuration files are domain/configuration/domain.xml and standalone/configuration/standalone.xml for managed domains and standalone servers respectively.
  3. Locate the EE Subsystem Configuration

    Locate the EE Subsystem configuration element in the configuration file. The <profile> element of the configuration file contains several subsystem elements. The EE Subsystem element has the namespace of urn:jboss:domain:ee:1.0.
       <subsystem xmlns="urn:jboss:domain:ee:1.0" />
    The default configuration has a single self-closing tag but a custom configuration may have separate open and closing tags (possibly with other elements within) like this:
    <subsystem xmlns="urn:jboss:domain:ee:1.0" ></subsystem>
  4. Replace self-closing tags if necessary

    If the EE Subsystem element is a single self-closing tag then replace with with appropriate opening and closing tags like this:
    <subsystem xmlns="urn:jboss:domain:ee:1.0" ></subsystem>
  5. Add ear-subdeployments-isolated element

    Add the ear-subdeployments-isolated element as a child of the EE Subsystem element and add the content of false like this:
    <subsystem xmlns="urn:jboss:domain:ee:1.0" ><ear-subdeployments-isolated>false</ear-subdeployments-isolated></subsystem>
  6. Start the server

    Relaunch the JBoss Enterprise Application Platform server to start it running with the new configuration.

The server will now be running with Subdeployment Module Isolation disabled for all deployments.