Skip to main content
  • EN

Hello,

We are in a process of upgrading fme 2016 to 2019. After some tests that passed well we need to move all our components to use fme 2019.

 

 

Normally what we would do is to create backup of fme 2016 and restore it on 2019. And this is what we did initially, Then for 2 weeks both 2016 and 2019 was running thats why we have some new things on 2016 and some on 2019.

 

 

What we need to migrate from 2016 to 2019 are only schedules that were created after given date.

 

 

For some reason I can't create normal backup on fme 2016 right now. I wrote it to safe support and they know that in this build there is a bug so we would need to apply fot fix.

 

 

My idea to do it in a different way is to:

 

 

1. Use fme 2016 desktop to export FME Server Configuration to ffs file (choosing repository and scheduling)

 

2. Run fme 2016 desktop to write from ffs file to fme server configuration of fme 2019 only scheduling with insert mode.

 

 

Will it work and I will not do any damages to new fme 2019 database configuration?

 

 

Thanks for any hints.

I think a better option would be to use the REST API but I am not sure whether the 2016 one offers access to the schedules and whether or not there is any differences between 2016 and 2019 in that respect. It's a big step. One option that has been removed in FME 2019 is to set monthly schedules (you can still do that but have to go through CRON)

If you do that, I strongly suggest you keep an eye on it for the first triggers of the schedule.

Alternatively, if there's not too many, you can also replace them manually (or make Automations out of them)

I think a better option would be to use the REST API but I am not sure whether the 2016 one offers access to the schedules and whether or not there is any differences between 2016 and 2019 in that respect. It's a big step. One option that has been removed in FME 2019 is to set monthly schedules (you can still do that but have to go through CRON)

If you do that, I strongly suggest you keep an eye on it for the first triggers of the schedule.

Alternatively, if there's not too many, you can also replace them manually (or make Automations out of them)

Hello,

 

 

Ok you are right, in web portal there is no option to create schedule that would run once every month without using CRON:

 

 

but on the other hand in rest api v3 documentation there is:

 

 

 

 

Reply


Community Stats

29,696
Posts
112,872
Replies
37,356
Members
Terms & ConditionsCookie settings