When you are planning the ActiveRoles upgrade process, the main aspect that worries you most likely is risk minimization. To avoid any excesses during the upgrade, we recommend running a pilot project before rolling the new version out to the entire enterprise.
It means that you should add one more ActiveRoles service in your current environment – we call it «Pilot service». Initially the version of this service must be the same as all other services have at the moment. Subject to what your environment is – whether configuration data base is shared («Shared DB» scenario) or replicated («Replicated DB» scenario), you should add this new service as subscriber to a current replication group or just leave it as a standalone service with data base imported from the current shared data base.
On the next step you should upgrade the pilot service. But before it, in case of configuration database is replicated, you should wait until replication is complete and detach this service from the replication group. At the same time in both scenarios all changes in the current environment must be frozen otherwise these changes must be replicated manually to a new environment. One more step for the «Replicated DB» is promoting the pilot service to a publisher.
And now it's time to start the pilot project. Its main idea is to check the fundamental scenarios and new features. Notice that the previous version of ActiveRoles continues working in your production environment independently from the pilot project.
When the pilot is finished you could start the upgrade process of the rest services in your environment. If you use replication group in your environment, then detach services one by one, upgrade them and add as subscribers to the new replication group, where the pilot service is a publisher now. If you use shared database then also upgrade them one by one, redirecting to the pilot service database.
When all services are upgraded, it means that ActiveRoles upgrade process is over. Congratulations!
Don't forget to migrate management history data.
The table below briefly describes all main steps of the ActiveRoles upgrade process for both scenarios:
Configuration database is replicated
Configuration database is shared
1. Add new service as subscriber
1. Add new standalone service, using import data base option
2. When replication is completed, detach it from replication group
2. Freeze changes in current environment
3. Freeze changes in current environment
3. Upgrade new service
4. Upgrade new service
4. Start pilot
5. Promote new service to publisher
6. Start pilot
6. Start upgrade of the rest, redirect them to pilot
7. Finish pilot
7. Finish upgrade
8. Start upgrade of the rest, add them as subscribers
9. Finish upgrade