Tip and Tricks... Add Your Own... :)

[tony]

Hi!

I'm placing a sticky here for me to be able to update this thread with Genesys "Tip and Tricks".

I think we all know how painful the learning curve for Genesys Solution can be, so please feel free to add your own Tips or Tricks, if you want...

TT

[tony]

[b][color=blue]CCPulse+ : How to lock-down the Application using the start-up parameters[/color][/b]

Running a command line or batch file for CCPulse+ means you can start up using a particular Host, Port, Username, Password, and a named Workspace rather than simply starting the Application.

For Batch Files, you need to set the command line first:

SET CCPULSE_ACCESS=COMMAND_LINE

On the next line add in the location/path to the CCPulse+ executable file, followed by Application "switches"

[i]<type in the full path of CCPulse here...>[/i]CallCenter.exe [b]-host[/b] [i]<hostname>[/i] [b]-port [/b] [i]<port number> [/i] [b]-user[/b] [i]<username> [/i] [b]-pwd [/b] [i]<password>[/i] [b]-app[/b] [i]<CCPulse CME application instance name>[/i] [b]-ws[/b] [i]<Workspace Name>[/i]

- this is particularly useful as the means to lock down the start up CCPulse+ on Desktops where you do not want to use the standard Genesys "login" splash screen parameters (which could be amended by Users).

NOTE: You cannot change the location of the .STG Files using this method.  You must define these locations in the Application Instance within CIM/CME.



TT

[tony]

[b][color=blue]StatServer Client and Statistic Update Limitations[/color][/b]

I think this might come in handy...?

A StatServer does not have a finite number of Statistics that it can handle - apparently, you can throw millions of requests at it and it will respond to them all... - of course, this is really dependant on the specification of your hardware and how much memory is available...   As a rule of thumb, you can consider the following, based on update requests (from CCPulse+, etc.)

For 1000 statistics with a time profile of 10800 (24 hours) and all of them with a notification frequency of 2 seconds on a 64 bit OS, the amount of memory used will be:

1000 * 64 * 10800/2 = 345.6Mb ~ .3 Gb

There is also (apparently) a finite number of Clients that can connect to a StatServer, too - 1016. This means the number of Message Servers, Config Server, TServers, Clients (CCPulse+), etc. connecting in Real Time cannot exceed 1016.  This might not seem like a problem until you come across a number of CCPulse+ Clients that have either locked out or have not been shut down gracefully.  These "ghost" Clients remain connected and they will not disconnect until you restart your StatServer...  Very soon you find that new Clients cannot connect, since there are more than 1016 Clients...  Depending on your OS, there are various ways to check the number of Clients connected to a particular StatServer - I'm not going to list them but, if you are troubleshooting, this is a good place to start if your StatServer is refusing connections...

TT

[Tambo]

Hi Tony,

Perfect this may solve an ongoing issue we have !!! where can I find how many clients are connected as almost daily we are having this "cannot connect" problem

Tambo

[tony]

Hi Tambo - what OS is your StatServer on..?

[Grum]

[color=blue]ETL: Error with transfering statistic (Dublicated column names)[/color]

It is one of the most Genesys tip&tricks, so-called "pitfall".
Start at the begginer...
When you modelling you data model for your statistic in Data Modelling Assistent you should know one thing
!!!you must not create the NEW statistic with the name has already ONCE EXISTED!!!
1)For example, you have a statistic named M_TALK_TIME from statistical type MaxInTalkTime in some Layout Teamplate and resp., in Report Layout.
2)You desire to create a NEW statistic like already existed M_TALK_TIME but, for example, with some filter.
WRONG STEPS:
3)You delete your statistic M_TALK_TIME and create a new one with filter and with the SAME name "M_TALK_TIME"
In this case statistic information collected from your statistical types will stop transfering to historical DB.
RIGHT STEPS:
3)You should create a new statistic WITHOUT deleting old stat. with a name "M_TALK_TIME_FILTER".
You can create a new statistic also with deleting M_TALK_TIME but in future you can foget it. So I adviсe you NOT TO delete older statistic ANYTIME and create a new one just with other name.

So, what you should do:
1) Simplest solving - find out, what layout was activated at the day when statistic was stopped transfering, delete it and then create a new one with UNIQUE names of statistic types. Or just delete only one or several problem statistic and create them with a UNIQUE names too.
2) Sophisticated solving - if the first solving will not help you, then you should enter you DB manually, watch and delete statistic with DUPLICATED column names. Also you can find a special script for deleting DUPLICATED column names on Genesys support but I don't advice to use it. It will be better to do it yourself manually.

previously sorry for my English.

Hope it will help you.

Regards,
Grum