Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: abudwill on September 09, 2015, 08:41:42 PM
-
Hi Guys,
Looking for input on how you best accomplish migrating data from one config server to another. Or alternatively if there is a Genesys tool available to do this that I am simply not aware of.
My scenario is that I have a production Genesys environment. I would like to extract certain objects from it (mainly items that make up some outbound campaigns such as skills, users, fields, formats, table access objects, treatments, calling lists, campaigns, campaign groups, virtual agent groups) and import those objects into a different Genesys environment (my development environment) so that I can move forward doing proper development NOT on a production system.
Am I nuts? Is this best accomplished by hand through CME or GA?
Am I looking at examining the database schema and exporting/importing SQL?
Is there a tool that will do this for me?
Regards,
Andrew
-
No tool. You can copy whole db maybe but will have to change names and lot of stuff. Better install from scratch and configure objects. You will know exactly what you are doing and not scratching the head after when you have no clue what went wrong
Enviado de meu C6602 usando Tapatalk
-
Ugh I was afraid of this.
In my case this is a huge effort because each campaign has something like 40 calling lists attached. Each with a unique filter and treatments. Multiply that by 30ish campaigns and you are keeping yourself busy for a couple days point and clicking in CME or GA.
Thanks for the response.
I will look into using PSDK to export/serialize config objects (and their dependencies) along with a way to import them. If I ever get around to making this I will post it here so everyone can benefit.
Regards,
Andrew
-
There are third party apps that may help
Sent from my SM-N9005 using Tapatalk
-
Like which one?
Enviado de meu C6602 usando Tapatalk
-
Looks like a company named "eemaan" makes one. Based on their site, it also looks expensive (since no price is listed).
-
It is owned by my friends cousin lol
Never saw them in deep. Contact them and will give you more details
Enviado de meu C6602 usando Tapatalk
-
Small world!
-
Don't remember the cost but I arranged to purchase the eemaan import/export apps (and their audit trail app). Worked quite well as I recall - this was about a year ago. I'd ask them for a demo/trial.
Sent from my SM-N9005 using Tapatalk
-
Hopefully I can finish putting together some code to post soon. I wanted to let everyone know I figured out how to accomplish this for my purposes.
Lets talk .Net for now, Java would be nearly the same.
From PSDK perspective, all config objects seem to have an implementation for ToXml() method. This method expresses the config object in... XML. I have been able to create a chooser GUI that will allow me to choose objects I want to migrate. I call ToXml() on all the objects I select, write the XML to disk.
I can take the file I wrote to disk and move it to a different Genesys deployment, then use my GUI to import the XML.
The IConfService class has a method, CreateObjectFromXml(), this method can be utilized to reconstruct the config object from XML on a different Genesys deployment.
The XML includes things like DBID, but when consuming CreateObjectFromXml and passing an objects XML, the new config server assigns a new DBID, cool. Haven't done this on objects that have options/annex values yet, so not sure if those would carry over. Will have to play with that soon.
I was able to migrate 125 skills from a prod to dev environment in about 10 seconds rather than have to type them all in by hand, yeah!
Regards,
Andrew
-
Nice job, congrats
Enviado de meu C6603 usando Tapatalk
-
Just added support for agent groups. Migrated over 100 in seconds!
-
Complexity will be when you get to object dependencies and need to link by DBIDs etc. Similar fun with PSDK here:
http://genesysguru.com/blog/blog/2009/10/03/configuration-snapshots/
Regards
-
Excellent idea re configuration auditing there on your blog. I wouldn't suppose your tool is available?
And I agree regarding the linking DBIDs. I already ran into the need to scrub some linking DBIDs from the agent groups that I exported/imported - otherwise the import fails because the linking DBIDs don't exist on the target deployment I am importing at.