We would like to know if there are any ramifications swapping out our code database while an Ensemble production is running. We are trying to minimize down time as much as possible and even though stopping and starting the production ideally would be pretty quick, is it possible that we could just restart the business hosts that had the code change?
So this is our setup:
Ensemble 2016.1
global cache.dat
code1 cache.dat
code2 cache.dat
Namespace that we switch to point to either code1 or code2 and is mapped to the globals.