Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: mdewhurstuk@yahoo.co.uk on September 17, 2018, 09:58:38 AM
-
Hi all,
We need to copy our QA environment to Prod as we will go-live in a few weeks and i just wanted to see what are the best practices for such things.
My plan is to copy the config db and then modify the hosts & config but not sure if that the best way ??? :)>
Thanks in advance
-
Yes that should do it
Be aware of your license file and IP Addresses, some apps like RM and MCP depend on some internal parameters with IP Address
-
You can configure everything (even mcp) using dns names only.. meaning you could copy the whole environment and just use dns to make sure everything works properly in a second environment. There is also a product InProd that can let you migrate objects (and make changes) between environments
-
Even with DNS names, rarely a test environment will share the same names with a production environment. Mainly to serve it's purpose, differentiate prd from test and homologation environment.
Enviado de meu E6633 usando o Tapatalk
-
Thanks James ;)
Cloning your UAT to make production is a common thing to do on a green field site. You can change the host names in the database before starting up config server if you are using a flat network.
But going forward you will need to manage how you get changes from UAT into prod. This is what InProd was designed to do as labs are a pain to manage correctly. InProd is now a DevOps tool for Genesys Engage [url=http://www.inprod.io]www.inprod.io[/url]