Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

WildFly Configuration, Deployment, and Administration - Second Edition - Second Edition

4.4 (5)

WildFly Configuration, Deployment, and Administration - Second Edition

4.4 (5)

Overview of this book

This book is aimed at Java developers, system administrators, application testers using WildFly, and anyone who performs a DevOps role. Whether you are completely new to WildFly or just require an understanding of WildFly's new features, this book is for you.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Installing WildFly

1. Installing WildFly

What's new in WildFly 8?

Getting started with the application server

Exploring the application server filesystem

Summary

2. Configuring the Core WildFly Subsystems

2. Configuring the Core WildFly Subsystems

Configuring our application server

Configuring application server logging

Summary

3. Configuring Enterprise Services

3. Configuring Enterprise Services

Connecting to a database

Configuring the Enterprise JavaBeans container

Configuring concurrency

Summary

4. The Undertow Web Server

4. The Undertow Web Server

An overview of Undertow

Creating and deploying a web application

Creating a new Maven web project

Summary

5. Configuring a WildFly Domain

5. Configuring a WildFly Domain

Introducing the WildFly domain

Understanding the default domain configuration

Starting up and stopping a domain

Configuring the domain

Creating our very own domain configuration

Summary

6. Application Structure and Deployment

6. Application Structure and Deployment

Deploying resources on the application server

Deploying applications on a standalone WildFly server

Deploying applications on a WildFly domain

Explaining WildFly classloading

Summary

7. Using the Management Interfaces

7. Using the Management Interfaces

The command-line interface (CLI)

The web admin console

The CLI or web console?

Summary

8. Clustering

8. Clustering

Setting up a WildFly cluster

Configuring the WildFly cluster

Configuring the Infinispan subsystem

Clustering the messaging subsystem

Configuring clustering in your applications

Clustering session beans

Clustering entities

Caching entities

Caching queries

Clustering web applications

Summary

9. Load-balancing Web Applications

9. Load-balancing Web Applications

Benefits of using the Apache web server with WildFly

Load-balancing with mod_cluster

Installing mod_cluster libraries

Managing mod_cluster via the CLI

Managing your web contexts with the CLI

Adding native management capabilities

Managing web contexts using the configuration file

Troubleshooting mod_cluster

Load-balancing between nodes

Summary

10. Securing WildFly

10. Securing WildFly

Approaching Java security API

Securing the management interfaces

Securing the transport layer

Summary

11. WildFly, OpenShift, and Cloud Computing

11. WildFly, OpenShift, and Cloud Computing

Introduction to cloud computing

Getting started with OpenShift Online

Creating our first OpenShift application

Viewing the OpenShift server logfiles

Managing applications in OpenShift

Configuring your applications

Summary

A. CLI References

A. CLI References

Startup options

General commands

The domain-mode commands

Commands related to application deployment

JMS

Datasources

Mod_cluster

Batch

Snapshots

Index

Index

Connecting to a database

To allow your application to connect to a database, you will need to configure your server by adding a datasource. Upon server startup, each datasource is prepopulated with a pool of database connections. Applications acquire a database connection from the pool by doing a JNDI lookup and then calling getConnection(). Take a look at the following code:

Connection result = null;
try {
    Context initialContext = new InitialContext();
    DataSource datasource = (DataSource)initialContext.lookup("java:/MySqlDS");
    result = datasource.getConnection();
} catch (Exception ex) {
    log("Cannot get connection: " + ex);}

After the connection has been used, you should always call connection.close() as soon as possible. This frees the connection and allows it to be returned to the connection pool—ready for other applications or processes to use.

Releases prior to JBoss AS 7 required a datasource configuration file (ds.xml) to be deployed with...

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

WildFly Configuration, Deployment, and Administration - Second Edition

Search

Your notes and bookmarks