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

Features of the CLI

The CLI offers you some neat features such as executing operations as an atomic operation - which is called batch mode - scripting all the commands into a file (commonly named .cli files), and also the opportunity to do configuration tasks offline, which means without a running JBoss EAP instance... or better, there is one, but it's embedded into the CLI and it's not invisible outside.

Let's start gradually.

Batch mode

Batch mode allows you to run multiple CLI commands and operations in sequence, and commit the whole set of statements as one. The all-or-nothing commit pattern is applied, which means that all tasks must run successfully in order to complete correctly, otherwise if just one task goes in error, the whole batch sequence rolls back.

To enable batch mode, first you need to invoke the batch directive, since all future commands and operations will not be executed until you invoke the end of the batch sequence by invoking the run-batch command.

Suppose...

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