Book Image

WildFly Configuration, Deployment, and Administration

By : Francesco Marchioni, Christopher Adam M Ritchie
Book Image

WildFly Configuration, Deployment, and Administration

By: Francesco Marchioni, Christopher Adam M Ritchie

Overview of this book

Table of Contents (19 chapters)
WildFly Configuration, Deployment, and Administration Second Edition
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Configuring our application server


The default configuration files are named standalone.xml, for standalone servers, and domain.xml for an application server domain. An application server domain can be seen as a specialized server configuration, which also includes the domain and host controller setup. We will discuss the application server domain in Chapter 5, Configuring a WildFly Domain. However, as far as the core services configuration is concerned, what we cover here will be suitable for the domain configuration as well. The configuration files (standalone.xml and domain.xml) are non-static files, which means that runtime changes are persisted to them, for example, adding a new component, such as a JMS destination, or deploying an application.

You can define as many configuration files as you need. The WildFly 8.1.0 release provides a few variants of standalone.xml (web profile), such as standalone-full.xml (full profile), and the standalone-ha.xml (web profile with high availability...