licence usage in newer editions of cache (can I release licences immediately back to the pool)

[kevin furze]

I've just jumped up to 2016.1 and have already encountered licence issues (it's the old story of csp retaining the licences for a period of time even after you have stopped using the csp pages)
licencing seems to have changed in 2012 (but I've just jumped from 2010)

I've noticed that at the top of the system portal, we have a LOGOUT option that runs
                 http://localhost:57772/csp/sys/%25CSP.Portal.Home.zen?CacheLogout=end
and as per documentation, the session (and licence usage is immediately killed)

If I then go an look at the documentation (I need to, its a new system) the system uses one more licence up, doesn't release it, and I end up running out of licences

is there any option in documentation that allows me to release the licence back to the system please

currently running "workgroup for x86-32 (Microsoft Windows):8" type of licence, so they are NOT named-users or web-users

kevin

[Dmitry Maslennikov]

Working with Licenses is a very difficult question, and depends on different types of connections, and hardest part is, how to get it good working with WEB.

Unfortunately, as web technology does not disconnections, license cannot be released after closing tab or even browser at all. You should have some timeout, and this timeout you can set as default in csp-gateway, or in your application itself. And one change in license politic was made in 2011 version you are talking about. From that version, all web connection now has client's IP address in named licenses. So, if you have guest access in your application, before 2011, version you may do $system.License.Login("guest") for all new connection before real auth, and all that connections were used 1 license unit, but now will be different identifiers such as gu...@192.168.0.10 or gu...@192.168.0.20 even the doing nothing in our system, just open login page, and in this case you will use 2 license units, after auth you can change it so do $system.OBJ.Login("john"), and some guest license identifier will change to jo...@192.168.0.10, and still use the same count of licenses, after logout, you can only change %session.AppTimeout to something quite little number, so, that time should be enought to authenticate

--
--
Caché, Ensemble, DeepSee

---
You received this message because you are subscribed to the Google Groups "Caché, Ensemble, DeepSee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to intersystems-publi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Dmitry Maslennikov

Senior Caché Developer

Skype: DAiMor

about.me/dmitry.maslennikov

[Tom Fitzgibbon]

Kevin -

As Dmitry points out licensing issues are tough because software licensing can change rapidly without apparent logic.  Do you have a "web-addon" license for your Cache which InterSystems might make available.  I've used this great license many times to allow many users (as long users are not authenticated by Cache - you supply your own auth). There are a few other restrictions. Check with InterSystems sales.

Tom Fitzgibbon | Multidata | 212-967-6700 x537

[kevin furze]

Thanks for the updates.

I've asked for a temporary upgrade to my current licen$e, just long enough to find out what the real count is that I now need
I've set the documentation csp pages down to 600, again, think that needs setting down lower, i've never needed to "logout" before, the small number of licences worked well. now it seems, I need to quickly upgrade.

I've got a call out for the sales rep to talk to me tomorrow.

will update
kev

[Gio]

I'm in a similar situation regarding licence usage on an older (2009) system ... exacerbated by the fact that it is being used as the back end for a mobile app, so there are (typically) several hundred connections being made per minute...

I found something in the Caché 2011 documentation that - at first glance - seems to provide a solution...
 
via: http://docs.intersystems.com/enscomm20152/csp/docbook/DocBook.UI.Page.cls?KEY=GCNVA_R2011_1#GCNVA_C146273
 

Licensing
 
In prior versions, license units were not consumed for CSP sessions when $USERNAME equalled "UnknownUser". Now, if the Caché license key has the Web Add-On feature enabled, it is necessary to explicitly declare the Web application public in order to avoid consuming a license key; otherwise, CSP sessions and SOAP sessions consume a license unit.
 
This can be accomplished for CSP applications by creating a subclass of the %CSP.SessionEvents class and defining a method to handle the OnStartSession event, and invoking $SYSTEM.License.PublicWebAppUser() from it.

Am I reading this correctly - would the use of OnStartSession() mean that our existing (Real Time 2012.1 Elite for x86-64 Microsoft Windows) licence would suffice (assuming the Web AddOn is present)?

Also, is there a tool that will will run on 2009 but will report what licence usage would be under 2016? The powers-that-be would need to know what licence cost to expect, should that be necessary.

Any clarification gratefully received...

[kevin furze]

i've been given a newer version of my current licence by intersystems.
it's now a "Cache 2007.1 Workgroup" licence
clearly there's a difference internally in the licence arrangements, and my licence issues have settle down.

I was running out of licences and now my usage seems to have settled down to 30-40% (back like it was before I upgraded))
It must be the way it's grouping licences under grouped users.

for now, I have my problem solved, thanks for the assistance given.

kev