Simple answers:
1. Each application typically requires a "server license". For example,
you'll need a Change Manager application license for the server you want to
run the Change Management application. (You'll also need an AR System
application license, typically running on the same server, and multiple
applications can use/share the same AR System server license.)
2. User (client) licenses fall into two categories. "Fixed" licenses are
also known as "named" licenses, as they're typically tied to a specific
user, not to a specific server. "Floating" licenses are also known as
"concurrent" licenses, as they determine how many user may "concurrently"
access the application. They're typically assigned to a server (or server
pool), not to an individual user. Floating licenses are kept in a revolving
pool and metered out on a first come, first served basis. With AR System 5
and earlier, each floating license was assigned to a server; problem was,
when that server became unavailable, the associated floating licenses also
became unavailable. With AR System 6 came the concept of server pools,
which introduced a better way to manage floating licenses; if assigned to a
server pool, rather than to an individual server, if one server becomes
unavailable, the associated floating licenses don't necessarily become
unavailable. The concept of reserved license pools was also introduced,
which allowed you to reserve a set number of floating licenses for special
user groups (such as IT management or occasional-use executives).
3. Here's where it gets confusing. To license a user for AR System, you
need a fixed or floating AR System user license. To license a user for an
application (such as Change Management), you need a fixed or floating Change
Management user license, AND a fixed or floating AR System user license.
Also, a fixed Change Management user license can only be used with a fixed
AR System user license, and a floating Change Management user license can
only be used with a floating AR System user license. When you purchase new
application user licenses you have the option of purchasing an "incremental"
application user license (e.g., a fixed or floating Change Management user
license by itself, which assumes you already have the companion fixed or
floating AR System user license), or a "full" application user license
(e.g., a fixed or floating Change Management user license bundled with a
companion fixed or floating AR System user license.)
4. Pricing can also be confusing. A "production" license is a full price
license (e.g., a Change Management application license lists for $22,000),
intended for production environments. A "development" (or "dev") license or
a "test" (or "QA") license typically costs half as much (e.g., a "dev"
Change Management application license lists for $11,000) but can only be
used in a non-production environment. In addition, "standby" or "hot
backup" licenses, which let you set up a standby (passive failover) server,
are also available at half price, but are typically complimentary for large
accounts. In the past, Remedy would charge full maintenance fees for dev or
test licenses, but that policy changed a couple of years ago and now
maintenance for dev or test licenses is half of maintenance for production
licenses.
Ivan, to answer your question on an application license, that would be
equivalent to a "server" license. (Please note that Remedy does not use the
term "server license" and prefers instead to use the term "application
license". Since it's a license for the application to run on a server, I
call it a server license.) And yes . . . if you want to set up a
"non-production" Remedy environment for your development or QA teams, you'll
need to purchase separate server and user licenses. Bummer.
Nick, to answer your question on whether a floating application license
stays with a user, the answer is "no" -- only a fixed user license "follows"
the user. If an occasional user logs in and requests a floating license (a
background process Remedy performs automatically), if a floating license is
available it will be assigned to that user. Once assigned, it remains
"attached" to that user until one of two events occurs: 1) the user
explicitly signs out (which immediately releases the floating license); or
2) the user remains inactive, their Remedy session times out, and the
floating license is returned to the floating license pool. Please note the
timeout clock cannot be set to be shorter than 60 minutes.
If you need more detailed answers or have a specific issue to discuss,
including licensing strategies and additional pricing information, feel free
to contact me directly, off the ARSlist.
-- Bing
Bradford Bingel ("Bing")
ITM3 California
http://www.itm3.com/
[EMAIL PROTECTED] (email)
925-260-6394 (mobile)
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Friday, March 30, 2007 3:24 PM
To: arslist@ARSLIST.ORG
Subject: Re: Application licensing question
The history has been (for products that require a server side license) that
a separate license is required per server; examples include flashboards,
arserver, and migrator.
The server side application licenses are new to the mix, starting with the
7.0 applications. I would imagine that BMC expects users to purchase a
separate application license per server, right wrong or indifferent; which
it seems you are confirming.
The deployable apps 'require' the presence of an app license (in addition to
user licenses), and this enforcement is (probably) BMC's method of enforcing
what they always considered the proper usage/licensing of their
applications.
Development licenses are usually priced at a reduced rate from the regular
list price, though if memory serves me correctly, the pricing on annual
support/maintenance is against the list price.
Even the products that Remedy acquired (ITMasters) that had a different
licensing scheme (e.g., per desktop), were moved to the licensing model that
Remedy applies to all it's products, which is per server. Unfortunately,
this makes both the price entry point and growth price extremely expensive.
Consider you want to use the following applications:
- Asset
- Change
- Incident
- Problem
- Service Request Management
- SLM
It get's really expensive really fast when (1) you have multiple
environments (dev, test, production) and (2) you have a growing user base,
esp, when it is difficult to predict the growth of said user base.
I also have reservations about the floating license model for development
environments, simply due to the fact that purchasing them for a dev/test
environment is cost prohibitive when the fixed can be used in all
environments; we have been burned by a number of defects in the last couple
of releases related to floating licenses (single users holding multiple
floating licenses, no method in mid-tier to soundly release floating
licenses, etc.).
Axton Grams
On 3/30/07, Ivan Runions <[EMAIL PROTECTED]> wrote:
> I don't quite understand the phrase "stay with the user".
>
> The level of licenses required for Joe User to run Incident Management
> 7.0 is
> 1) An Application Fixed or Float license for the person
> 2) An ARS Fixed or Float license for the person
> 3) An application license for Incident Management
> 4) An ARS Server license for the server.
>
> My question is re: #3 above... is that a "site" license or a "server"
> license.
>
> -ivan-
>
>
> ARSList wrote:
>
> >I am curious doe the floating application licenses stay with the user?
> >
> >Nick
> >Havin' Fun in Sacramento
> >
> >
> >[EMAIL PROTECTED]
> >
> >-----Original Message-----
> >From: Action Request System discussion list(ARSList)
> >[mailto:[EMAIL PROTECTED] On Behalf Of Ivan Runions
> >Sent: Friday, March 30, 2007 12:39 PM
> >To: arslist@ARSLIST.ORG
> >Subject: Application licensing question
> >
> >My question is on site licenses vs server licenses.
> >
> >The licensing tool basically enforces this, because User Fixed
> >licenses come up as being valid for a site, whereas User Float
> >licenses come up as being valid for a server.
> >
> >My question is on the Application license (not the Application
> >Fixed/Float license). The license tool accepts the Incident &
> >Problem Application license as being valid for a site, however my
> >Sales Rep is saying we need to purchase additional development copies
> >for our Test and QA servers.
> >
> >Can I get opinions, or better yet, facts? on this?
> >
> >-ivan-
> >
> >
> >
>
> --
> Ivan Runions
> Information Technologies
> University of Calgary
> Calgary Alberta Canada
> (403) 220-4437
>
> ______________________________________________________________________
> _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> ARSlist:"Where the Answers Are"
>
____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
