Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Mastering JBoss Enterprise Application Platform 7
  • Toc
  • feedback
Mastering JBoss Enterprise Application Platform 7

Mastering JBoss Enterprise Application Platform 7

By : Marchioni, Luigi Fugaro
3.7 (3)
close
Mastering JBoss Enterprise Application Platform 7

Mastering JBoss Enterprise Application Platform 7

3.7 (3)
By: Marchioni, Luigi Fugaro

Overview of this book

The JBoss Enterprise Application Platform (EAP) has been one of the most popular tools for Java developers to create modular, cloud-ready, and modern applications. It has achieved a reputation for architectural excellence and technical savvy, making it a solid and efficient environment for delivering your applications. The book will first introduce application server configuration and the management instruments that can be used to control the application server. Next, the focus will shift to enterprise solutions such as clustering, load balancing, and data caching; this will be the core of the book. We will also discuss services provided by the application server, such as database connectivity and logging. We focus on real-world example configurations and how to avoid common mistakes. Finally, we will implement the knowledge gained so far in terms of Docker containers and cloud availability using RedHat's OpenShift.
Table of Contents (15 chapters)
close

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...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete