UPS Migration Documentation

[William Eddy]

I am unable to find documentation for migrating versions of Aerogear UnifiedPush.

From what I can find there is

1. Docs describing a 1.0.x to 1.0.3 migration
1. https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide
   
2. Service for migrating that is a few years out of date
1. https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/migrator

Is there any support for updating past 1.0.3? Currently running 1.1.3 in Production and need to update to 1.2.4 to use FCM, are there docs for this migration in particular?

Thanks,

William Eddy

[William Eddy]

Update from IRC;

[14:00] <will_> I'm using an older version of the unifiedpush server and would like to upgrade. The only documentation I see is for getting to 1.0.3 from previous 1.0.x. Is there documentation for later releases?

[14:21] <grdryn[m]> will_ hi! If you don't get an answer here, you might have better luck on the mailing list (aerogear on Google groups, I think it's aero...@googlegroups.com (sorry, I'm afk, so not 100% sure))

[14:23] <grdryn[m]> will_ also, I'm no expert, but I _think_ UPS has some built-in migration stuff, for the likes of database schema changes and stuff

[14:23] <grdryn[m]> Again, not a UPS expert, I could even be thinking of a different project

[14:25] <grdryn[m]> summersp or passos or ziccardi or pbraun might be able to give better information if they're around! ;-)

[14:28] <+passos> will_: grdryn[m] I don't touch in migration in years. I don't know if it's updated

[14:28] <+passos> Need to check

[14:30] <will_> Hi guys, I looked into the migration functionality in github and it looks out of date.

[14:30] <will_> I joined the mailing group as well, https://groups.google.com/forum/#!topic/aerogear/aCWvoZr9KPc

[14:30] <+jbossbot> Title: Google Groups

[14:32] <+passos> will_: I will try to take a look and reply your email ASAP

[14:33] <will_> Thanks, passos :) and thanks grdryn for the help

[14:33] <+passos> I think there is no change from 1.x to 2.x in the database, but I will give it try and let you know

[14:33] <+summersp> will_, Good news, bad news situation.  The good news is that the data model should be/is the same from 1.1.x series to the 2.x series.  We have tools in the migrator package that are based on liquibase.  So upgrading your data should be as easy as using those tools.  Upgrading UPS is a little bit harder or easier depending on your situation.  If you can replace your old app server then you can run the dockerized UPS and pass it the database

[14:33] <+summersp> parameters as environment variables.

[14:33] <+summersp> If you can't then things get trick with having to set up JMS queues and such in wildfly/jboss

[14:33] <+summersp> and by tricky I mean you have to run a script to create the queues and replace the war file

[14:37] <will_> Alright, our minimum requirement is to migrate our production to 1.2.x to use FCM so we'll start with that. It sounds like a straightforward process for that small of an update, just replace the war file and start it up. Is that a fair assessment?

[14:37] <will_> To 1.2.x from 1.1.3*

[14:38] <+summersp> will_, I think so.  It has been a few years since I did that upgrade so my memory might be rusty

[14:38] <+summersp> Make sure you have backups :)

[14:38] <will_> Haha will do. I'll update on the mailing group how it goes for anyone else who may have this issue

[14:38] <will_> Thanks again

[14:38] <+summersp> Thanks

[14:38] <+summersp> No problem

Will send a follow up with findings / results from migration

[nvg]

Hi William,

We have the same problem with the upgrade.
Did you have any luck upgrading to a FCM compatible version?

Thanks

[Tejas Bhanushali]

hello nvazquez,

How did you managed to upgrade to the latest version? can you please share some tips here as I'm also facing the same issues.

Thanks & Regards,

Tejas