Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Grouper Deployment Infrastructure

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Grouper Deployment Infrastructure

Chronological Thread 
  • From: Gagné Sébastien <>
  • To: "Bryan E. Wooten" <>, <>
  • Subject: RE: [grouper-users] Grouper Deployment Infrastructure
  • Date: Thu, 16 May 2013 08:38:59 -0400
  • Authentication-results:; dkim=neutral (message not signed) header.i=none

For your information, here is our deployement :

(the thin vertical boxes are F5 Load balancers)


Your deployment looks similar, but here we kept the UI and WS on the same tomcat (we don’t really use the WS anyway), we also have proxy webservers to please our firewall guys.


Our backend (UI+API+Daemon) servers are using about 3gb of disk space, so disk usage is minimal (we have a 20g partition for Grouper). They also have 4gb of RAM, it’s working, but if I could I would bump this up to 6gb. In your case since the Daemon is running on another server this might not be necessary




De : [mailto:] De la part de Bryan E. Wooten
Envoyé : 15 mai 2013 13:59
À :
Objet : [grouper-users] Grouper Deployment Infrastructure


Hi all,


I have drawn up this diagram showing all the servers needed to deploy Grouper in a production environment.


The red shaded items are peripheral / supporting  to the Grouper installation.


Any feedback would be appreciated. I would like to add minimum ram and disk requirements, rules of thumb would be appreciated. Do I have a reasonable fault tolerant / high availability configuration? Anything else I need to warn our server guys about?


Also I could use guidance on how long to keep log files and any suggested backup strategies beyond normal Oracle DB backups.





Archive powered by MHonArc 2.6.16.

Top of Page