Thank you for sharing that, Misi! Matt R.
-----Original Message----- From: Misi Mladoniczky [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 05, 2006 12:04 PM To: [email protected] Subject: AR System User Licenses Hi All, I just thought that I would share with you the information I extracted during BMC UserWorld in regards to User License Allocation within the AR System. I first got some conflicting information from R&D, but after a long one on one chat with Doug Mueller, I feel that I know how it works in reality, and how it is supposed to work. The "reality" and "supposed to" fortunately work in perfect tandem, or so says my experience. A. FLOATING USER WRITE LICENSES are allocated on any operation to the server, except for the actual login process and retrieval of form definitions. It does not matter if the user does a "READ" or a "WRITE" operation, the license token is grabbed anyway. B. There are a couple of API-calls that does not affect license allocation, which are associated with things like the login process, the form list, opening of forms and caching of form definitions. C. There is only one reason that will cause a FLOATING user to get a FLOATING-READ license. This is when there is no licenses available. D. Starting with version 7 of the AR System, application licenses will be enforced in the same way. The difference is that the licenses tokens are only grabbed when a user READ or WRITE data to those forms tagged for the specific application. To be technically correct, the application licensing functionality has been around since version 6, but the applications has not been packed in such a way that they made use of this functionality. Best Regards - Misi, RRR AB, http://www.rrr.se ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
