JBoss setup to support the clustered configuration for Pega
Currently Customer uses Jboss application server setup for Pega v63 sp1. There is a question whether Pega really needs clustered configuration on JBoss and if it relies on the application server specific HA features. Can the customer update the JBoss configuration by changing to the “non-HA” profile?
Also there is a plan to upgrade to 7.x . Does 7.x leverage any application server configuration for clustering / HA ?
***Updated by moderator: Lochan to add Categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
we do not mandate one way or another. The only thing you need to remember is that you need to use standalone-full and above (including HA) for ear deployment whereas war deployment you only need standalone profile. Since Pega is not using any of the JBoss clustering features, use standalone-full, that is what is documented in the installation guide. In reality, I have seen customers using HA proifles as well. For 63sp1, we do not even support jboss eap 6.x, so that is not part of the discussion here.
Keep up to date on this post and subscribe to comments
- Setup Pega 7.1.9 with JBoss mod_clustering using only TCP
- What configurations are required to setup MDB listener in Pega (JBOSS Server) to read from remote queue hosted in different server?
- Can we setup a centralized AES for both JBOSS and WAS pega JVM's. Similarly can we setup a centralized SMA to add pega nodes running on both JBOSS and WAS
- Is JVM clustering required for PEGA AES setup
- Pega 7.1.9 JBOSS setup