It should be possible to deploy a Integrity Setup via Staging mechanism to more than one server, for example to a second productive server of another productline or simple a Trainings or Playground Server.
Very good requirement: The following should also be considered here: In some companies (like us) it is not allowed to permanently connect servers of different stages to each other. And it is also not allowed to have the same data on different stages. This means that no user accounts and user data from a productive system may be stored on a development server and therefore, for example, the user administration including all permissions must be separated from staging.
This idea is one of our open use cases since years as well. We would like to keep our training and development servers synchronized with a master server.
As of today we need to apply changes manually to all our independent development / training servers. That is causing a lot of extra work. And because of that in most cases our playgrounds are out of sync.
Copying the native SQL DBs would be an option but then we would destroy all available server specific configuration (e.g. groups, ACLs, etc.) while we were just interested in an update of a data type. So cloning SQL DBs might work for some scenarios but is no option to bring approved changes to our staging systems.
So we thought more of a script based concept to get rid of this repetitive manual configuration on multiple servers. So we have to do changes only once and then we apply them via a script throughout our Integrity training and development servers.
Hence we searched for such a solution and found it with PTC platinum partner Nanga Systems.
They develop a separate Integrity deployment tool that can export an existing Integrity solution or parts of it without the requirement of a locked staging link. These exports can be imported / applied to other Integrity servers in parts or completely.
We are still in an early conception phase but it looks very promising. So we intend to use this approach for synchronizing development environments before we deploy tested changes also to our final regular staging / production environment. Also our training servers shall be updated by this on regular basis.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.