Run JBoss EAP workloads on Azure Virtual Machines and VM Scale Sets
JBoss EAP is a leading Java application server running some of the most mission-critical enterprise applications in the world. This solution automates most boilerplate steps to provision a single JBoss EAP instance on an Azure Virtual Machine. Once initial provisioning is complete, you are completely free to customize deployments further. The solution is jointly developed by Red Hat and Microsoft.
The following resources are automatically provisioned by the offer.
- Red Hat Enterprise Linux (RHEL) VM
- JBoss EAP standalone instance (EAP_HOME is /opt/rh/eap7/root/usr/share/wildfly).
- JBoss EAP management console
- Red Hat build of OpenJDK (JAVA_HOME is a subdirectory of /usr/lib/jvm, depending on the selected JDK version).
- Virtual network and subnet (alternatively, you can deploy to an existing virtual network)
- Network security group
- Network interface with public IP address
This offer requires a JBoss EAP subscription and works on a Bring-Your-Own-Subscription (BYOS) basis. For the RHEL part of the offer, you have a choice to use either Pay-As-You-Go (PAYGO) or BYOS. In case of PAYGO, there is an additional hourly RHEL subscription charge for using this offer on top of the normal Azure compute, network and storage costs. To use RHEL BYOS, you must contact Red Hat to get your subscription enabled on Azure. Once you do so, the RHEL BYOS options will become visible as plans.
Red Hat and Microsoft also provide basic step-by-step instructions on getting started with JBoss EAP and RHEL without automated provisioning.
Red Hat and Microsoft provide similar solutions targeting JBoss EAP on a cluster of VMs, Azure Red Hat OpenShift (ARO) and App Service. These options are linked in the Learn more section below.
You can reach out to the engineering team developing these offers by clicking the CONTACT ME button on the marketplace JBoss EAP on Azure overview page. Program managers, architects and engineers will get in touch and can assist you for free with your Azure migration.