Port Integrations to new version
When upgrading from 2021 to 2022 via the create new server update methodology, how do we ensure that all the integrations and other settings get ported over to the new version?
-
Hi Rita,
Thank you for reaching us via our Community Forums!
BarTender 2021 is fully compatible with BarTender 2021 installations; This allows for a much smoother update plan, and if you update your BarTender environment by installing it over the top, all integrations and other settings should remain unchanged from your customized options and integrations. That being said, please take a moment to review our article on the subject, and remember to take a snapshot of your machines or create a backup you can roll back to in case there are any issues with the update plan.
Updating to BarTender 2022
Let us know if there is anything else we can do you for.0 -
- Because the Updating to BarTender 2022 instructions recommended that 2022 be installed on a new server and tested there, I need a way to port my integrations to the new server. How do I do that?
- One of the instructions (see section titled: "I'm setting up a totally new environment for BarTender's 2022 Licensing Server and BarTender clients.") recommended testing on the new server and then at go live of 2022 make that the production server. In this approach all the integrations and other settings from the administration console would be needed on the new server. How do they get there?
- Another deployment approach is titled: "I'm setting up a new environment for BarTender's Licensing Server and will update existing BarTender clients to 2022". Since my environment has both the client and license server on the same VM, would this deployment approach be a bad idea? Or if it is feasible, doesn't it still have the same issue that integrations need to be run in the sandbox to know if they will have issues. And that means we need a migration approach for those integrations?
0 -
I just want to share want we found with you
If Bartender 2022 was install over 2021 in the same machine integrations will carry over automatically,
If you setup a new machine then just copy source btin and other realted files(btw, database) with it and redeploy btin one by one.But on v.2022 we found that integrations are heavily delayed, after working with support we found that Integration service keeps restart it self every a few minutes, happen on both new and clean install of windows server + bartender 2022 and machine that bartender 2022 upgrade from 2021
(no workarround yet, when integration service is down both integration jobs and API will not working)So I sugguest you to test this first and keep eye on Integration.Service.Startup.txt in "C:\ProgramData\Seagull\Services\Logging" folder
you might see something like this in your log file if Integration keep crashing like what we found.
2022.05.21.145731: Warn: 'Seagull.Services.Integration.WebService.exe' process is not responsive. Disposing it...
2022.05.21.145731: Info: Starting a new 'Seagull.Services.Integration.WebService.exe' process...
2022.05.21.145821: Warn: 'Seagull.Services.Integration.WebService.exe' process is not responsive. Disposing it...
2022.05.21.145821: Info: Starting a new 'Seagull.Services.Integration.WebService.exe' process...
2022.05.21.145951: Warn: 'Seagull.Services.Integration.WebService.exe' process is not responsive. Disposing it...
2022.05.21.145951: Info: Starting a new 'Seagull.Services.Integration.WebService.exe' process...
2022.05.21.150151: Warn: 'Seagull.Services.Integration.WebService.exe' process is not responsive. Disposing it...
2022.05.21.150151: Info: Starting a new 'Seagull.Services.Integration.WebService.exe' process...
2022.05.21.150411: Warn: 'Seagull.Services.Integration.WebService.exe' process is not responsive. Disposing it...
2022.05.21.150411: Info: Starting a new 'Seagull.Services.Integration.WebService.exe' process...0
Iniciar sesión para dejar un comentario.
Comentarios
3 comentarios