Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

> 1. When patching one server the process could potentially cause 
> an outage or locking issues to the other three servers if the 
> patch manipulates a DB table ?

Patches don’t manipulate database tables

> 
> Is the rule of thumb always complete Patching / Upgrades after 
> hours or run a Status Check to understand the patches.. 

I would do them off hours

> 
> 2. Im gathering the installer won’t advise a caution statement 
> “Outage May Occur” on a specific patch when running Status option 
> against the application (UI, WS, API, PSPNG) 

Yes, if it detects a java change it will prompt you to restart.  You can see 
that in dev.  If it is just a JSP or config file (rare), then you might not 
need to restart, but I would assum you always need to

Thanks
Chris

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

 
[mailto:]
 On Behalf Of Reid Watson
Sent: Monday, May 21, 2018 11:25 PM
To: 

Subject: [grouper-users] Upgrade and Patching Advice

Hi Everyone, 

I have just been introduced to the Grouper Upgrade / Patching Process and I 
have some basic questions 

Current Enviornment 

- 4 Grouper servers within Production Environment
- 1 Oracle DB 
- I understand we backup the DB / and required Paths before running an 
upgrade / patching process 
- I have been through the training video and reviewed 
“https://spaces.internet2.edu/display/Grouper/Grouper+patching";

Basic Questions 

1. When patching one server the process could potentially cause an outage or 
locking issues to the other three servers if the patch manipulates a DB table 
?

Is the rule of thumb always complete Patching / Upgrades after hours or run a 
Status Check to understand the patches.. 

2. Im gathering the installer won’t advise a caution statement “Outage May 
Occur” on a specific patch when running Status option against the application 
(UI, WS, API, PSPNG) 

Cheers

Reid