Hi folks,
we encountered a mismatch of our configuration in UAT and PROD. I think a common issue in any IT environment.
Do you have any advice on how to keep the configuration in sync? Do you have a check list of filters, templates, methods, macros etc. which is kind of automatically checked? I think it is not easy as both instances cannot be triggered by a central report, right?
Any ideas welcome...
Cheers
Peter
Hi Peter,
IMHO
If you use two configurations (tenants), then there is not much to do. ARIS gives a manual way to backup all those elements (DBs, filters, reports, etc.) one by one (which is pure hell) or, as I believe you are aware, the ability to backup the whole tenant, including DBs, reports, configuration, etc. But there is another issue — when you back up the entire tenant, its restoration at another configuration will affect your critical components, first of all, DBs and users.
So, my usual strategy is to separate DEV/PROD only on the logical level. This means we use one configuration (one tenant or multi-node), separating access to different DBs and all required components. Then, you don't have the issue you've raised; the only benefits are simpler merge, simpler provide access, simpler backup/restore, and simpler configure. There are no minuses in this approach, especially if you use (as I believe your Bank does) a multi-node setup.
So I would simplify life, and switch from two different configurations into one.
Hi Peter,
IMHO
If you use two configurations (tenants), then there is not much to do. ARIS gives a manual way to backup all those elements (DBs, filters, reports, etc.) one by one (which is pure hell) or, as I believe you are aware, the ability to backup the whole tenant, including DBs, reports, configuration, etc. But there is another issue — when you back up the entire tenant, its restoration at another configuration will affect your critical components, first of all, DBs and users.
So, my usual strategy is to separate DEV/PROD only on the logical level. This means we use one configuration (one tenant or multi-node), separating access to different DBs and all required components. Then, you don't have the issue you've raised; the only benefits are simpler merge, simpler provide access, simpler backup/restore, and simpler configure. There are no minuses in this approach, especially if you use (as I believe your Bank does) a multi-node setup.
So I would simplify life, and switch from two different configurations into one.