WildFly Application Server

WildFly is a modern, flexible, and lightweight application runtime designed for Java. It adheres to the latest standards of the Java Platform Enterprise Edition (Java EE). WildFly is completely free and open source, capable of running on various platforms. Key features of this application server include:

• A customizable runtime with pluggable subsystems that can be added or removed as needed.
• Support for Java EE8, making it easy to implement the latest enterprise Java standards.
• A modular design that allows each service to be started independently.
• An optimized, lightweight framework for maximum performance.

To set up a WildFly application server for hosting a Java project, follow the steps below.

Creating WildFly Server

1. Log in to your PaaS account and click the New Environment button in the upper left corner of the dashboard.

2. In the environment topology wizard, go to the Java tab and choose WildFly from the list of supported application servers (versions 10-16 are available). Next, use the cloudlet sliders to set the resource limits, select a region if multiple options are available, and give your environment a name.

When you’re prepared, just hit the Create button.

3. Just give it a few minutes for your setup to finish, then hit the Open in Browser button when it’s ready.

4. Take a moment or two for your setup to wrap up, and once it’s good to go, simply click on the “Open in Browser” button.

To reach the WildFly Administration Console, you can either click on the marked link in the image or find the URL in the email you received when the server was set up, along with your other login details.

Alternatively, you can connect to your WildFly server via SSH connection and utilize the built-in WildFly CLI tool for management tasks.

Standalone Mode

By default, the WildFly application server operates in “standalone” mode, ensuring that every instance functions as a separate process. This configuration is determined by the settings outlined in the STANDALONE_MODE_CONFIG environment variable.

There are four certified profiles available for standalone mode:

1. standalone.xml (default) – Configures Java Enterprise Edition 8 Web with the essential technologies.
2. standalone-full.xml – Provides configurations for Java Enterprise Edition 8 Full, including all EE 8 technologies.
3. standalone-ha.xml – Sets up Java Enterprise Edition 8 Web with high availability features.
4. standalone-full-ha.xml – Configures Java Enterprise Edition 8 Full with high availability.

When using the high availability configurations (the last two options), the jgroups protocol facilitates communication between nodes. By default, it is set up to use MD5 token authorization and asymmetric encryption, ensuring that unauthorized nodes cannot join the cluster and non-members cannot communicate with cluster members.

That wraps up our guide on installing the WildFly server! You’re now ready to customize the configuration to your needs and start deploying your applications.