" /> Migrtation from QA to Prod - Genesys CTI User Forum

Author Topic: Migrtation from QA to Prod  (Read 1965 times)

Offline mdewhurstuk@yahoo.co.uk

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Migrtation from QA to Prod
« on: September 17, 2018, 09:58:38 AM »
Advertisement
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

Marked as best answer by mdewhurstuk@yahoo.co.uk on September 18, 2018, 06:33:32 PM

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Migrtation from QA to Prod
« Reply #1 on: September 17, 2018, 02:21:39 PM »
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

Offline jamesmurphyau

  • Full Member
  • ***
  • Posts: 123
  • Karma: 2
Re: Migrtation from QA to Prod
« Reply #2 on: September 18, 2018, 07:42:59 AM »
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

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Migrtation from QA to Prod
« Reply #3 on: October 01, 2018, 06:39:06 PM »
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


Offline jarrod

  • Newbie
  • *
  • Posts: 42
  • Karma: 1
    • InProd CMS
Re: Migrtation from QA to Prod
« Reply #4 on: October 08, 2018, 11:46:56 AM »
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]