Chapter 2. Supported Configurations
The only virtual machine operating systems supported for using JBoss EAP in Microsoft Azure are:
- Red Hat Enterprise Linux 7
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2016
The Red Hat Cloud Access program allows you to use a JBoss EAP subscription to install JBoss EAP on your own Azure virtual machine or one of the above On-Demand operating systems from the Microsoft Azure Marketplace. Note that virtual machine operating system subscriptions are separate from a JBoss EAP subscription.
Other than the above operating system restrictions, see the Customer Portal for further information on supported configurations for JBoss EAP, such as supported Java Development Kit (JDK) vendors and versions.
2.1. Unsupported Features
There are some unsupported features when using JBoss EAP in a Microsoft Azure environment.
- Managed Domains
- JBoss EAP managed domains are not supported in Microsoft Azure. Only standalone JBoss EAP server instances are supported. Note that configuring JBoss EAP clusters using standalone JBoss EAP servers is supported in Azure.
- ActiveMQ Artemis High Availability Using a Shared Store
- JBoss EAP messaging high availability using Artemis shared stores is not supported in Microsoft Azure. To configure JBoss EAP messaging high availability in Azure, see the instructions in the ActiveMQ Artemis High Availability section.
- mod_custer Advertising
- If you want to use JBoss EAP as an Undertow mod_cluster proxy load balancer, the mod_cluster advertisement functionally is unsupported because of Azure UDP multicast limitations. You must configure mod_cluster load balancing to use a proxy list instead of advertising.