Grouper Users - Open Discussion List

["Sawyer, Mona Zarei" <>]

Thanks a lot Chris and James for your help and suggestions.

Thank you so much.
Best Regards,
Mona.
 
Mona Z Sawyer M.Sc.
Programmer Intermediate
Middleware and Identity Services
Information Technology
University of Miami
1320 S. Dixie Hwy
Suite 1000.49
Coral Gables, Fl 33146
305-284-2214
 
"At the U, we transform lives through teaching, research and service."



-----Original Message-----
From: Hyzer, Chris 
[mailto:]
 
Sent: Friday, September 29, 2017 3:44 PM
To: James Babb 
<>;
 Sawyer, Mona Zarei 
<>;
 Petursson, Sigurdur 
<>;
 Wessel, Keith 
<>
Cc: 

Subject: RE: [grouper-users] RE: Patching and ant dist

We want to start being able to keep some/most configs in the DB which will 
help with this too

-----Original Message-----
From: James Babb 
[mailto:]
Sent: Friday, September 29, 2017 3:43 PM
To: Sawyer, Mona Zarei 
<>;
 Hyzer, Chris 
<>;
 Petursson, Sigurdur 
<>;
 Wessel, Keith 
<>
Cc: 

Subject: Re: [grouper-users] RE: Patching and ant dist

If I need to make a change to one of the config files, I tend to just copy 
the changed file in to the already built UI and WS:

E.g. ./grouper.apiBinary-2.3.0/conf/grouper-loader.properties  

...is copied to...

./grouper.ws-2.3.0/grouper-ws/build/dist/grouper-ws/WEB-INF/classes/grouper-loader.properties
./grouper.ui-2.3.0/dist/grouper/WEB-INF/classes/grouper-loader.properties

Downside is that is a manual process and missed steps do happen sometimes. 

In my dev environment, which uses Docker files and automatic building on 
commit in Jenkins, I am less concerned about having to rebuild/repatch every 
time since the build and deployment happens in the background. It also 
enforces that both of my Grouper servers are using the same configuration—not 
something that is slowly drifting apart as a change is made on one but not 
the other. :)

As for automated patching, I recommend you check out: 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fspaces.internet2.edu%2Fdisplay%2FGrouper%2FGrouper%2Binstaller%2Bnon%2Binteractive%2Bmode&data=02%7C01%7Cmonaz%40miami.edu%7C2560cbc41f0d4e6a4ff508d50772689c%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636423110321498117&sdata=7IfvRiD04Kku%2F5pLodh6xw7FYysU0RSigCohxrhfT7g%3D&reserved=0

The Grouper Installer has a pretty extensive set of options you can specify 
in a file to have it automatically apply all patches without user 
intervention. Here is a simple unattended file for the grouper-installer to 
patch the UI:

grouperInstaller.autorun.useDefaultsAsMuchAsAvailable = true 
grouperInstaller.autorun.actionEgInstallUpgradePatch = patch 
grouperInstaller.autorun.tarballDirectory = /tmp/grp-ui 
grouperInstaller.autorun.appToUpgrade = ui 
grouperInstaller.autorun.grouperWhereInstalled = 
/opt/webapps/grouper.ui-2.3.0/dist/
grouperInstaller.autorun.patchAction = install grouper.version = 2.3.0 
download.server.url = 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsoftware.internet2.edu%2Fgrouper&data=02%7C01%7Cmonaz%40miami.edu%7C2560cbc41f0d4e6a4ff508d50772689c%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636423110321498117&sdata=g%2F%2FVYCWtgf9exObuFzHV3qztfsSTbtQvBmw4TGvC%2B1E%3D&reserved=0


--
James Babb
Enterprise Identity Management Technologist Division of Information 
Technology University of Wisconsin-Madison 



 

On 9/29/17, 2:08 PM, 
"
 on behalf of Sawyer, Mona Zarei" 
<
 on behalf of 
>
 wrote:

    I am referring to changes in grouper-loader.properties , sources.xml or 
log4j.properties files. Which are located on " 
home/grouper.apiBinary-2.3.0/conf/".
    So you mean, we can build and then patch once and make further changes to 
these properties files without any needs to rebuild again?
    
    
    Thank you so much.
    Best Regards,
    Mona.
     
    Mona Z Sawyer M.Sc.
    Programmer Intermediate
    Middleware and Identity Services
    Information Technology
    1320 S. Dixie Hwy
    Suite 1000.49
    Coral Gables, Fl 33146
    305-284-2214
     
    "At the U, we transform lives through teaching, research and service."
    
    
    
    -----Original Message-----
    From: Hyzer, Chris 
