Joe,
Just to help David out a bit with a couple of answers:
... delete the folder /etc/arsystem/ ....
Maybe... how is that for a crisp, clear, consise and definitive answer!
We will no longer be using the arsystem.lic file or the multlicense.lic
file. Those files are obsolete as of the
7.1 release.
However, there is one more file that you might have (you definitely have
if you are an ITSM customer). It is
called arsystem.tag. That file is still important.
This is a file with some licensing information for the approval server.
There is a form in the system that can hold the data that is in this
file, and in the future, applications will put
the data in that internal form. For now, the system will check both the
internal form AND this file for the tag
information and will use it appropriately. HOWEVER, the upgrade does
not copy the content of this file into
the form (because there are versions of the applications that still will
install in this file rather than the form).
There is no need for you to do anything, the system will still reference
the file if it is present. Over time, all
apps will be updated to use the internal table that is now present and
this file will not be needed. BUT, for
the interum, you need this file.
So, don't delete the directory if there is a .tag file in it. You can
get rid of the two .lic files (although it is
suggested that you keep a backup copy of arsystem.lic just in case and
why not leave it there).
In summary,
1) KEEP the directory because the arsystem.tag file is still needed and
deleting it removes functionality
2) Delete the multilicense.lic file if you want because it is no longer
used
3) Leave the arsystem.lic file as documentation/backup even though it is
no longer used and once the 7.1 or
later system is installed, all licenses in this file are uploaded
into the new license form
".. shared systems..."
As David noted, since all the servers in a server group are pointing to
the same DB and since the license data
is now a table in the DB, there is no need to generate parallel licenses
for applications, options, services,
users on each server in the server group. They all share the same
definitions.
HOWEVER, you will still need a server license for each server in the
group. You can enter multiple AR
System server licenses. Each will be tied to the Host ID of the
respective server. You cannot enter multiple
of other licenses, you just specify total counts for things like users
(much easier than having to add them up).
Each server will have its host ID in one of the licenses and that is how
it validates itself. Other licenses are on
the server in a table and by validating the server license, the rest of
the contents of the license are
accepted/validated
In a server group, ALL licenses apply to ALL servers (other than the AR
System server license which is per
server). There is no need to identify which are mine and which are not.
It is a single logical server environment
so all the app/user/option licenses are identical across the logical
group.
Hopefully, this answers the "tech detail" aspects of your questions,
Doug Mueller
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, September 04, 2007 12:53 PM
To: [email protected]
Subject: Re: 7.1 available today? (some more questions regarding
licenses)
**
As always, thank you David for answering my questions. But I think I
have a few more on the same topic..
So basically once you upgrade from 7.0.x to 7.1.0, could we delete the
folder /etc/arsystem/<xxx>?? Or its equivalent tree in Windows? I did
read somewhere on the release notes that the multilicense.lic file is
obsolete too for the same reason i.e. the licenses are now stored in the
database..
So if the licenses are stored in the database, how will that impact
'shared servers' or 'server group' AR System database. How will each
server be able to identify and validate its own license? In what table
are these licenses stored in and what is the column identifier that each
server will use to identify its licenses and ignore the rest?
I hope these aren't too many questions..
Joe
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Easter, David
Sent: Tuesday, September 04, 2007 3:41 PM
To: [email protected]
Subject: Re: 7.1 available today?
**
From the FAQ:
Q: What about my existing AR System Server? How will my
licenses be converted to this new model?
A: During an upgrade, AR System 7.1.00 will automatically
convert an existing .lic file to the new model. In addition, after
installation, the ability to import a previously created .lic file will
be available within the Administration Console.
Q: So it will update the .lic file?
A: No. Licensing in AR System 7.1.00 is now kept within the
database, not in a file. The .lic file will no longer be needed in AR
System 7.1.00.
Thanks,
-David J. Easter
Sr. Product Manager, Service Management Business Unit
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:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, September 04, 2007 12:35 PM
To: [email protected]
Subject: Re: 7.1 available today?
**
Does this mean you have to 'upgrade' the arsystem.lic file as
was done in the past when there were changes made with the license
format when upgrading its earlier versions?
Joe
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected] <mailto:[email protected]> ]On Behalf Of
Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, September 04, 2007 3:19 PM
To: [email protected]
Subject: Re: 7.1 available today?
Has anyone figured out the new licensing? I see form the
release-notes-710.pdf (pg. 8) the following:
Enterprise features
! Customer-driven license enforcement system-License keys are no
longer used to enforce limits for any license types except server
licenses.
Customers must self-enforce limits for all other AR System and
application license types.
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected] <mailto:[email protected]> ] On
Behalf Of Easter, David
Sent: Tuesday, September 04, 2007 1:23 PM
To: [email protected]
Subject: Re: 7.1 available today?
"What's New" was posted previously to the BMC Developer's
Network:
http://developer.bmc.com/jiveProd/entry.jspa?externalID=1926
<http://developer.bmc.com/jiveProd/entry.jspa?externalID=1926>
Thanks,
-David J. Easter
Sr. Product Manager, Service Management Business Unit
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.
__20060125_______________________This posting was submitted with HTML in
it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
