HP Systems Insight Manager 7.2 Technical Reference Guide

Management processor product license keys can be added into the database because they can
be deployed directly to management processors.
NOTE: You cannot enter some types of valid keys if the key already exists in the database.
NOTE: To run License Manager, you must have administrative rights on the CMS (to set, select
Options+SecurityUsers and AuthorizationsUser) and choose the Configure CMS Security option,
and the All Tools toolbox (to set, select Options+SecurityUsers and AuthorizationsUser) on the
managed systems that you want to license.
Procedure 251 Add license from a file
1. To access License Manager, select DeployLicense Manager.... The Product License Information
table appears.
2. Click Add License... The Add Licenses section appears at the bottom of the page. For more
information, see Add License page.
3. Choose one of the following:
Enter the full path and file name in the Specify a file name and path field.
Click Browse... to select the desired file. For more information, see Add License page.
4. When the full path and file name appear in the Specify a file name and path field, click Process
to open the file. The contents of the license key file appear. For more information, see Keys
from file:.
5. Select license(s) to be added.
6. Click Add Licenses Now to add the keys to the database.
The page is refreshed and any invalid keys are deactivated.
7. Click Back if the licenses displayed is not the product license you wanted added. The Add
License section appears.
After successfully adding the keys to the database, the Product License Information table is
refreshed to display the updated license status in HP SIM.
Creating a license file
License keys are defined in an XML file with a .key extension. You can create these files. The
format is as follows.
<?xml version="1.0" encoding="UTF-8"?>
<KEYLIST>
<KEY>
<KEYSTRING>A2345-1B345-12C45-123D5-123E5</KEYSTRING>
</KEY>
<KEY>
<KEYSTRING>987RK-AB456-EW123-3489K-XQ555</KEYSTRING>
<PURCHASER>XYZ Company</PURCHASER>
<DATE>29 July 2006</DATE>
<PRODUCTNAME>Productname</PRODUCTNAME>
<PRODUCTVERSION>1.1</PRODUCTVERSION>
<DISP>1<DISP>
</KEY>
</KEYLIST>
The KEYLIST, KEY, and KEYSTRING values are required. The PURCHASER, DATE, PRODUCTNAME,
PRODUCTVERSION, and DISP fields are optional and are not needed if the only purpose is to
load multiple keys. If a key file is provided, the content should be left as is. A minimal file would
have a structure similar to the following, with at least one KEY tag:
<?xml version="1.0" encoding="UTF-8"?>
<KEYLIST>
386 Operations