Grouper Users - Open Discussion List

[Scott Koranda <>]

Excellent.

Precisely the "cheat sheet" I needed to save me some real time.

Thanks much,

Scott K

> Yes, we download the api binary, ws, and ui without the installer and then
> patch accordingly with the grouper installer. The way we do it is the 
> following
> (from our Dockerfile for the API):
> 
>  
> 
> ---
> 
>  
> 
> RUN set -x \
> 
>     && echo 'Downloading Grouper Installer...' \
> 
>     && wget -q http://software.internet2.edu/grouper/release/2.3.0/
> grouperInstaller.jar \
> 
>    
> 
> # Download the Grouper API
> 
>     && echo 'Downloading Grouper API...'\
> 
>     && wget -q http://software.internet2.edu/grouper/release/2.3.0/
> grouper.apiBinary-2.3.0.tar.gz \
> 
>     && tar -zxf grouper.apiBinary-2.3.0.tar.gz -C /mst \
> 
>  
> 
> # Patch the API using the installer
> 
>     && echo 'Patching Grouper API...'\
> 
>     && mkdir /tmp/grp-api/ \
> 
>     && cp /mst/installer-scripts/grouper.installer-api.properties /mst/
> grouper.installer.properties \
> 
>     && ${JAVA_HOME}/bin/java -cp .:/mst/grouperInstaller.jar
> edu.internet2.middleware.grouperInstaller.GrouperInstaller \
> 
>  
> 
> # And some final cleanup
> 
>     && rm -rvf grouper.apiBinary-2.3.0.tar.gz /tmp/grp-api/  /mst/
> grouper.installer.properties \
> 
>  
> 
> ---
> 
>  
> 
> And the grouper.install.properties file:
> 
>  
> 
> ---
> 
>  
> 
> grouperInstaller.autorun.useDefaultsAsMuchAsAvailable = true
> 
> grouperInstaller.autorun.actionEgInstallUpgradePatch = patch
> 
> grouperInstaller.autorun.tarballDirectory = /tmp/grp-api
> 
> grouperInstaller.autorun.appToUpgrade = api
> 
> grouperInstaller.autorun.grouperWhereInstalled = 
> /mst/grouper.apiBinary-2.3.0
> 
> grouperInstaller.autorun.patchAction = install
> 
> grouper.version = 2.3.0
> 
> download.server.url = http://software.internet2.edu/grouper
> 
>  
> 
> ---
> 
>  
> 
> Note that UI and WS require building with ant if you download the tar ball.
> They can be patched with the same sort of unattended properties file.
> 
>  
> 
>  
> 
> --
> 
> James Babb
> 
> Enterprise Identity Management Technologist
> 
> Division of Information Technology
> 
> University of Wisconsin-Madison
> 
> 
> 
>  
> 
>  
> 
>  
> 
> On 8/3/17, 2:20 PM, 
> "
>  on behalf of Hyzer,
> Chris" 
> <
>  on behalf of 
> >
> wrote:
> 
>  
> 
>     Of course!  :)
> 
>    
> 
>     The patcher doesn't know or care how you installed.  And actually, the
> installer just does manual steps for you, you could do all that stuff 
> manually
> and just skip the parts about configuring the hibernate config, starting 
> things
> up, doing the DDL, etc.
> 
>    
> 
>     Thanks
> 
>     Chris
> 
>    
> 
>     -----Original Message-----
> 
>     From: Scott Koranda 
> [mailto:]
> 
>     Sent: Thursday, August 03, 2017 3:14 PM
> 
>     To: Hyzer, Chris 
> <>
> 
>     Cc: grouper-users 
> <>
> 
>     Subject: Re: [grouper-users] installing without a running database
> 
>    
> 
>     > When you install you need a database, but you can temporarily use 
> HSQLDB.
> 
>     >
> 
>     
> 
>     Thanks.
> 
>    
> 
>     Suppose I want to avoid having to use HSQLDB (or any database) at
> 
>    install time.
> 
>    
> 
>     Could I install from Java source files (not using grouperInstaller.jar)
> 
>     but then still use grouperInstaller.jar to deploy the patches?
> 
>    
> 
>     Thanks,
> 
>    
> 
>     Scott K
> 
>    
>