Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering JBoss Enterprise Application Platform 7

You're reading from   Mastering JBoss Enterprise Application Platform 7 Core details of the Enteprise server supported by clear directions and advanced tips.

Arrow left icon
Product type Paperback
Published in Aug 2016
Publisher Packt
ISBN-13 9781786463630
Length 390 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Luigi Fugaro Luigi Fugaro
Author Profile Icon Luigi Fugaro
Luigi Fugaro
Francesco Marchioni Francesco Marchioni
Author Profile Icon Francesco Marchioni
Francesco Marchioni
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Installation and Configuration FREE CHAPTER 2. The CLI Management Tool 3. Managing EAP in Domain Mode 4. Deploying Applications 5. Load Balancing 6. Clustering EAP 7 7. Logging 8. Configuring Database Connectivity 9. Configuring EAP 7 for Java EE Applications 10. Messaging Administration 11. Securing the Application Server 12. New Security Features of EAP 7 13. Using EAP 7 with Docker 14. Running EAP 7 on the Cloud Using OpenShift

Clustering in standalone mode


As previously mentioned, to get clustering capabilities you need to use either the ha profile or the full-ha profile. We will stick with the ha profile for now. In standalone mode, this means that your configuration file is meant to be the one named standalone-ha.xml.

Let's give a first run to the default configuration and let's see what happens.

Do as follows:

cd $JBOSS_HOME
cp -a standalone cluster-1
$JBOSS_HOME/bin/standalone.sh -Djboss.server.base.dir=cluster-1 --server-config=standalone-ha.xml

We first cloned the standalone folder to the cluster-1 folder. Then we used the cluster-1 folder as the server base directory, and then used the standalone-ha.xml file as the server configuration file.

That's because, by default, standalone.sh uses standalone as the base directory and standalone.xml as the configuration file.

Once your cluster-1 instance started, did you see any cluster topology information? I guess you didn't. Is this because we are just running one...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime