Announce: Database Backed Storage Service

[Wessel, Keith]

Thanks, both of you. This is what I was thinking I could do, Paul, but I couldn't' figure out where to put the hibernate.properties. tomcat/lib makes sense.

Scott, hadn't thought of the parallel attribute resolver. Good call. Are you suggesting just cloning the $IPD_HOME/conf dir, modifying the storedid connector definition to use local settings instead of my container managed connection, then passing in that cloned dir using the --configdir option to aacli?

Thanks,
Keith


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Tuesday, October 01, 2013 3:13 PM
To: Shib Users
Subject: Re: Announce: Database Backed Storage Service

On 10/1/13 4:09 PM, "Paul Hethmon" <paul.hethmon at clareitysecurity.com>
wrote:
>
>I can tell you how I handle it. I use the Tomcat container managed 
>connections, because I get better pool management from it. I then put 
>my hibernate.properties in the Tomcat lib directory. So all DB 
>configuration is done at the Tomcat level, not the webapp level. The 
>hibernate.properties essentially just becomes a pointer to the 
>container managed stuff. If I have data resolvers that use a RDMS, I 
>use the syntax to point them directly at the container managed connection.

I'd add that you can make aacli work at the same time by creating a parallel version of the resolver config that uses app pools with the same definitions otherwise.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net