Anonymous_User Absent Member.
Absent Member.
1278 views

Patching the Appliance

I'm trying to get my SSPR 4.1.0.0 appliance up to 4.1.0.4, but the
documentation is a bit cryptic. I tried "apply a field patch" and
browsing to the sspr.war contained in SSPR-4.1.0.4.zip, but I get a null
pointer exception. Online Update doesn't work because the registration
process fails with an RPC error.

Can I just copy the new sspr.war over the existing one on the appliance?


Thanks


0 Likes
21 Replies
Knowledge Partner
Knowledge Partner

Re: Patching the Appliance

Black, Douglas wrote:

> Can I just copy the new sspr.war over the existing one on the appliance?


That's how it works for all non-applicance installs of SSPR I've ever patched.

Do not forget to export settings and DB and restore after the update, which is
something the appliance might have automated as part of the online update
process.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Knowledge Partner
Knowledge Partner

Re: Patching the Appliance

On 7/27/2017 2:30 AM, Lothar Haeger wrote:
> Black, Douglas wrote:
>
>> Can I just copy the new sspr.war over the existing one on the appliance?

>
> That's how it works for all non-applicance installs of SSPR I've ever patched.
>
> Do not forget to export settings and DB and restore after the update, which is
> something the appliance might have automated as part of the online update
> process.


In 4.something they added an env setting for where the conf file
resides. So you can move the SSPRConfiguration,XML and I guess the
localDB out of the tomcat/webapps/sspr/WEB-INF directory so that a
simple update of the WAR file and a redeploy should work.


0 Likes
Knowledge Partner
Knowledge Partner

Re: Patching the Appliance

Geoffrey Carman wrote:

> In 4.something they added an env setting for where the conf file resides. So
> you can move the SSPRConfiguration,XML and I guess the localDB out of the
> tomcat/webapps/sspr/WEB-INF directory so that a simple update of the WAR file
> and a redeploy should work.


Cool, I wasn't aware of that option.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Knowledge Partner
Knowledge Partner

Re: Patching the Appliance

On 7/27/2017 9:37 AM, Lothar Haeger wrote:
> Geoffrey Carman wrote:
>
>> In 4.something they added an env setting for where the conf file resides. So
>> you can move the SSPRConfiguration,XML and I guess the localDB out of the
>> tomcat/webapps/sspr/WEB-INF directory so that a simple update of the WAR file
>> and a redeploy should work.

>
> Cool, I wasn't aware of that option.


Ya, a nice update. Was a kind of silly config, having the config file
inside the replacable filesystem.

In fact, it won't start without that env setting I think.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Patching the Appliance

Lothar Haeger,


>
>> Can I just copy the new sspr.war over the existing one on the appliance?

>
> That's how it works for all non-applicance installs of SSPR I've ever patched.
>
> Do not forget to export settings and DB and restore after the update, which is
> something the appliance might have automated as part of the online update
> process.
>


I must be missing something -- I located sspr.war in
/var/lib/docker/devicemapper/mnt/<long string of
numbers>/rootfs/appliance/, copied the new sspr.war file over it, then
rebooted the appliance. When it came back up, it still says "SSPR
Version: v4.1.0.0 b256 r39020" in the top right.


0 Likes
Knowledge Partner
Knowledge Partner

Re: Patching the Appliance

Black, Douglas wrote:

> copied the new sspr.war file over it, then rebooted


there's usually an expanded folder named sspr next to the WAR file. Delete it
so it can be recreated from the WAR. It als contains config and DB in some
setups, so make sure to have both backed up.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Patching the Appliance

Lothar Haeger,

>> copied the new sspr.war file over it, then rebooted

>
> there's usually an expanded folder named sspr next to the WAR file. Delete it
> so it can be recreated from the WAR. It als contains config and DB in some
> setups, so make sure to have both backed up.
>


There isn't a folder named sspr next to the sspr.war file. There is one
under relative path /usr/local/tomcat/webapps, another under relative
path /usr/local/tomcat/work/Catalina/localhost/, and yet another
under /usr/local/ . I guess I should delete the one under webapps?

Thanks


0 Likes
Knowledge Partner
Knowledge Partner

Re: Patching the Appliance

Black, Douglas wrote:

> There is one under relative path /usr/local/tomcat/webapps, another under
> relative path /usr/local/tomcat/work/Catalina/localhost/, and yet another
> under /usr/local/ . I guess I should delete the one under webapps?


Both under webapps and work/Catalina. No idea what the one in /usr/local does,
how does the contents look like? Is the one under webapps a symlink to
/opt/local/sspr, maybe?

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Patching the Appliance

Lothar Haeger,

>
>> There is one under relative path /usr/local/tomcat/webapps, another under
>> relative path /usr/local/tomcat/work/Catalina/localhost/, and yet another
>> under /usr/local/ . I guess I should delete the one under webapps?

>
> Both under webapps and work/Catalina. No idea what the one in /usr/local does,
> how does the contents look like? Is the one under webapps a symlink to
> /opt/local/sspr, maybe?
>


No, but /usr/local/sspr is an empty folder, so I guess I don't need to
delete that one.

Thanks
0 Likes
Micro Focus Contributor
Micro Focus Contributor

Re: Patching the Appliance

Black, Douglas;2462985 wrote:
Lothar Haeger,

>
>> There is one under relative path /usr/local/tomcat/webapps, another under
>> relative path /usr/local/tomcat/work/Catalina/localhost/, and yet another
>> under /usr/local/ . I guess I should delete the one under webapps?

>
> Both under webapps and work/Catalina. No idea what the one in /usr/local does,
> how does the contents look like? Is the one under webapps a symlink to
> /opt/local/sspr, maybe?
>


No, but /usr/local/sspr is an empty folder, so I guess I don't need to
delete that one.

Thanks


Manually copying any files on to the appliance is a bad idea. This is absolutely not the right way to upgrade the appliance. Do not use this procedure.

The documentation for updating the appliance is here:

https://www.netiq.com/documentation/self-service-password-reset-41/adminguide/data/onlineupdate.html

Following this process will keep both the OS and the application patches updated with current OS and application releases and ensuring that the entire patch is pre-tested before being released to the update channel. There is no off-line method for updating the appliance.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Patching the Appliance

jrivard,

> Manually copying any files on to the appliance is a bad idea. This is
> absolutely not the right way to upgrade the appliance. Do not use this
> procedure.
>
> The documentation for updating the appliance is here:
>
> https://www.netiq.com/documentation/self-service-password-reset-41/adminguide/data/onlineupdate.html
>
> Following this process will keep both the OS and the application patches
> updated with current OS and application releases and ensuring that the
> entire patch is pre-tested before being released to the update channel.
> There is no off-line method for updating the appliance.
>




Thanks for the warning. I did try the online update procedure but it
failed. I don't remember the exact wording of the error message; I will
try again and post that information.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.