Questo contenuto non è disponibile nella lingua selezionata.
Chapter 2. Supported Configurations
The only virtual machine operating systems supported for using JBoss EAP in Microsoft Azure are:
- Red Hat Enterprise Linux 7
- Red Hat Enterprise Linux 8
- Microsoft Windows Server 2016
- Microsoft Windows Server 2019
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.
- Azure Autoscale capabilities for JBoss EAP clustering
Vertical scaling is supported for all JBoss EAP clustering use cases.
The following horizontal scaling use cases are also supported:
Distributed HTTP sessions
-
Via
hotrod-session-management Via
infinispan-session-management-
Using
invalidation-cacheand a shared, persistent cache store
-
Using
-
Via
Distributed
@StatefulEJBsVia
infinispan-passivation-store-
Using
invalidation-cacheand a shared, persistent cache store
-
Using
Distributed EJB timers
-
Using
invalidation-cacheand a shared, persistent cache store
-
Using
JPA/Hibernate second-level cache
- Invalidation or local entity/collection/query caching only
Public WildFly clustering API
-
CommandDispatcherAPI GroupAPIRed Hat Datagrid (RHDG) cluster is the preferred choice for a shared, persistent cache store.
For a list of unsupported JBoss EAP clustering use cases, see Unsupported Azure Autoscale horizontal scaling for JBoss EAP clustering.
To set up a JBoss EAP clustering instance, see Setting up a clustering instance for JBoss EAP in Microsoft Azure.
-
2.1. JBoss EAP 7.4 OpenJDK images available in Microsoft Azure Copia collegamentoCollegamento copiato negli appunti!
In JBoss EAP 7.4, you can now use OpenJDK 8 images on Red Hat Enterprise Linux 8 virtual machines in Microsoft Azure via Azure Templates.
2.2. Unsupported Features Copia collegamentoCollegamento copiato negli appunti!
There are some unsupported features when using JBoss EAP in a Microsoft Azure environment.
- 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.
- Virtual Machine Scale Set
Transactions in Microsoft Azure Virtual Machine Scale Set (VMSS) is unsupported because the automatic scale down feature does not wait for all transactions to be completed during the scale down process. This could cause data integrity issues. Microsoft Azure VMSS destroys an EAP VM and does not support proper shutdown, which results in the following limitation for EAP clustering:
-
VMSS should be supported for the configurations, in which the server-side state for HA needs to be externalized to a third-party service, such as Red Hat Data Grid. JBoss EAP supports VMSS for
HttpSessionsexternalization, but not for the stateful session bean.
-
VMSS should be supported for the configurations, in which the server-side state for HA needs to be externalized to a third-party service, such as Red Hat Data Grid. JBoss EAP supports VMSS for
- Azure App Service
JTS is not supported in the JBoss EAP Azure App Service offering.
NoteAlthough JTS is not supported, Jakarta Transactions are supported under the following conditions:
- The automatic removal of instances is disabled.
- Instances are not removed manually, for example, by reducing the number of running instances using the Azure dashboard.
Also, transactions over Jakarta Enterprise Beans-remoting are not supported.
- Unsupported Azure Autoscale horizontal scaling for JBoss EAP clustering
The following JBoss EAP clustering use cases are not supported when scaling horizontally:
Distributed HTTP sessions
Infinispan-session-management- Using a distributed, replicated, or scattered cache
Distributed
@StatefulEJBsVia
infinispan-passivation-store- Using a distributed, replicated, or scattered cache
Distributed EJB timers
- When using a distributed, replicated, or scattered cache
- Singleton MDBs
JPA/Hibernate Second-Level Cache
- Distributed, replicated, or scattered entity/collection/query caching
- Singleton deployments
- Singleton MSC services
Public WildFly
clusteringAPI:-
RegistryAPI ServiceProviderRegistryAPIFor a list of supported JBoss EAP clustering use cases, see Azure Autoscale capabilities for JBoss EAP clustering.
To set up a JBoss EAP clustering instance, see Setting up a clustering instance for JBoss EAP in Microsoft Azure.
-