View RSS Feed

JBoss7

  1. EAR Class Loading

    by , 04-27-2012 at 06:33 PM
    Ear deployments are multi-module deployments. This means that not all classes inside an ear will necessarily have access to all other classes in the ear, unless explicit dependencies have been defined. By default the EAR/lib directory is a single module, and every WAR or EJB jar deployment is also a separate module. Sub deployments (wars and ejb-jars) always have a dependency on the parent module, which gives them access to classes in EAR/lib, however they do not always have an automatic dependency ...
    Categories
    JBoss7
  2. Class Loading Precedence

    by , 04-27-2012 at 06:32 PM
    A common source of errors in Java applications is including API classes in a deployment that are also provided by the container. This can result in multiple versions of the class being created and the deployment failing to deploy properly. To prevent this in AS7, module dependencies are added in a specific order that should prevent this situation from occurring.

    In order of highest priority to lowest priority

    1. System Dependencies - These are dependencies that are
    ...
    Categories
    JBoss7
  3. Automatic Dependencies

    by , 04-27-2012 at 06:32 PM
    Even though in AS7 modules are isolated by default, as part of the deployment process some dependencies on modules defined by the application server are set up for you automatically. For instance, if you are deploying a Java EE application a dependency on the Java EE API's will be added to your module automatically. Similarly if your module contains a beans.xml file a dependency on Weld will be added automatically, along with any supporting modules that weld needs to operate.

    Automatic ...
    Categories
    JBoss7
  4. Domain Directory Structure

    by , 04-27-2012 at 06:31 PM
    A key feature of AS 7 is the managing multiple servers from a single control point. A collection of multiple servers are referred to as a "domain". Domains can span multiple physical (or virtual) machines with all JBoss Application Server 7 instances on a given host under the control of a Host Controller process. The Host Controllers interact with the Domain Controller to control the lifecycle of the JBoss Application Server 7 instances running on that host and to assist the Domain ...
    Categories
    JBoss7
  5. Standalone Directory Structure

    by , 04-27-2012 at 06:29 PM
    In "standalone" mode each JBoss Application Server 7 instance is an independent process (similar to previous JBoss AS versions; e.g., 3, 4, 5, or 6). The configuration files, deployment content and writable areas used by the single standalone server run from a JBoss Application Server installation are found in the following subdirectories under the top level "standalone" directory:

    configuration: Configuration files for the standalone server that runs off of this ...
  6. Deciding between running standalone servers or a managed domain

    by , 04-27-2012 at 06:27 PM
    Which use cases are appropriate for managed domain and which are appropriate for standalone servers? A managed domain is all about coordinated multi-server management -- with it JBoss AS 7 provides a central point through which users can manage multiple servers, with rich capabilities to keep those servers' configurations consistent and the ability to roll out configuration changes (including deployments) to the servers in a coordinated fashion.
    It's important to understand that the choice ...
    Categories
    JBoss7
  7. JBoss7 Server Group

    by , 04-27-2012 at 06:26 PM
    A server group is set of server instances that will be managed and configured as one. In a managed domain each application server instance is a member of a server group. (Even if the group only has a single server, the server is still a member of a group.) It is the responsibility of the Domain Controller and the Host Controllers to ensure that all servers in a server group have a consistent configuration. They should all be configured with the same profile and they should have the same deployment ...
    Categories
    JBoss7
  8. JBoss7 Domain Controller

    by , 04-27-2012 at 06:25 PM
    One Host Controller instance is configured to act as the central management point for the entire domain, i.e. to be the Domain Controller. The primary responsibility of the Domain Controller is to maintain the domain's central management policy, to ensure all Host Controllers are aware of its current contents, and to assist the Host Controllers in ensuring any running application server instances are configured in accordance with this policy. This central management policy is stored by default in ...
    Categories
    JBoss7
  9. JBoss7 Host Controller

    by , 04-27-2012 at 06:25 PM
    When the domain.sh or domain.bat script is run on a host, a process known as a Host Controller is launched. The Host Controller is solely concerned with server management; it does not itself handle application server workloads. The Host Controller is responsible for starting and stopping the individual application server processes that run on its host, and interacts with the Domain Controller to help manage them.

    Each Host Controller by default reads its configuration from the domain/configuration/host.xml ...
    Categories
    JBoss7
  10. JBoss7 Managed Domain

    by , 04-27-2012 at 06:24 PM
    One of the primary new features of JBoss Application Server 7 is the ability to manage multiple JBoss Application Server 7 instances from a single control point. A collection of such servers is referred to as the members of a "domain" with a single Domain Controller process acting as the central management control point. All of the JBoss Application Server 7 instances in the domain share a common management policy, with the Domain Controller acting to ensure that each server is configured ...
    Categories
    JBoss7