Title: RE: After all these years (10) confused about Licensing
**

Misi:

Thank you for reminding us about rrrLicense.  Does it show if the user was given a write token or just a Float (Read)?

Unfortunately, due to DoD restrictions on Temporary Duty, I am not able to attend RUG/BUW this year.  Also, I am looking for a new position.

James McKenzie
 

-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Misi Mladoniczky
Sent: Monday, August 28, 2006 8:01 AM
To: [email protected]
Subject: Re: After all these years (10) confused about Licensing

Hi,

The user.log-file has the information you need to determine if you should give a user USER-FIXED or USER-FLOATING license. You can allways use the free portion of our rrrLic-tool to determine how well you are tuned, and if you have the correct mix of licenses on your server.

Concerning the APP-licenses, there is no information in the logfile, but you can get to it through the API.

We have just created a first version of a rrrLicMonitor that use the API to poll the statistics of APP-usage to a logfile. This will enable us to do the same calculations for the APP-licenses as we have done for many years with the USER-licenses.

The basic idea of license tuning, as we see it from our experience is this:
1. Find the absolute peak hours during the period you are analyzing (maybe
6 weeks)
2. Use the cost ratio between FIXED/FLOATING licenses to decide how much a user should be logged in to get a FIXED vs FLOATING license. This value has allways been 2.5 (or 40%). In other words, if a user is logged in more than 40% during peak hours, give him a FIXED license.

3. When you have found the absolute number of users to give a FIXED license, put all the rest of your money on FLOATING licenses.

4. Repeat the analasys every month or so, to find the users that has changed their usage behaviour.

See you at the "RUG"!

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

> James:
>
> It's going to be interesting for many Remedy users now that the same
> enforcement is being used for app licenses with the 7.0 apps.  We have
> a mix of fixed and floating licenses, with a different number of
> licenses and a different mix for each of the apps.  We have no way to
> guage the current usage either (5.6 apps).
>
> Axton
>
> On 8/28/06, McKenzie, James J C-E LCMC HQISEC/L3
> <[EMAIL PROTECTED]> wrote:
>> **
>>
>>
>> Mark:
>>
>> This has since been fixed.  This was never supposed to be this way.
>>
>>
>> James McKenzie
>>
>>
>>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList)
>> [mailto:[email protected]] On Behalf Of Mark Walters
>> Sent: Saturday, August 26, 2006 4:53 AM
>> To: [email protected]
>> Subject: Re: After all these years (10) confused about Licensing
>>
>>
>> Guess again :-)
>>
>> SW00218113      Server modified so client tools will not claim a
>> floating
>> write token at login time when using a preference server. Requires
>> corresponding client tool patch 003 (6.3) (i.e., User Tool, Alert
>> Tool) to produce the expected results.
>>
>> Mark
>>
>> On Fri, 25 Aug 2006 18:18:40 -0400, Geoff Endresen
>> <[EMAIL PROTECTED]> wrote:
>>
>>
>> >So I guess this is a feature, not a bug ;-)
>> >
>> >-----Original Message-----
>> >>From: Axton Grams <[EMAIL PROTECTED]>
>> >>Sent: Aug 25, 2006 6:16 PM
>> >>To: [email protected]
>> >>Subject: Re: After all these years (10) confused about Licensing
>> >>
>> >>How convenient for them.
>> >>
>> >>Axton
>>
>>
>>
>>
>> _____________________________________________________________________
>> __________ UNSUBSCRIBE or access ARSlist Archives at
>> http://www.wwrug.org __20060125_______________________This posting
>> was submitted with HTML in it___
>
> ______________________________________________________________________
> _________ UNSUBSCRIBE or access ARSlist Archives at
> http://www.wwrug.org
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

__20060125_______________________This posting was submitted with HTML in it___

Reply via email to