[mailto:]
 
    Sent: Friday, September 29, 2017 2:46 PM
    To: Sawyer, Mona Zarei 
<>;
 Petursson, Sigurdur 
<>;
 Wessel, Keith 
<>;
 

    Subject: RE: [grouper-users] RE: Patching and ant dist
    
    What source for the loader are you referring to?  Change log consumer?  
If so that should be in your own jar on your own classpath.  You can just 
copy that to the built target.  And properties file changes can be copied to 
the built target.  No need to rebuild.
    
    Thanks
    Chris
    
    -----Original Message-----
    From: Sawyer, Mona Zarei 
[mailto:]
    Sent: Friday, September 29, 2017 2:32 PM
    To: Hyzer, Chris 
<>;
 Petursson, Sigurdur 
<>;
 Wessel, Keith 
<>;
 

    Subject: RE: [grouper-users] RE: Patching and ant dist
    
    Any time we have a new source for the loader or need to provision into a 
different AD we need to update the properties files and for them to get into 
effect we need to rebuild.
    
    Mona.
     
    Mona Z Sawyer M.Sc.
    Programmer Intermediate
    Middleware and Identity Services
    Information Technology
    1320 S. Dixie Hwy
    Suite 1000.49
    Coral Gables, Fl 33146
    305-284-2214
     
    "At the U, we transform lives through teaching, research and service."
    
    
    
    -----Original Message-----
    From: 

 
[mailto:]
 On Behalf Of Hyzer, Chris
    Sent: Friday, September 29, 2017 2:25 PM
    To: Petursson, Sigurdur 
<>;
 Wessel, Keith 
<>;
 

    Subject: RE: [grouper-users] RE: Patching and ant dist
    
    Just curious, why do you need to rebuild?  The patches have the latest 
code in there.  If you are editing files and want to incorporate them then 
need to rebuild, but for hooks or plugins you can just make your own jar and 
not bother with rebuilding grouper.
    
    With the one command to apply all patches we have tried to make it not 
very cumbersome.
    
    If you don’t apply patches on top of a build then things could get messy 
if you are editing or downloading files on top of patches.  The patches make 
sure that the underlying files are not edited when they are applied.
    
    Thanks
    Chris
    
    -----Original Message-----
    From: 

 
[mailto:]
 On Behalf Of Petursson, Sigurdur
    Sent: Friday, September 29, 2017 12:06 PM
    To: Wessel, Keith 
<>;
 

    Subject: Re: [grouper-users] RE: Patching and ant dist
    
    We have been kicking the tires on Grouper for over a year now and this is 
the first time we are hearing about this. Re-build should of course not wipe 
out previously installed patches. Now, a separate function called factory 
reset would wipe out patches and configuration but a rebuild should simply 
rebuild with any code and patches in place.
    
    This is particularly important with Grouper where the patching process is 
very cumbersome and somewhat flawed. I will surely look at the wiki and adopt 
the automation of patching.
    
    I hope the Grouper team reconsiders the patching process and finds ways 
to improve, as well as the rebuild with respect to patching.
    
    Thanks.
    
    Sig
    
    On 9/28/2017 1:36 PM, Wessel, Keith wrote:
    > And thank YOU for the help on this one!
    >
    > keith
    >
    > -----Original Message-----
    > From: Hyzer, Chris 
[mailto:]
    > Sent: Thursday, September 28, 2017 12:28 PM
    > To: Wessel, Keith 
<>;
 

    > Subject: RE: Patching and ant dist
    >
    > I added a note on the wiki, thanks.  Chris
    >
    > -----Original Message-----
    > From: 

    > 
[mailto:]
 On Behalf Of Wessel, 
    > Keith
    > Sent: Thursday, September 28, 2017 11:46 AM
    > To: 

    > Subject: [grouper-users] RE: Patching and ant dist
    >
    > Thanks for that explanation, Sir. Yeah, we've all but fully automated 
    > patching thanks to the script you posted to the wiki, and that should 
    > help. We'll just keep that in mind when we rebuild. Perhaps there 
    > should be a note on the Grouper patching instructions page on the wiki 
    > mentioning that you must repatch after rebuilding? It should be common 
    > sense, but it obviously wasn't to us. :)
    >
    > Looking forward to the Grouper workshop at TechEx so we can learn a few 
more tidbits like this!
    >
    > Keith
    >
    >