Hi Misi, I have seen your presentation and it is way too useful, thank you ....
2012/1/5 Misi Mladoniczky <m...@rrr.se> > Hi, > > A couple of small notes... > > The write license is not grabbed when you login. It is grabbed when you do > a search, update a table-field, or something else that access the server > concerning data. You can open a form without grabbing your licenses, as > long as there is no workflow that connects to the server for data. > > Application licenses work in a similar way to AR licenses. The difference > is that users are not assigned floating read licenses from the start, this > only happens when they access data. Forms are tagged to the application > they belong to, and the licenses tokens are grabbed when you access data > in application-tagged forms. > > You can get some more details in a RUG-presentation I did some time ago: > http://rrr.se/doc/RRR_LicenseManagement.pdf > > Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) > > Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > Find these products, and many free tools and utilities, at http://rrr.se. > > > It has taken us years to completely understand the floating license > > timeout. > > > > It may be best to not think in the terms of a single user but think of a > > floating write license pool. My description below is for the server > > floating write licenses. > > > > User B logs into the server. Is the number of users with floating write > > licenses less than the number of available floating write licenses? > > If the answer is yes then they are allocated a floating write > license. > > If the answer is no then they are given a Read license. They can > > execute searches and under certain conditions they can update records > > (Submitter Mode locked and they are the Submitter for one). > > > > With a Read license User B can run reports, looks at records, anything > > that doesn't trigger a modification of a record. If they log off they > > don't need to be assigned a floating write license. > > > > Now lets say 5 minutes pass and User B modifies a record. The server > > checks to see if there is a floating write license available from the > > pool. If there is then User B is given a floating write license. > > > > Now the question becomes what makes the floating write license available. > > One way is User A is assigned a floating write license and User A logs > off > > the server. Their license is now available in the pool. > > Another way is User A is assigned a floating write license and they went > > to a meeting. They were not doing anything within the client for 65 > > minutes. If User B made their modification after User A has been > inactive > > for 60 minutes, the system will give User B the floating write license > and > > User A will be given a Read license. > > I'm not familiar with the application licenses but I would assume the > > logic is similar. > > > > Dave > > ________________________________ > > From: Action Request System discussion list(ARSList) > > [mailto:arslist@ARSLIST.ORG] On Behalf Of Mauricio M. > > Sent: Wednesday, January 04, 2012 3:42 PM > > To: arslist@ARSLIST.ORG > > Subject: Re: Floating License Timeout - myths and facts > > > > ** Dave, > > > > With that in mind, actually there is no "license timeout" functionality > as > > we all understand, is that right? if user is inactive for the timeout > > interval, I would expect him to be flushed and not only get reverted to > > read-floating. > > > >>From what you say, if you set a 1 hour timeout, if the user is inactive > >> but returns to his session at the last moment, say 59m:59s and he has > >> activity he could potentionally grab the token again and other users > >> waiting "in line" will never get the token and have write access for > long > >> time.... > > > > This is odd, is this supposed to work this way? if users are not really > > flushed after timeout, how is this controlled? > > > > What you say about users could also get reverted to floating-write after > > timeout, is also odd, since there would not be a real timeout > funcionality > > at all. > > > > -Mauricio > > > > > > 2012/1/4 Shellman, David > > <dave.shell...@te.com<mailto:dave.shell...@te.com>>: > >> The user is not kicked out of the system. > >> > >> The will continue to show in the list of Users. Whether they are given > >> a read license or continue to have a floating license depends on if the > >> number of users associated with floating licenses is less than the > >> number of floating licenses. > >> > >> It's also dependent on if they have executed a search or a function that > >> acts like a search. This resets the license time out clock. > >> > >> Dave > >> > >> -----Original Message----- > >> From: Action Request System discussion list(ARSList) > >> [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of > >> Mauricio M. > >> Sent: Wednesday, January 04, 2012 2:01 PM > >> To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > >> Subject: Floating License Timeout - myths and facts > >> > >> Hello everyone, > >> > >> Just bringing back the old question about how license timeout is > >> supposed to work > >> > >> Which is the expected behaviour if user logged in and he had been > >> granted with floating write license and now he is timed out due to > >> session inactivity > >> > >> I mean, if the timeout interval expires, > >> > >> 1) User should dissapear and not get listed at all in "Manage User > >> Licenses" -> Server - Current Licenses?? > >> > >> or > >> > >> 2) User should remain listed in "Manage User Licenses" but now being > >> reverted to Read (Floating)? Is normal behaviour that user is not > >> actually kicked-out of the system although he got license timeout?? > >> > >> Hope someone can clarify this, thank you!! > >> > >> Regards, > >> > >> Happy 2012 > >> > >> -Maw > >> > >> > _______________________________________________________________________________ > >> UNSUBSCRIBE or access ARSlist Archives at > >> www.arslist.org<http://www.arslist.org> attend wwrug12 > >> www.wwrug12.com<http://www.wwrug12.com> ARSList: "Where the Answers > Are" > >> > >> > _______________________________________________________________________________ > >> UNSUBSCRIBE or access ARSlist Archives at > >> www.arslist.org<http://www.arslist.org> > >> attend wwrug12 www.wwrug12.com<http://www.wwrug12.com> ARSList: "Where > >> the Answers Are" > > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
