" /> Exporting data - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: Exporting data  (Read 9606 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Drew

  • Guest
Exporting data
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hello all... I'm looking for a way to export my CME data from my test environment and load it on the Production box.
Logged

Victor

  • Guest
Exporting data
« Reply #1 on: January 01, 1970, 12:00:00 AM »
Well, there are several way of doing it. If you have the same database type (SQL, Oracle, etc) then a simple export, import script will do just fine.

But, if you are doing it crossplatform, then you will need to use CME Export and CME Import. CME Export comes with Framework CD. Of course, needless to say, Genesys does not support it, so you are on your own.

What platform is it?
Logged

Drew

  • Guest
Exporting data
« Reply #2 on: January 01, 1970, 12:00:00 AM »
Hi Victor,

we're running on Informix... would you happen to have the db schema?
Logged
Marked as best answer by on May 05, 2025, 03:08:44 AM

Betty Davidson

  • Guest
Exporting data
« Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
    • I have it too! Should I post it to the forum?
    Logged

    Matthew Harttree

    • Guest
    Exporting data
    « Reply #4 on: January 01, 1970, 12:00:00 AM »
    If it is Oracle ... Use Toad http://www.quest.com ... Speak with Tudor McGrann.

    With Toad you can create DBA Scripts from live Data. Edit the data and then run the scripts against a new database. This is not a supported procedure from Genesys ... but it works rather well.


    mth

    --
    my views ... not Genesys
    Logged

    Victor

    • Guest
    Exporting data
    « Reply #5 on: January 01, 1970, 12:00:00 AM »
    Matthew,

    I don't quite understand. You mean use Toad to export and import data? If this is the case, then I must agree with Betty that that CME Import/Export tool is simply wonderful.
    How do you usually use Toad?
    Logged

    Matthew Harttree

    • Guest
    Exporting data
    « Reply #6 on: January 01, 1970, 12:00:00 AM »
    I have to state this once again: I am offering my opinion only.

    When Genesys designed the IMP/EXP lib and the the tools the goal was for support to have access to the cme data at a customer site to see if there were any config errors (usually one of the "dirty dozen" errors that customers have trouble with). As I understand it, the import tool was released into the "wild" and now is used as the de facto standard for moving test data to production.... I dont think the tool was designed for this purpose and I dont believe we support its use directly ... I dont see it listed as a customer tool. Blindly moving data from test to prod is one of the most dangerous things you can do.

    I know that it is a pain to manually recreate things from start. When you complete a Genesys test ... spirits are running high and departments and endcustomers want to get running as soon as possible.

    At this nexus... This very shining moment is where all hell breaks loose.

    Why? Most likely the test numbering schemas and IP addresses are different and things are configured for a test environment. In a fleeting moment, somehwere somehow somone forgets something that was done three months ago (or much less... I have seen 1000 seat call centers go live in a month with Genesys) as an experiement.

    Usually, the data is carted over en masse to another database and
    then booted up to see "what happens".


    Using a tool like TOAD for oracle or SQLWalk for MS (I have heard of this but dont have it - I deal strictly with Oracle) alllows someone to read the data that is coming out of your database and review it, make changes and most importantly understand the data that is about to be moved over. Do you see an IP address that is duplicated in production? Do you see a username that is wrong? What about the Agent login ID or email addresses ... do they need to be changed?

    Having a flat file script that creates the data (complete script included) allows you to review the whole structure and make *seperate* notataions regarding what needs to be changed and if possible the information that could be replaced in the file before you import it. Depending on the data... search and replace could be used.

    In an emergency the TOAD DBA module or comparable product gives you a complete script to create a config database from scratch. The Genesys product was never intended to do that. Support has 50 to 60 databases with automation tools available to them that allow any support engineer the ability to review a submitted customer config and search for errors. For end users, consistent backups and DBA involvement are the key. Our import tools, currently dont do a lot of sanity checks... This is the responsibility of the person doing the importing.

    I have seen several times, a customer/var/consultant copy the data from a test database to prod ... boot the environment without making any changes and wonder why the system doesnt work.

    In some deployments the DBA is involved at the last minute or there is no DBA to speak of. Take a few minutes each week and relate to the DBA what your group is doing ... what processes are going on. DBAs are a curious folk who might like to know more about CTI/CRM and your project.



    6.1 (something you should really consider using) has many more import and export features. As XML and other technologies take hold, I would guess that Genesys would consider using these tools and technologies to offer ways to migrate data... If you have a big project that requires en mass movement of data from test to prod... I would suggest you approach your Genesys contact and ask them to contact appropriate folks in product management. As A side note... If your call center has over 300 agents or is multi site... Start thinking about LDAP.



    Hope this helps and does not sound to preachy... Just hoping that your implementation goes well and avoids pit falls.

    Regards,


    /mth/

    Matthew Harttree
    Principal Engineer
    Genesys
    mth@genesyslab.com
    Logged

    Ed

    • Guest
    Exporting data
    « Reply #7 on: January 01, 1970, 12:00:00 AM »
    Bottom line is to have DBA's involved with imports/exports. One thing to be sure of is to keep CME data seperate from Reporting etc. The CME export/import tool probably will not be supported by Genesys because they provide CTI solution and not DBA support. If you keep the data seperate you should have minimal issues. I do understand it is usually time consuming to get DBA support and some shops have a team that handles databases at the programming level. Hope this helps. As you can see there are a lot of good answers. Hope this helps
    Logged
    Pages: [1]   Go Up
    « previous next »