I thought I would just put all my answers into one E-mail so that there aren't a bunch of separate threads flying around...
> Q: Will the unlicensed AR Server, which presently runs in Evaluation mode with 3 fixed licensed and a > 2000-record limit per table, still be available with v7.1? Yes. > Q: Will we (Remedy developers) now have the ability to run AR Server (in Evaluation mode) on our own personal computer with the > other Remedy applications (Change, Asset, etc) without having to purchase licenses for the applications? Licensing policies have not changed. Purchasing requirements have not changed. The same restrictions on license usage will be in place with AR System 7.1.00 that are in place today. Licensing is not changing - only the need for keys. > If somebody logs in that has a defined float license - but performs no actions that require a license > (say submits their own record) - will a license usage be logged? License behavior has not change in AR System 7.1.00. Actions or situations that consume a license today will continue to consume a license in AR System 7.1.00. Only the need for keys has changed in AR System 7.1.00. If a license is consumed, it will be logged as such and appear in your usage report. > One of the major troubles with MidTier is that it seems to generate different versions of HTML-Forms for each combination of user groups This has been updated in AR System 7.1.00 in pre-fetching. Each form is prefetched according to the set of permissions for that form and its fields. For example, if the administrator selects a form that has 75 fields, the entire form (all 75 fields plus workflow) is cached. As a user accesses the form, the Mid-Tier will only grant the user access to those fields and workflow objects that match the group permissions of that user - but the original form is not cached a second time as it is today. It's a bit more technical than this - but the general answer is it's better than in AR System 7.0.01. The final documentation will explain it better than I probably just did. ;-) > you will be able to configure a ceiling for each license type, which is supposed to correspond to the number of licenses you've purchased. It is correct that administrators may still set a "ceiling" for each license type. What was done in keys previously is now controlled by the administrator. If the administrator chooses to set a maximum number of user licenses, for example, AR System will behave just like it does today. Licensing is not changing - only the need for keys. Note that the maximum does not have to correspond to the number of licenses you've purchased, although many administrators will find it most convenient to do so. This was detailed in the original FAQ. > I would continue the argument that the recorded values are not accurate with the way the mid-tier handles floating licenses, > e.g., not releasing the token when the user ends the session (i.e., closes the browser). This topic is a bit tangential to the changes made in AR System 7.1.00. The issue of the Mid-Tier not being able to recognize a session closing when the user does not logout properly is not addressed in this release - but the feedback from the customer base has been heard and BMC will look into the issue further in a future release. This was the #2 issue cited in the recently performed survey as a restriction for moving to a web-client only environment. Thanks for the feedback so far! David J. Easter Product Line Manager AR System - BMC Service Management Business Unit _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
