No need for license file?

[Victor]

Reading through the previous post, I noticed that you can get away without placing license.dat file on every machine you have Genesys product running on.

I ran few simple tests in our lab, and it seems like most of the products (5.1.x) support 7260@hostname value for licensefile option. Just to be on a safe side, can someone please confirm it?

By the way, it seems like IR does not like licensefile option, does it? Instead you have to use l from a command prompt... I tried 7260@hostname and ... it worked!

Vic

[Jason]

In my setup we only have one location for the license file. On all the other servers that make up our Genesys install (tserver, configserver, cm, etc) that require the license file we just map the drive and point the portion of the batch file to the mapped drive.

[Vic]

Jason,

I ran few additional tests for Call Concentrator, IR, Stat Server, and TServer and in all cases 7260@hostname worked. For IR, and statserver licensefile option did not work, but l 7260@hostname was fine.

I am currently starting to redesign most of our multisite call centers to take advantage of this wonderful, but yet commonly overlooked feature.

I have checked TServer 5.1.070, IR Server 5.1.521.03, Stat Server 5.1.075, and CCon 5.1.042(?) for UNIX and all of them worked. I would not want to go back to license.dat, unless it is a multi enant environment which would require limiting each tenant to what they can access. I will try to post a report about it later on this week.

Cheers,
Vic

[eva]

Hi Vic,

yes it´s true that you can use thie option.
In all genesys rainigs this option is teached!

Eva



#####

[Dan]

I can understand how you might want to reduce your effort and have only one license file location, but have you thought about what this means. Anything affecting the server with the license file and license manager will cause you to lose all licensed Genesys servers. I changed to have a license file and a copy of license manager on each server. This way you can keep some processes running and avoid having all your agents down. Of course, this also depends on how you have setup for backup processes, etc. You can customize each license file to have entries for just the processes on that particular server. Something to think about....

[gauthier]

The best thing you can do to setup a redundant license manager configuration is to put flexlm under a cluster environment. Otherwise there are multiple other ways to configure redudnacy that are explained in detail on the website of Globetrotter software. They are the vendors of FLEXlm.

[Vic]

Ok, here is what I know from our own tests:

in G6.1 if license manager goes does, TServer is not affected. All other products will be affected within 180 seconds or so.

if URS goes down because of a license failure and your try to restart it with LCA, SCS (6.1.012) will be confused and will show URS is starting even though it is still down. You will need to restart LCA on URS machine to get the right status for URS.

redundancy can be implemented in two ways: via threeserver backup redundancy plan where you have three license managers running on three different machines which are sharing the same license file (yes, you can do it and it is supported) or you can just have a normalk redundancy by using ":" option as in 7260@server_a:7260@server_b. All products will automatically switch to backup license server if original one is down, so it would really simplify your environment when you have myriad of servers each using its own license manager/file in order to avoid problems due to network congestion.

For further info, just search this forum for redundancy (make sure the "LAst" option is set for one year or more when you search )))