WildFly 40

Azure Application Servers

WildFly is a Jakarta EE application server for enterprise Java, ready to accept application deployments on first boot.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

WildFly is an open source Jakarta EE application server and the upstream project behind JBoss EAP. It provides a modular, standards based runtime for enterprise Java applications, with fast startup, a small memory footprint and a web management console for administration. It implements the full Jakarta EE profile including servlets, EJB, JPA, JMS, CDI and web services, so applications packaged as WAR or EAR archives deploy without modification. Teams use it to run business applications that need a complete, certified Java runtime rather than a bare servlet container.

Why the cloudimg image

cloudimg ships WildFly preconfigured so the application server answers on the standard HTTP port as soon as the instance finishes its first boot, with nothing to install or wire together. The image is secure by default: no management account exists inside the image at all, and the server is held back from starting until first boot has provisioned unique per instance passwords for both the management realm and the application realm, so no default or shared credential ever exists on a running instance. The management console binds to the loopback interface only and is reached over an SSH tunnel rather than being published to the internet, the base is fully patched with unattended security upgrades enabled, and every deployment is paired with a step by step deploy guide and backed by 24/7 cloudimg support.

Common uses

  • Run enterprise Java applications on a certified Jakarta EE runtime
  • Deploy WAR and EAR archives to a managed application server
  • Host Java web services, EJB and JMS messaging workloads

See it running

Real screenshots taken while testing this image against its deployment guide.

WildFly 40 screenshot 1 WildFly 40 screenshot 2 WildFly 40 screenshot 3 WildFly 40 screenshot 4