We are trying to come up with a procedure for migration.
We have 4 standalone gateways staging and prod environments that must maintain same state.
1 in dev and 1 test.
1. We want to migrate policy that is using Siteminder. A Siteminder configuration already exists in destination gateway.Because all policies in the folder are leveraging Siteminder we get the following for each policy
error attempting to save or update the PublishedService with id='ff3749237faaeeed4972374'. Constraint Violation: could not insert collection:[com.l7tech.gateway.common.siteminder.SiteMinderConfiguration.properties#ff4vcgdjs647923784faaaeeejdvdj]
We cant not migrate the siteminder part because we are using an siteminder authentication policy fragment in each policy.
2. What is the best way to prevent having to manually update the siteminder settings at policy level i.e settings when using Check protected Resource against Siteminder Assertion. config name, agent, server name, aco.
Should we save all these as cluster properties or possibly have to make the changes in a template?
3. We will be relying heavily on GMU our policy sdlc and maintaining same status between gateways in same environment as well as between staging, and Prod. Any additional GMU pointers , best practices we should know?