Grouper Developers Forum

[Chris Hyzer <>]

Sure :)

In your grouper.hibernate.properties, don’t put environment specific 
information there (though you could put institution specific if you like).  
Just have an entry like this in there:

# comma separated config files that override each other (files on the right 
override the left)
# each should start with file: or classpath:
# e.g. classpath:grouper.hibernate.base.properties, 
file:c:/temp/myFile.properties
grouper.hibernate.config.hierarchy = 
classpath:grouper.hibernate.base.properties, 
classpath:grouper.hibernate.properties, file: 
/etc/grouper/grouper.hibernate.local.properties

or you could take out the grouper.hibernate.properties one, or you could name 
the local one grouper.hibernate.properties, whatever you want.  You might 
want to put custom setting that apply to all envs in the 
classpath:grouper.hibernate.properties.  Note, you might have to do this in 
other config files too..

Thanks,
Chris

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Waldbieser, Carl
Sent: Monday, November 17, 2014 12:07 PM
To: 

Subject: [grouper-dev] Can `grouper.hibernate.properties` be externalized 
from WAR file?


I am building a native package (RPM) for our Grouper pilot deployment on 
RHEL6.  During a test deployment to a QA host, I noticed that the Grouper UI 
WAR file had made a copy of the 
$GROUPER_HOME/conf/grouper.hibernate.properties file from the build host.

Is there some way that the settings can be externalized (to say something 
like `/etc/grouper/grouper.hibernate.properties`) so that there is a single 
place from which both the API and the UI get their hibernate settings?  

I would really like to be able to build a single software artifact and deploy 
it to QA and production environments, and not have to build a separate WAR 
for each environment.

Thanks,
Carl Waldbieser
ITS System Programmer
Lafayette College