Using JDG as External Cache Container for WildFly HTTP Session Replication: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
JDG can be used as an external cache container for HTTP session data within WildFly. This allows scaling of the data layer independent of the application, and enables different WildFly clusters, that may reside in various domains, to access data from the same JDG cluster. | JDG can be used as an external cache container for HTTP session data within WildFly. This allows scaling of the data layer independent of the application, and enables different WildFly clusters, that may reside in various domains, to access data from the same JDG cluster. | ||
=Setup the JDG Cluster= | |||
Configuration details are available here [[Infinispan Configuration]]: . The external JDG cluster will be accessed by the WildFly instance over the HotRod protocol. | |||
Revision as of 00:11, 1 June 2016
External
- Externalizing Sessions with JDG https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.6/html/Administration_and_Configuration_Guide/chap-Externalize_Sessions.html
Internal
Overview
JDG can be used as an external cache container for HTTP session data within WildFly. This allows scaling of the data layer independent of the application, and enables different WildFly clusters, that may reside in various domains, to access data from the same JDG cluster.
Setup the JDG Cluster
Configuration details are available here Infinispan Configuration: . The external JDG cluster will be accessed by the WildFly instance over the HotRod protocol.