WildFly Server

WildFly Application Server

WildFly is an open-source Jakarta EE application server for developing and running enterprise Java applications. On the platform, WildFly can be deployed as a standalone server or as an automatically clustered Managed Domain environment.

In this article

WildFly Overview

WildFly provides the services required by enterprise Java applications, including servlet processing, dependency injection, persistence, transactions, messaging, web services, security, and centralized management.

Jakarta EE supportRuns standards-based enterprise Java applications.
Standalone modeRuns one independently managed WildFly application-server instance.
Managed Domain modeCoordinates multiple worker nodes through a Domain Controller.
Auto-ClusteringThe platform can create a Managed Domain topology with one Domain Controller and multiple worker nodes.
Public IP supportA dedicated public address can be attached when direct external access is required.
i

Cluster topology

When WildFly Auto-Clustering is enabled, the platform creates the cluster in Managed Domain mode with one Domain Controller and the selected number of worker nodes.

Create a WildFly Environment

1

Open the environment wizard

Sign in to the platform dashboard and click New Environment.

2

Select WildFly

Open the Java tab and select WildFly as the application server.

3

Configure the topology

Select the required WildFly version and JDK, define the Cloudlet limits, disk space, node count, public IP requirement, region, and environment name.

4

Create the environment

Review the topology and click Create. The platform provisions and starts the WildFly server automatically.

Select WildFly in the Java topology wizard
Select WildFly and configure resources, scaling, networking, and environment settings.

Open and Verify the Server

1

Open WildFly in a browser

After environment creation finishes, click Open in Browser beside the WildFly node.

2

Confirm the server is available

The WildFly welcome page should open, confirming that the application server is running.

WildFly welcome page
The WildFly welcome page confirms successful server startup.

Management and Configuration

WildFly can be managed through the platform dashboard, configuration-file manager, command-line tools, and the WildFly management interface.

ConfigOpen and edit WildFly configuration files through the dashboard.
LogsReview server startup, deployment, application, and runtime logs.
SSH accessConnect to the container for command-line administration and troubleshooting.
Management consoleUse the WildFly administration interface when it is enabled and securely exposed.
Environment variablesDefine environment-specific values without hardcoding them into the application.
!

Protect the management interface

Do not expose WildFly management ports publicly without authentication, firewall restrictions, and SSL/TLS protection.

Deploy an Application

Java applications can be deployed from an archive or built from a version-control repository.

1

Open Deployment Manager

Upload a supported Java application package, such as a WAR or EAR archive.

2

Select the WildFly environment

Click Deploy to, choose the target environment, and specify the deployment context when required.

3

Review the deployment

Wait for the deployment task to complete and review the WildFly logs when the application does not start correctly.

Deploy an application to WildFly
Upload the application archive and deploy it to the WildFly environment.

Scaling and Auto-Clustering

WildFly containers support automatic vertical scaling. Clustered deployments can also use multiple worker nodes in Managed Domain mode.

Vertical scalingRAM and CPU usage can grow automatically up to the configured Cloudlet limit.
Worker-node scalingIncrease or reduce the number of application-server workers according to workload.
Domain ControllerCoordinates WildFly configuration and management across the worker nodes.
High availabilityMultiple workers reduce dependence on one application-server instance.
1

Enable Auto-Clustering

Open the topology wizard and enable the Auto-Clustering option for WildFly.

2

Set the worker-node count

Select the required number of WildFly worker nodes. The platform creates one Domain Controller and the configured workers.

3

Apply the topology

Create the environment or apply the topology change and wait for the cluster configuration to complete.

Enable WildFly Auto-Clustering
Enable Auto-Clustering to create a WildFly Managed Domain topology.

Expected Result

A managed WildFly environment is created with the selected WildFly and JDK versions, resource limits, networking, deployment options, and optional Managed Domain clustering.

Important Notes

  • Check application compatibility before changing the WildFly or JDK version.
  • Protect the management interface and management ports.
  • Use private networking between nodes whenever possible.
  • Review application persistence, session state, and shared services before scaling.
  • Use Auto-Clustering when centralized management of multiple WildFly workers is required.
  • Review deployment and server logs after every production change.

Common Issues and Solutions

WildFly is unavailable in the wizardCheck the Java application-server list and the hosting provider’s current stack availability.
Welcome page does not openCheck the node status, environment URL, Shared Load Balancer or public IP, and firewall rules.
Application deployment failsVerify the archive format, deployment context, WildFly/JDK compatibility, and server logs.
Management console is inaccessibleCheck management-user configuration, port access, firewall rules, and whether the console is enabled.
Worker node does not join the domainReview Domain Controller connectivity, node configuration, credentials, and WildFly logs.
Sessions are lost between workersConfigure a supported clustered session solution or shared external session storage.

Related Guides