Book Image

JBoss AS 7 Configuration, Deployment and Administration

By : Francesco Marchioni
Book Image

JBoss AS 7 Configuration, Deployment and Administration

By: Francesco Marchioni

Overview of this book

<p>As the Java EE standard has evolved and matured, the API has become increasingly rich and complex. The next generation of application servers needs to be modular and configurable to run only specific services or containers. JBoss AS 7 promises to meet those requirements but the configuration of a complex application server is composed of a mix of administrative and management tasks which often overlap, generating confusion.<br /><br />JBoss AS 7 Configuration, Deployment and Administration will give you an expert's understanding of every component that makes up the JBoss application server, and will show you how to use them, helping you to dramatically cut down the learning curve for this exciting product.<br /><br />This book will guide you through configuration, management, deployment and advanced administration in a logical order to avoid the common pitfalls of setting up a new AS. The book dives into the new application server structure and shows you how to install it. You will learn how to configure the core AS services, including thread pools, the messaging system, and the transaction service. Finally, you will learn how to deploy and manage your applications and then tune the performance of your AS to achieve an efficient, indispensible application server.</p>
Table of Contents (19 chapters)
JBoss AS 7 Configuration, Deployment, and Administration
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Clustering web applications


Clustering web applications requires the least effort for the developer. As we have just discussed, all you need to switch on clustering in a web application is adding the following directive in the web.xml descriptor:

<web-app>
   <distributable/>
</web-app>

By default, clustered web applications will use the web cache contained in the Infinispan configuration. One thing you can customize is setting up a specific cache per deployment unit. This can be achieved by adding to jboss-web.xml the replication-config directive containing the cache name to be used:

<jboss-web>
  <replication-config>
     <cache-name>web.dist</cache-name>
  </replication-config>
</jboss-web>

The previous configuration should obviously reference a cache defined in the main configuration file:

<cache-container name="web" default-cache="repl">
   <alias>standard-session-cache</alias>

   <distributed-cache mode="ASYNC"...