Wildfly Cookbook

Book Image

Wildfly Cookbook

Book Image

Wildfly Cookbook

Overview of this book

WildFly Cookbook

WildFly Cookbook

Credits

About the Author

About the Author

Acknowledgments

Acknowledgments

About the Reviewers

About the Reviewers

www.PacktPub.com

www.PacktPub.com

Preface

Free Chapter

Welcome to WildFly!

Welcome to WildFly!

Software prerequisites

Downloading and installing WildFly

Understanding WildFly's directory overview

Running WildFly in standalone mode

Running WildFly in domain mode

Running WildFly as a service

Running WildFly in Standalone Mode

Running WildFly in Standalone Mode

Running WildFly from a custom configuration folder

Binding WildFly onto a custom port

Binding WildFly onto a custom IP

Configuring multiple WildFly instances to run on the same machine with different ports

Configuring multiple WildFly instances to run on the same machine with different IPs

Managing applications using the deployments folder

Connecting to the CLI

Checking the server-state via the CLI

Deploying an application via the CLI

Undeploying an application via the CLI

Executing commands in batch mode via the CLI

Reloading a server configuration via the CLI

Shutting down and restarting an instance via the CLI

Suspending and resuming an instance via the CLI

Backing up your configuration file via the CLI

Running WildFly in Domain Mode

Running WildFly in Domain Mode

Running domain mode

Connecting the host controller to the domain controller

Stopping and starting server groups via the Web Console

Stopping and starting your server groups via the CLI

Stopping and starting your servers via the CLI

Deploying and undeploying an application to a specific server group via Web Console

Deploying and undeploying an application to a specific server group via the CLI

Checking server status via the CLI

Managing the Logging Subsystem with the CLI

Managing the Logging Subsystem with the CLI

Creating a file-handler logging

Creating a periodic-rotating file-handler

Creating a size-rotating file-handler

Defining asynchronous handlers

Creating a syslog-handler

Listing and reading log files

Using a different logging implementation

Managing the Datasource Subsystems with the CLI

Managing the Datasource Subsystems with the CLI

Preparing a non JDBC-4 compliant driver

Creating and removing a datasource

Checking the datasource connection

Reading the datasource's statistics

Setting a connection pool

Creating and removing XA-Datasource

Clustering WildFly

Clustering WildFly

Creating a cluster in standalone mode

Creating separate clusters in standalone mode

Creating a cluster in domain mode

Creating separate clusters in domain mode

Creating a cluster via TCP

Testing the UDP protocol with the JGroups tool

Load Balancing WildFly

Load Balancing WildFly

Installing and configuring Apache HTTPD

Installing and configuring mod_cluster for Apache

Balancing WildFly using auto advertising – UDP

Balancing WildFly using a list of available balancers – TCP

Balancing using the HTTP connector instead of AJP

Preserve WildFly workers while restarting Apache

Balancing the same context for different applications

Rolling updates

Commanding the CLI

Commanding the CLI

Invoking CLI commands

Checking the WildFly version

Checking WildFly operational mode

Getting the OS version

Getting the JVM version

Checking the JVM options

Checking JVM memories – heap-size and all

Checking the server status

Checking the JNDI tree view

Invoking CLI commands declared in an external file

Conquering the CLI

Conquering the CLI

Invoking server stop, start, and reload

Invoking server group stop, start, restart, and reload

Creating a server group

Creating a server

Managing an application – deploy, undeploy

Hardening the WildFly Communication

Hardening the WildFly Communication

Securing WildFly using HTTPS

Securing a specific application using HTTPS

Securing the WildFly console using HTTPS

Securing domain and host controller communication using HTTPS

Hardening the WildFly Configuration

Hardening the WildFly Configuration

Delivering your configuration using property files

Securing your configuration hashing passwords

Securing and protecting passwords using a vault

Role-based Access Control with WildFly

Role-based Access Control with WildFly

Switching between simple and RBAC providers

Managing users, groups, and their role mapping

Setting a predefined role to all authenticated users

Granting user access by server group or host – scoped roles

Integrating with OpenLDAP

Messaging with WildFly

Messaging with WildFly

Running the messaging system using HornetQ

Sending and receiving messages to/from a JMS queue destination

Clustering HornetQ using a shared store

Clustering HornetQ using message replication

WildFly into the Cloud with OpenShift

WildFly into the Cloud with OpenShift

Registering to OpenShift Online

Installing the WildFly cartridge for our first deployment

Taking control of your WildFly server via SSH

Deploying your code to OpenShift Online

Using WildFly with Docker

Using WildFly with Docker

Setting up the Docker environment

Running WildFly in Docker

Logging WildFly outside Docker

Running WildFly in domain mode in Docker using different Docker containers

Index

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Reloading a server configuration via the CLI

In this recipe, we will learn how to reload the server configuration, without the need for a full restart. Often, there are changes that need the server to be reloaded. Most of the time you realize that a specific setting needs a different value just after a server startup or during tests. So, instead of stopping and starting the all application server, you can just reload the configuration, unless the change involves the JVM or settings that are needed at boot time.

Getting ready

We have already seen how to reload a server while playing with IPs and port binding, but it's worth mentioning again.

How to do it…

The command itself is pretty easy:

$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9990 /] reload
[standalone@localhost:9990 /]

How it works…

Basically, the reload command issues, in sequence, a stop for all the WildFly active services and a start, which starts up the services again. This should give you important information. The JVM remains...