Hi @arnold_bijlsma
Can the LicenseChecker transformer be used?
I've been thinking about something like that as well, but the downside of @sigtill's suggestion is that you need to run FME (and check out a license) in order to run the LicenseChecker, which would skew the results.
FlexLM comes with some command line tools, including one to show the license status (lmtools lmstat, see this page). If you set up a scheduled task in Windows to run that at a regular interval and output (append) the results to a text file you can then at a later stage process that with FME and produce a report.
Digging deep into my MS Dos memory, adding this to the end of the command line should do the trick:
>> floatinglicense.log
So the full command line would be
lmtools lmstat -a -c &license file] >> floatinglicense.log
But note I don't have a floating license setup here that I can test it with...
I've been thinking about something like that as well, but the downside of @sigtill's suggestion is that you need to run FME (and check out a license) in order to run the LicenseChecker, which would skew the results.
FlexLM comes with some command line tools, including one to show the license status (lmtools lmstat, see this page). If you set up a scheduled task in Windows to run that at a regular interval and output (append) the results to a text file you can then at a later stage process that with FME and produce a report.
Digging deep into my MS Dos memory, adding this to the end of the command line should do the trick:
>> floatinglicense.log
So the full command line would be
lmtools lmstat -a -c &license file] >> floatinglicense.log
But note I don't have a floating license setup here that I can test it with...
That's what I have done so far, and is described in my second option. I got the lmtools command running, creating a time-stamped logfile, saved it as a batch file, and then set up a Windows Task Schedule to run it every 15 minutes after login.
Apart from some Windows issue with the Task Scheduler, it does kind of work. However, it only runs when I am logged in (i.e. Tue-Fri 9am-5pm). And IT is not happy me moving that batch file that runs every 15 minutes to a corporate server.
And it still feels very much like a Blue Peter solution (houtje-touwtje oplossing). Given that our ArcGIS license server used to work on lmtools as well, I would hope someone has something a bit more elegant (he said with his fingers crossed...) than fiddling about with 90s DOS commands ;-)
That's what I have done so far, and is described in my second option. I got the lmtools command running, creating a time-stamped logfile, saved it as a batch file, and then set up a Windows Task Schedule to run it every 15 minutes after login.
Apart from some Windows issue with the Task Scheduler, it does kind of work. However, it only runs when I am logged in (i.e. Tue-Fri 9am-5pm). And IT is not happy me moving that batch file that runs every 15 minutes to a corporate server.
And it still feels very much like a Blue Peter solution (houtje-touwtje oplossing). Given that our ArcGIS license server used to work on lmtools as well, I would hope someone has something a bit more elegant (he said with his fingers crossed...) than fiddling about with 90s DOS commands ;-)
90s DOS commands for the win!! (My first computer had MS-DOS 3.21, on 5.25" floppy disks)
But yeah, it is a bit of a Blue Peter / houtje-touwtje solution. I've done a bit of googling and found some hits here but there's no telling whether or not those solutions do exactly the same thing but wrapped in a shiny interface and whether or not your IT department is going to like it. OpenLM does seem to have an ArcGIS-specific version though, so that might come in useful.
