" /> Solution in CME - Genesys CTI User Forum

Author Topic: Solution in CME  (Read 8590 times)

Tony

  • Guest
Solution in CME
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Anyone using Solution in CME to start and stop applications in order in SCI? If so do you have documentation on the proper startup/shutdown order?


Mikael Jansson

  • Guest
Solution in CME
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Hi !
    We are using Solution to stop and start Workforce Manager.
    Is there a special solution your looking for or just any ?
    WFM Start order:
    1: StatServer
    2: ScheduleServer
    3: DataAggregator

    Regards
    Mikael Jansson

    Superglide

    • Guest
    Solution in CME
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • I would be interested to see how others stop and start an Enterprise Routing solution:
    CCPulse
    URS
    GIS
    Custom Server
    etc

    Graeme

    ecki

    • Guest
    Solution in CME
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • The most interesting is start of CCPulse with SCI ;0)

    Superglide

    • Guest
    Solution in CME
    « Reply #4 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Perhaps I should turn my brain on before I comment next time...
    ;)

    Vic

    • Guest
    Solution in CME
    « Reply #5 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • It is scary but it took me a while to realize it! Superlglide ice going! :)

    (skipping backups)

    cfg_dbserver
    confserv
    LogDBServer
    MessageServer
    SCS <-heck, maybe I am doing it from backup)
    TServer
    Stat Server
    URS
    and of course...
    CCPulse :)

    Superglide

    • Guest
    Solution in CME
    « Reply #6 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • See I was right... Even Vic uses SCI to manage CCPulse... :()

    But back to the thread... The operational team here are a bit dubious about the "one click stops all" approach, particulairly with the SQL cluster in the background, which can add complexity to it all (mainly because they are not DBAs). Does anyone actually stop and start a solution such as Vics example using SCI or do they manually do it as our Ops team do (they found a way that works, but is really dependant upon them to come into work and do etc..)

    Graeme

    ecki

    • Guest
    Solution in CME
    « Reply #7 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • We always manage it through cluster management system or if there isn't cluster then with windoze service or unix autostart scripts after boot. For that is the start through solutions not realy usefull for us.
    It's realy pity that the genesys management solution doesn't have auto start function (not autorestart). Or has anybody other expriences?

    AR

    • Guest
    Solution in CME
    « Reply #8 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Latest 7.01 SCS server supports auto start .

    Check the release notes!

    Al

    • Guest
    Solution in CME
    « Reply #9 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • TONY:
    I am not sure how the formating will look, but here is how our SCI solutions for a (3) site system. I am not sure I totally agree with the configuration, but this how our vendor set it up and we are living with it.

    Reporting
    Name Status Mode Startup Type Host
    dbserver_log Started PRIMARY 1 DB Server WFM Server
    dbserver_ers Started PRIMARY 1 DB Server CCA Server
    ETL_Service Started PRIMARY 3 CCAnalyzer Data Mart CCA Server

    CCA_DataSourcer Started PRIMARY 4 CC Analyzer
    Data Sourcer CCA Server
    dbserver_cca Started PRIMARY 1 DB Server CCA Server
    statserver_ccpulse Started PRIMARY 4 Stat Server WEB Server
    statserver_global Started PRIMARY 4 Stat Server Tacoma CTI

    Workforce Management
    msgserver_global Started PRIMARY 1 Message Server WFM Server
    wfm_da651
    Started PRIMARY 3 WFM Data
    Aggregator WFM2 Server
    wfm_ss651 Started PRIMARY 2 WFM Schedule Server WFM2 Server
    statserver_wfm Started PRIMARY 1 Stat Server WFM2 Server

    Seattle
    dbserver_log Started PRIMARY 1 DB Server WFM Server
    statserver_sea Started PRIMARY 4 Stat Server Seattle CTI
    statserver_seaR Started PRIMARY 4 Stat Server Seattle CTI
    dbserver_ers Started PRIMARY 3 DB Server CCA Server
    tserver_seattle_s Started PRIMARY 1 TServer Seattle CTI
    ivri_seattle Started PRIMARY 2 IVR Interface Server Seattle CTI
    urs_seattle Started PRIMARY 4 Universal Routing Server Seattle CTI
    msgserver_global Started PRIMARY 1 Message Server WFM Server
    msgserver_sea Started PRIMARY 1 Message Server Seattle CTI

    Tacoma
    dbserver_log Started PRIMARY 1 DB Server WFM Server
    statserver_tac Started PRIMARY 4 Stat Server Tacoma CTI
    statserver_tacR Started PRIMARY 4 Stat Server Tacoma CTI
    dbserver_ers Started PRIMARY 3 DB Server CCA Server
    tserver_tacoma_s Started PRIMARY 1 TServer Tacoma CTI
    ivri_tacoma Started PRIMARY 2 IVR Interface Server Tacoma CTI
    urs_tacoma Started PRIMARY 4 Universal Routing Server Tacoma CTI
    msgserver_global Started PRIMARY 1 Message Server WFM Server
    msgserver_tac Started PRIMARY 1 Message Server Tacoma CTI

    Spokane
    dbserver_log Started PRIMARY 1 DB Server WFM Server
    statserver_spo Started PRIMARY 4 Stat Server Spokane CTI
    statserver_spoR Started PRIMARY 4 Stat Server Spokane CTI
    dbserver_ers Started PRIMARY 3 DB Server CCA Server
    tserver_spokane_s Started PRIMARY 1 TServer Spokane CTI
    ivri_spokane Started PRIMARY 2 IVR Interface Server Spokane CTI
    urs_spokane Started PRIMARY 4 Universal Routing Server Spokane CTI
    msgserver_global Started PRIMARY 1 Message Server WFM Server
    msgserver_spo Started PRIMARY 1 Message Server Spokane CTI

    Matt Haynie

    • Guest
    Solution in CME
    « Reply #10 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • We use a batch file in combination with PS Tools a free program. This allows us to start each service in order by executing a batch file. I had our programmer write a nifty little script that will also make sure the service has started before going on to the next.

    It is really nice for us since we have about 20 services to start. It works for restarting the whole suite as well.