Those links reference versions 3 and 5. We're using 6. And they mostly cover the information I already linked to.
It still doesn't really explain why it's important to have an HA front end web server with a back end that is not resilient.
Or why you need multiple web servers to handle the load but only ever need one of each back end server.
I can't find anything that explains how to cluster the back end nodes. Or if it's even possible.
I've done the architecture on a Jive 6 on-premise environment. If you think about the services that an on-premise environment has it really breaks down to this:
- Jive httpd and application
- Cache/Cluster service
- Document Conversion service
- Activity Engine service
- Search Service
The database server should be part of an HA environment. The Jive application connects to the database and handles the load of your user base, so there should be 2 or more of these servers depending on the number of users, pageviews, etc.
Clustering service can be made HA, but you need 3 or more boxes if you do so. I decided to have only 1. You can have multiple document conversion nodes, but each acts independently, but in reality you only need 1. The search service is just setup to essentially contain the full-text index and offload processing to that box. I don't believe you can set that up in a cluster, but honestly haven't dived too deeply into it. If the search server goes down, all that happens is you have to spin the service up on another machine, and rebuild the index. You can have multiple activity engine servers and break down their roles to doing either inout, in, or out servicing.
What I did to make sure there wasn't massive disruption in service should the cache/cluster node, activity engine, or search services go down, or If I need any additional application node from the 3 that I have clustered; was to build a separate box with all the services installed, and have config ready and documented to quickly place that box into the lineup should a failure exist.
There are many aspects into making this design work, but my constraints were budget related and my customers were internal non-customer facing users. If I were architecting for a customer facing on-premise solution and budget wasn't an issue, I would have done it slightly different.
Please keep in mind, these are just my opinions and not something that I got from Jive.
Hope that helps.