Book Image

Wildfly Cookbook

Book Image

Wildfly Cookbook

Overview of this book

Related Content you might be interested in

Current Title:

Small book image
Wildfly Cookbook
Jul, 2015 | 604 pages
No titles found
Table of Contents (23 chapters)
WildFly Cookbook
WildFly Cookbook
Credits
Credits
About the Author
About the Author
Acknowledgments
Acknowledgments
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Welcome to WildFly!
Welcome to WildFly!
Introduction
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
2
Running WildFly in Standalone Mode
Running WildFly in Standalone Mode
Introduction
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
3
Running WildFly in Domain Mode
Running WildFly in Domain Mode
Introduction
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
4
Managing the Logging Subsystem with the CLI
Managing the Logging Subsystem with the CLI
Introduction
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
5
Managing the Datasource Subsystems with the CLI
Managing the Datasource Subsystems with the CLI
Introduction
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
6
Clustering WildFly
Clustering WildFly
Introduction
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
7
Load Balancing WildFly
Load Balancing WildFly
Introduction
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
8
Commanding the CLI
Commanding the CLI
Introduction
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
9
Conquering the CLI
Conquering the CLI
Introduction
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
10
Hardening the WildFly Communication
Hardening the WildFly Communication
Introduction
Securing WildFly using HTTPS
Securing a specific application using HTTPS
Securing the WildFly console using HTTPS
Securing domain and host controller communication using HTTPS
11
Hardening the WildFly Configuration
Hardening the WildFly Configuration
Introduction
Delivering your configuration using property files
Securing your configuration hashing passwords
Securing and protecting passwords using a vault
12
Role-based Access Control with WildFly
Role-based Access Control with WildFly
Introduction
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
13
Messaging with WildFly
Messaging with WildFly
Introduction
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
14
WildFly into the Cloud with OpenShift
WildFly into the Cloud with OpenShift
Introduction
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
15
Using WildFly with Docker
Using WildFly with Docker
Introduction
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
Index

Introduction

In this chapter, you will learn how to configure HornetQ embedded in our WildFly in order to provide JMS capabilities to our applications. As WildFly is a Java EE 7-certified application server, it implements the JMS specification version 2.0.

HornetQ is a Message oriented middleware (MOM) used to exchange messages in clustered and asynchronous systems. It can run standalone (I'm not talking about the WildFly standalone mode) or embedded, that is inside an application server such as WildFly, by using the Java EE Connector Architecture (JCA).

Because HornetQ uses the JCA to integrate itself with WildFly, it also provides out-of-the-box support for connection pooling, JTA transactions, and container managed security, features that simplify a developer's life. Thus, integrating your EJB application with the JMS system will not need additional work.

HornetQ uses two fundamental concepts, that is, acceptors and connectors. Acceptors determine how the HornetQ server accepts incoming...

Previous Section
End of Section 2
Next Section