Hi again,

Just some extra info concerning application licenses, and more
specifically ITSM7-licenses. Application licenses in earlier versions was
not counted by the system...

The application licenses are allocated with the same principle as ordinary
licenses. The difference is that licenses are grabbed only when you access
data (read or write) in the specific forms tagged for that specific
application (for example Incident Management).

        Best Regards - Misi, RRR AB, http://rrr.se

> Hi,
>
> There is a lot of misunderstanding about how licenses are allocated.
>
> The floating license is "grabbed" as soon as the user, directly or
> indirectly, searches/submits/modifies to any form. This can be an
> active-link-set-fields or a table refresh.
>
> The license is held until the user logs out or a minimum of 1 hour
> depending on the server setting. This applies to Mid-Tier as well. The
> 15-minute timeout in Mid-Tier is something else.
>
> I have written down some details about this in a presentation I have done
> at various local RUGs: http://www.rrr.se/doc/RRR_LicenseManagement.pdf
>
> We have a tool called RRR|License where you can actually see how your
> proposed license allocation would work.
>
> There is a limited demo-version of RRR|License that you can access at
> https://www.rrr.se/cgi/rrrlic/rrrlic?i=1
>
> All you need is a user-log from your server.
>
> Let me know if you need help or suggestions with your analysis.
>
>         Best Regards - Misi, RRR AB, http://www.rrr.se
>
> Products from RRR Scandinavia:
> * RRR|License - Not enough Remedy licenses? Save money by optimizing.
> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
> * RRR|Translator - Manage and automate your language translations.
> Find these products, and many free tools and utilities, at http://rrr.se.
>
> 1> Agreed:
>> Gary said: I just do not think that a float license should be assigned
>> until such case that
>> one is needed; it messes up how many licenses are actually needing to be
>> used at one time.
>>
>> I am pretty sure the default behavior changed in approx 6.0 -- it used
>> to be the case that you did not get a float until needed.
>>
>> I can see why the default changed -- however -- it seems as if it
>> should be a parameter set at the server level. Either the whole system
>> uses "aggressive float license/not"
>>
>>
>>
>> -John
>>
>>
>>
>>
>> --
>> John David Sundberg
>> 235 East 6th Street, Suite 400B
>> St. Paul, MN 55101
>> (651) 556-0930-work
>> (651) 247-6766-cell
>> (651) 695-8577-fax
>> john.sundb...@kineticdata.com
>>
>> On Dec 17, 2008, at 7:48 AM, Opela, Gary L CTR USAF AFMC 72 CS/SCBAH
>> wrote:
>>
>> Dave, thanks for responding. I understand how licenses work, I just do
>> not think that a float license should be assigned until such case that
>> one is needed; it messes up how many licenses are actually needing to be
>> used at one time.
>>
>>> As defined, "When a search, modify, or submit is performed, AR System
>> checks for an available Floating Write license token.
>>
>> Why should it? A write license is not required at this point
>> unless/until a modify of another person's ticket is occurring, with
>> submitter mode locked. If it is consuming a license prior to this point,
>> basically any time the user uses the system, then I'm using more
>> licenses than I should be. That means that if I have 100 users that
>> might modify 5 other people's tickets per month, but 200 of their own,
>> then I most likely will be running out of licenses every day.
>>
>> I should be able to have 25 licenses for 100 users if they each only
>> modify five tickets per month, because they each only require a write
>> license for those five modifications.
>>
>> I wrote filters that track the different submit/mod own/mod other each
>> time someone performs one, and it increments a counter in another table
>> so that I know exactly how many licenses I need.
>>
>> We currently have everyone on fixed licenses, but I think that is a
>> waste.
>>
>> Thanks,
>>
>> Gary Opela, Jr.
>>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList)
>> [mailto:arsl...@arslist.org] On Behalf Of Easter, David
>> Sent: Tuesday, December 16, 2008 7:15 PM
>> To: arslist@ARSLIST.ORG
>> Subject: Re: floating licenses
>>
>> **
>>> In the mid-tier, it's 15 minutes
>>
>> The floating license time-out on the Mid-tier can be no less than one
>> hour currently.
>>
>>> Basically, if the user is just submitting, modifying their own, and
>> querying, will remedy go ahead and assign a ticket[sic]?
>>
>> As defined, "When a search, modify, or submit is performed, AR System
>> checks for an available Floating Write license token. If a token is
>> available, the user is granted write access to requests. If no tokens
>> are available, the user is notified and continues to use the Read
>> license until a token becomes available."  (Concepts Guide - AR System
>> 7.1.00 - Page 57)
>>
>>
>> -David J. Easter
>> Sr. Product Manager, Solution Strategy and Development
>> BMC Software, Inc.
>>
>> The opinions, statements, and/or suggested courses of action expressed
>> in this E-mail do not necessarily reflect those of BMC Software, Inc.
>> My voluntary participation in this forum is not intended to convey a
>> role as a spokesperson, liaison or public relations representative for
>> BMC Software, Inc.
>>
>> ________________________________
>>
>> From: Action Request System discussion list(ARSList)
>> [mailto:arsl...@arslist.org] On Behalf Of Meyer, Jennifer L
>> Sent: Tuesday, December 16, 2008 1:55 PM
>> To: arslist@ARSLIST.ORG
>> Subject: Re: floating licenses
>>
>>
>> **
>>
>> Once they are assigned a floating license, they keep that license until
>> they log out or are inactive for your minimum period.  In the user
>> client, the minimum that can be set is 1 hour.  In the mid-tier, it's 15
>> minutes, I believe, but please correct me if I am mistaken.
>>
>>
>>
>> ________________________________
>>
>> From: Action Request System discussion list(ARSList)
>> [mailto:arsl...@arslist.org] On Behalf Of Robert Halstead
>> Sent: Tuesday, December 16, 2008 4:45 PM
>> To: arslist@ARSLIST.ORG
>> Subject: Re: floating licenses
>>
>>
>>
>> Once a user requires a license, they have it till the license timeout or
>> till they log out as far as I know.  Most of our users are assigned a
>> read license unless they are modifying other people's tickets.  I
>> believe how the licenses work for floating is that the user is logged in
>> with a floating license.  How I wished it worked, is if the user was
>> logged in with a read license and remedy grab the floating license when
>> it needed it.  I've noticed that when we run out of floating licenses,
>> people that are logging in are getting that error message of no license
>> available which leads me to believe that Remedy is trying to assign them
>> a floating license.
>>
>> One sure fire way to tell would be to look at the aruser.log and see
>> what the log statement is when a user logs in.  I believe that when a
>> floating user logs in, the log statement would read FLOAT  GRANT WRITE
>> when they do.
>>
>>
>>
>> On Tue, Dec 16, 2008 at 2:20 PM, Opela, Gary L CTR USAF AFMC 72 CS/SCBAH
>> <gary.opela....@tinker.af.mil> wrote:
>>
>> **
>>
>> I just want to make sure that I'm clear on one thing.
>>
>> If a user has a floating license, will remedy assign them the license
>> before they must have it?
>>
>>
>> Basically, if the user is just submitting, modifying their own, and
>> querying, will remedy go ahead and assign a ticket? I think it probably
>> will, which I think might cause me some problems.
>>
>>
>>
>> I have a lot of users that just need a license for maybe 5 - 10 tickets
>> per month, I was going to look into transferring them over, like 100
>> users to 25 floating licenses. All of these users submit a lot of
>> tickets though, I just don't want any issues.
>>
>>
>>
>> Has anyone ever noticed if they've had issues if, say, all 100 users
>> were using remedy, but just not doing anything that required a license?
>>
>>
>>
>> ARS 6.3
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Gary Opela, Jr.
>>
>>
>>
>> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>> html___
>>
>>
>>
>>
>> --
>> "A fool acts, regardless; knowing well that he is wrong. The ignoramus
>> acts on only what he knows, but all that he knows.
>> The ignoramus may be saved, but the fool knows that he is doomed."
>>
>> Robert Halstead
>>
>> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>> html___
>> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>> html___
>>
>> _______________________________________________________________________________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>>
>> _______________________________________________________________________________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>>
>> --
>> This message was scanned by ESVA and is believed to be clean.
>>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to