How to implement UAPM License Compliance.

Document ID : KB000054434
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

How to implement UAPM License Compliance.

Solution

This example walks through the steps required to use the license compliance feature in UAPM. As a starting point, it is assumed that discovered data and downloaded CA-provided software definitions already exist in the MDB. These steps must be completed (using DSM/SCM or a 3rd party discovery tool) before license compliance can be implemented in UAPM.

The first step is to use the APM Utility to create models and model versions in UAPM corresponding to discovered software. The APM Utility uses the CA-provided software definitions you downloaded via DSM/SCM to create these new models and model versions.

The APM Utility is available from Start | All Programs | CA | Unicenter Asset Portfolio Management | APM Utility

After login to the MDB, select Utility | Load Software Content

Figure 1

After completion, the APM Utility will report the number of models and model versions created in UAPM from the CA-provided software definitions. Hopefully, you will see a larger number than the zero reported here. You may see zero reported results here if you have already performed this step ? as I have.

Figure 2

Notice that new software models created are loaded in inactive status. You must change the status to active before these models can be used in license compliance.

You can create an advanced search to locate inactive models.

Figure 3

Figure 4

In UAPM 11.3.4 and later, you can use the Mass Change Wizard (accessible from the ?Change Values? button) to reset the new models to active status: (Model Inactive) Value = False.

Figure 5

It will help you to remember these two equations. A model in UAPM is equivalent to a manufacturer name in license compliance, while a model version is equivalent to a software product name in license compliance.

Model = Manufacturer Name
Model Version = Software Product Name

In the figure below we see the output of a license compliance report before you have created UAPM owned assets linked to discovered software assets. The Model Name and Model UUID columns contain no data, and the License Count = 0. This is because no software assets have yet been created in UAPM which are linked to the discovered Manufacturer Name and discovered Software Product Name of discovered software assets. The Install Count column contains the number of discovered installations of the software, while the license count column contains the number of associated license assets .

Figure 6

To create assets corresponding to discovered manufacturers and products, search for a model name corresponding to the discovered manufacturer name in UAPM Models. Let?s walk through an example using the manufacturer, BEA Systems, Inc.

Search for the manufacturer, BEA Systems, Inc., in license compliance and make note of a row where the model name and model UUID fields are blank:

"BEA Tuxedo 8 x86 32"

The license count in a row like this will always be zero because no license assets exist corresponding with the discovered software "BEA Tuxedo 8 x86 32".

Figure 7

Now, return to the UAPM Home page and select Model to search for the model name matching the manufacturer name (BEA Systems, Inc.).

Select BEA Systems, Inc. from the model results list to display the model details page.

Figure 8

When the model details page appears, expand the model version section. Remembering that model versions are equivalent to software product names, we see that the software product name ?BEA Tuxedo 8 x86 32? is not in the list of model versions.

You are free to name a model version anything you want, but it will be much easier to link model versions with discovered software if you always name your model versions (and models as we shall see later) to match the software product name. Scroll to the right to view the software product name (SW Product Definition) associated with the model versions that are already defined.

Figure 9

Since ?BEA Tuxedo 8 x86 32? is not in the list of model versions, we need to create a new model version by this name.

To create a new model version which will correspond to a SW product definition (software product name) that is known within license compliance, click "Insert Row" in the model version area, scroll to the right and click ?select new? in the SW Product Definition column.

In the search results list that appears, select the SW Product Definition we are searching for, "BEA Tuxedo 8 x86 32".

Figure 10

You will be returned to the model details page with a new model version row for "BEA Tuxedo 8 x86 32".

In the new row, scroll to the left and type "BEA Tuxedo 8 x86 32" in the version name field. Click "save" at the top of the model details page.

Figure 11

You have now created a new model version which corresponds to a SW product definition (software product name) that is known within license compliance. For software, the Asset is the license you have purchased from a software manufacturer.

To complete the process, you must create an asset corresponding to the software product name discovered by your discovery tool.

Click Create Asset.

In our example, we will assume that you have purchased 99 single server licenses for the asset. In Asset Name, enter the name of your model version, ?BEA Tuxedo 8 X86 32?. The model name and other data is populated from the model version selected. You may fill in any other information desired.

Figure 12

After providing this basic information, scroll down to the Current Status box. This is where you will select the model version information for the software you have purchased. Select the model version created above ("BEA Tuxedo 8 x86 32").

Figure 13

Scroll back to the top of the asset page and click "Save".

You have now created an asset to match the discovered software from license compliance. You will receive a confirmation message that the save has completed successfully.

Return to the UAPM home page and select license compliance. To narrow your search, enter "bea*" in the manufacturer field and click "Go".

Figure 14

You will now see that the entry for "BEA Tuxedo 8 x86 32" has changed. A Model Name is now listed, along with a license count of 99, and a Model UUID is also now listed.

You can see that one "installed count" was discovered by your discovery tool, and that 98 licenses are still available for use.

Figure 15