bmc license usage collection utility 2.0...bmc license usage collection utility 2.0.00 bmc software...

BMC Software Confidential. BladeLogic Confidential.

Product documentation

BMC License Usage Collection Utility

2.0.00

URL:

Date: Apr 11, 2016 9:00 AM CDThttps://docs.bmc.com/docs/display/lucu2000/Home

BMC License Usage Collection Utility 2.0.00 BMC Software Confidential. BladeLogic Confidential.

BMC License Usage Collection Utility 2.0.00 Page of 2 53

This space contains information about the BMC License Usage Collection Utility 2.0.00 release.



What's new

Announcement

Version 2.0.00 available on April 11, is 2016 . This includes the following enhancements:

New support for BMC products

Support has been added for BMC TrueSight Capacity Optimization 10.5 (TSCO)

Corrections for BSA 8.2 to 8.6 reportingCorrections for BSA 8.2 to 8.6 reporting has been added. See the following topics:

UpgradingConfiguring environment settingsAdding deployments

Product enhancements

You can now schedule license reports. See Scheduling reports

Documentation enhancements and changes

Version 2.0.00 wiki docs and PDF has been added( wiki docs have been maintained as a separate space.)Version 1.6.00The following topics have been added:

2.0.00 enhancementsUpgradingServer clustering information in reportsScheduling reports

The screenshots in the topic have Getting started with deployments and reportsbeen updated with the following:

The License Report tab has been updated to show the Execution Method column (Manual or Auto)The Schedule reports tab has been added

https://docs.bmc.com/docs/display/LUCU/Home



| PDFs Help

https://docs.bmc.com/docs/display/lucu2000/PDFs

https://docs.bmc.com/docs/display/help

https://docs.bmc.com/docs/display/help



About the BMC License Usage Collection UtilityThe BMC License Usage Collection Utility enables you to view license usage for your BMC reportsproduct deployments. Each license report is specific to each BMC product; therefore, the file format and contents vary depending on the product. You can also view log reports that can be used to troubleshoot problems with failed deployments and with running reports.



Release notes and noticesThis section provides information about what is new or changed in this space, including urgent issues, documentation updates, service packs, and patches.

Tip

To stay informed of changes to this space, on this page.place a watch

Tip

Ready-made PDFs are available on the .PDFs page

Related topicsKnown and corrected issues2.0.00 enhancements1.6.00 enhancements1.5.00 enhancements1.0.00 enhancements

Known and corrected issuesThe following issues pertain to this release of the and its BMC License Usage Collection Utility service packs and patches.

Known and corrected product issuesKnown and corrected product issues

Defect

ID

Component Description Affected

versions

Corrected

in

LU-57 Installation A "Failed to find any suitable JVM" message appears while installing the License Utility using setup.exe when Java has not been installed on the computer.

1.5.00 2.0.00

All The BMC License Collection Utility is supported only on an English locale in order to run and view license usage reports.

1.0.00

DE93661 Manage Deployments

If the BNA and ADDM default ports are changed, the license usage will not be collected.

1.0.00 1.5.00

https://docs.bmc.com/docs/display/help/Notifications

https://docs.bmc.com/docs/display/lucu2000/PDFs



Related topicRelease notes and notices

2.0.00 enhancementsThis section contains information about enhancements in version 2.0.00.


Support has been added for BMC TrueSight Capacity Optimization 10.5 (TSCO)

Corrections for BSA 8.2 to 8.6 reportingCorrections for BSA 8.2 to 8.6 reporting has been added. See the following topics:

UpgradingConfiguring environment settingsAdding deployments


You can now schedule license reports. See Scheduling reports

Documentation enhancements and changes

Version 2.0.00 wiki docs and PDF has been added( wiki docs have been maintained as a separate space.)Version 1.6.00The following topics have been added:

2.0.00 enhancementsUpgradingServer clustering information in reportsScheduling reports

The screenshots in the topic have been Getting started with deployments and reportsupdated with the following:

The License Report tab has been updated to show the Execution Method column (Manual or Auto)The Schedule reports tab has been added


https://docs.bmc.com/docs/display/LUCU/Home




The Report File Prefix field has been added to the Manage Deployments form where you can enter the server name. This will be automatically appended to the report file name. See

.Adding deployments

The Email Attachment File Prefix text box has been added to the License Report tab. This enables you to append a prefix to the file name, such as your organization's name, so that you can easily find the file in your default email client mailbox. See .Emailing reports

When reports are generated by the License Utility, a CSV file is created from the BMC product's file. The License Utility internally converts the native file format native (for

to the CSV format. example, XML or HTML) See Running reports .

Note

For BSA versions 8.5 and 8.6, reports are generated in XML format only. The License Utility converts the XML file into CSV format.

Documentation enhancements

The and topics have been updatedRelease notes and notices Known and corrected issuesA table listing the supported BMC products for the BMC License Usage Collection Utility 1.6.00 has been added to the topicIntegratingThe topic has been addedLanguage informationThe screenshots in the topic have been Getting started with deployments and reportsupdated



BMC Client Management (BCM)

BMC Bladelogic Server Automation (BSA) 8.7

New feature

New license report email attachment feature




Installation

The installer includes a license for easier installationThe Java Runtime Environment (JRE) is included with the utility, eliminating the need to install/upgrade the existing JRE installed on user computersAs part of the initial setup and prerequisites, an a utomated copy process was added for BMC product-specific script filesA new feature was added to encrypt/decrypt credentials

New user interfaceSee the Quick tour of the new UI with screenshots in the Getting started with deployments and

reports topic.

New robust and feature-rich user interfaceLicense Report and Management Deployment tabsNew Help tab to provide user documentation

Deployments

Add, edit and delete deployments with real-time connectivity test and validation for a given user session

Test existing deployments to ensure data validity at any point of time

Reports

You can run license usage reports on:ADDM, ARS, BDA, BNA, and BSAYou can run reports for deployments hosted on both Unix/Linux and Windows platforms

When running license usage reports, you can:Select single, multiple, or all deploymentsSelect various duration times (start and end dates for the report time frame)View real-time status messages while the report is running



PlanningThe following topic provides information for planning to install the BMC License Usage Collection Utility:

System requirementsLanguage information

Recommendation

Before you install the product, you should review and understand the entire installation process. For information on installing the product, see .Installing

System requirementsThe License Utility can run on a server or desktop environment that has connectivity to the computers where the BMC products are installed. The following hardware and software requirements must be met before installing the BMC License Usage Collection Utility.

Software requirementsOperating systemsThe following operating systems are supported for the ControllerHost:

Operating system Version

Windows • Windows 7 Enterprise Edition (x86)• Windows 2008 Enterprise Server (x64)• Windows 2012 Enterprise Server

Email clientThe following email clients are supported for the feature (not license report email attachmentrequired for installation):

Operating system / version Email client / version

Windows 2012 (64-bit)Microsoft Office Outlook 2013 (64-bit and 32-bit)

Windows Enterprise Server 2008 (32-bit)Lotus Notes (32-bit)



Operating system / version Email client / version

Windows Enterprise Server 2008 (64-bit)DreamMaileM clientPostboxSeaMonkeyThunderbirdWindows Live Mail

Windows 7 (32-bit and 64-bit)Microsoft Office Outlook 2013 (32-bit)

Hardware requirementsComputer Recommended specifications

Controller Host Installation folder size: 299 MB

Windows Installer size: 300 MB

Language informationThe BMC License Collection Utility is supported only on an English locale in order to run and view license usage reports.

Related topicKnown and corrected issues



1.

InstallingThis section provides information about installing the BMC License Usage Collection Utility .

You can install the BMC License Usage Collection Utility on Windows systems. For more information, see the and .System requirements Prerequisites for installation

Prerequisites for installationPerforming the installationUninstalling

Prerequisites for installationMake sure that your system meets the minimal requirements for Hardware and Software. For more information, see the .System Requirements

The ControllerHost must be able to connect remote servers where BMC products are installed through WMI for Windows servers and through SSH for Unix servers.

Performing the installationThe following instructions describe how to install or reinstall the BMC License Usage Collection Utility. If you are upgrading, please see .Upgrading

Note

The installer screens are provided in multiple languages. However, the application is only available in English.

To install or reinstall the BMC License Usage Collection Utility

Log in as an Administrator on the computer where you want to install the BMC License Usage Collection Utility.

BMC recommends installing the License Usage Collection Utility on a computer/server separate from the computer(s) where the BMC products are hosted. License usage reports do not execute successfully when connecting on the same server (localhost) .This computer must be able to connect to all servers/systems that host BMC products, and will be referred to as the “ControllerHost”.



2. 3.

4.

5.

6. 7.

8. a.

b.

9. a.

b.

10.

11. 12.

13.

Download the installer file from the page.BMC Customer Support CommunityExtract the installer file contents in any directory on the ControllerHost. This will create a directory named .Disk1

Run the located in the directory.setup.exe Disk1

The installer screen appears.BMC License Usage Collector

If you want to install in a language other than English, click the , select a down arrow

language, then click .OK

On the screen, click .Welcome Next

On the screen, review the license agreement, then select License Agreement I agree to

, and then click .the terms of license agreement Next

If you are installing the application for the first time:On the screen, accept the default location (Directory Selection C:\Program

), or click Files\BMC Software\LicenseUsageCollector Browse to select an installation folder, then click . Next

On the screen, click .Installation Preview Install

The progress bar appears while the application is installed.If you are reinstalling or upgrading the application:

On the screen, click .Installation Preview Install

The progress bar appears while the application is reinstalled.A message displays asking if you want to overwrite the existing directory. Click Yes

to overwrite all files.to All

If you select only Yes or No, you will need to confirm the directory location for each file.If you select Yes or Yes to All, all of the deployment details history will be removed.If you select No to All, all of the deployment details history will be retained.

Accept the default "Create and Start Scheduler Service", or deselect the check box, then click .Next

The LUCService (License Usage Collector Service) will appear in Windows Services with the status "Started". You can manually start and stop the LUCService.Accept the default "Create Shortcut on Desktop", or deselect the check box, then click .Next

(Optional) On the screen, click to see the installation log.Installation Summary View Log

The window appears. You can click each item in the licenseuagecollector_install_log.text

list to view additional details.On the screen, click .Installation Summary Done

To access the BMC License Usage Collection Utility user interface, see Accessing the BMC .License Usage Collection Utility

Related topicUninstalling

https://communities.bmc.com/docs/DOC-36548



1.

2.

3. 4.

5. 6.

7.

8.

UninstallingYou can either specify to uninstall the License Usage Collector Utility application and usage data at once, or you can specify to uninstall only the application and preserve the usage data. You cannot uninstall only the usage data.

To uninstall the BMC License Usage Collection Utilityee

From the menu, select Start All Programs > BMC Software > LicenseUsageCollector >

.Uninstall LicenseUsageCollector

The screen appears.BMC License Usage Collector Uninstaller

If you want to uninstall in a language other than English, click the , select a down arrow

language, then click .OK

On the screen, click .License Usage Collector Uninstaller Next

Select one of the following:License Usage Collector (version #) Uninstallation (This will uninstall both the application and the usage data files.)

or

Uninstall License Usage Collection (version #), then deselect the Uninstall

check box.License Usage Data (version #)

(This will only uninstall the application and will preserve the usage data files.

Warning

If you select , all of the usage data will be Uninstall License Usage Data

deleted. By default, these files are located inC:\Program Files\BMC Software\LicenseUsageCollector\licenseusagecollector\user.If you attempt to only uninstall the usage data, a warning message appears directing you to go back and select one of the two options above.

After you have made your select, click .Next

The screen displays the selected features to be uninstalled. Click Uninstallation Preview

.Uninstall

The progress bar appears while the application is uninstalled.(Optional) On the screen, click to see the log.Uninstallation Summary View Log

The window appears. You can click each item in licenseuagecollector_uninstall_log.text

the list to view additional details..On the screen, click Uninstallation Summary Done

The LUCService (License Usage Collector Service) will be removed from Windows Services.



9. Restart your computer to complete the uninstallation process.



1.

2.

1.

2.

3.

Configuring product serversAfter you install the BMC License Usage Collection Utility, it must be able to connect to remote servers that host BMC products to successfully complete the license usage collection process.

The utility secures a WMI connection to connect Windows based servers and an SSH connection to connect UNIX/Linux based servers. In both the cases it uses the deployment details, such as server name, user credentials, etc. to connect the remote servers that the user has entered into the utility on the screen.Add Deployment

The utility does not require its users to have administrator privileges on the servers. However, as a one-time setup activity, the user must complete the following tasks:

With the assistance of the your server administrator, ensure that the user has the required permissions for WMI/SSH connections on remote servers. See .Configuring user settingsVerify that the environment settings are in place. See .Configuring environment settings

Related topicsConfiguring user settingsConfiguring environment settings

Configuring user settingsFollow the steps below in each section for your operating system.

Note

Please contact your local administrators who are responsible for configuring the servers for BMC products if you encounter any issues while creating or setting up the environment variables.

WindowsConfigure the Windows environment for non-administrator users

(Optional) Create a user account

Click , and in the box, type then Start Search programs and files mmc compmgmt.msc , press .Enter

In the left pane of , expand Microsoft Computer Management Console Local Users and

.Groups

Right click the folder, then click .Users New User



4. 5.

6.

1. 2.

3.

1. 2.

Type the appropriate information in the dialog box, and then click .Create

Ensure that the checkbox is selected.User must change password at next logon notThis will ensure that the BMC License Usage Collection Utility will not prompt the user to change their password.When you finish creating user accounts, click .Close

Windows Server 2003

Note

The following steps are required only for Windows Server 2003.

In , right click the executable C:\WINDOWS\system32\cmd.exe.Windows Explorer

Select the tab.Security

On the dialog, and add the following permissions to it:cmd.exe Properties

ReadRead and Execute

Add the required groups to the new user

In the left pane of expand the folder.Microsoft Management Console, Users

Right click the user name, then click .Properties



3. 4.

5.

1. 2. 3.

1.

2.

Select the tab.Member Of

Click , then add the following groups:Add

Distributed COM UsersPerformance Log UsersUsers

Click .OK

Verify password settings for non-administrator users

In the left pane of expand the folder.Microsoft Management Console, Users

Right click the user name, then click .Properties

Ensure that the checkbox is selected.User must change password at next logon notThis will ensure that the BMC License Usage Collection Utility will not prompt the user to change their password.

Configure WMI user access permissions for non-administrator users

Select , then enter and press .Start wmimgmt.msc Enter

This opens the Windows Management Instrumentation (WMI) console (wmimgmt).In the console tree, right-click and then click .WMI Control, Properties



3.

4.

5. 6.

On the dialog, Click the tab, then click the WMI Control Properties Security Security

button.

On the dialog, select the user, then select the check Security for Root License Allow

boxes for each of the following permissions:Execute MethodsEnable AccountRemote EnableRead Security

Click the button.Advanced

On the dialog, select the user, then click Advanced Security Settings for Root License

the button.Edit



7. On the dialog, from the list, select "This namespace Permission Entry for Root Apply to

and subnamespaces", then click .OK

UNIX(Optional) Create a new user

Note

The user should be authorized to connect remotely using SSH.

If you want to add a new user, create the new user with the command on the UNIX useradd

operating system.

Configuring environment settingsFollow the links below to configure BMC product servers.

Note

Configuration is not required for:

BMC Network Automation (BNA)BMC Atrium Discovery and Dependency Mapping (ADDM)BMC Client Management (BCM)BMC TrueSight Capacity Optimization (TSCO)

Configuring BMC Bladelogic Database Automation (BDA) systems



1.

1.

2.

UNIX

Ensure that the SSHD process is running on standard ports.

Note

BDA license gathering is supported only for the root user.

Configuring BMC BladeLogic Server Automation (BSA 8.2 to 8.6) systems

Identify the servers where the BMC BladeLogic Server Automation (BSA 8.2 to 8.6) database is installed.Make sure all ORACLE environment variables are set and accessible for the logged-in user on that server (Server user field value).

Note

The database user should be the normal user with Read/Write permissions to the Database schema.

WindowsEnsure that the "ORACLE_HOME" environment variable is set for the logged-in user (Server user field value) on that server.

UNIXEnsure that the "ORACLE_HOME" environment variable is set in the “. profile” file for the logged-in user (Server user field value) on that server.

Configuring BMC BladeLogic Server Automation (BSA 8.7) systems

Note

For BSA 8.7 Windows and UNIX: The “Profile User” must be assigned to the “BLAdmins” role.

Windows and UNIXIdentify the servers where BMC BladeLogic Server Automation (BSA) is installed.



1. 2.

1. 2.

a.

3.

WindowsEnsure that the NSH folder is in the system path.

UNIXhe SSHD process is running on standard ports.Ensure that t

Configuring BMC Remedy AR System Server (ARS) based products

Windows

Identify the server where BMC Remedy AR System Server (ARS) is installed.Ensure that the "BMC_AR_SYSTEM_HOME" environment variable is set on that server.

UNIXVerify each of the following:

The SSHD process is running on standard ports.The user whose credentials are being used by the License Utility to connect to this server:

Has BMC_AR_SYSTEM_HOME mapped to the correct directory and exported in the .profile file.For example: Export BMC_AR_SYSTEM_HOME=/<dir1>/<dir2>/ARSystem

The $BMC_AR_SYSTEM_HOME/db/LicenseReport.txt file has read access permission for the non-root user.



UpgradingThis section provides information about upgrading .BMC License Usage Collection Utility 2.0.00

You do not have to manually uninstall a previous version of BMC License Usage Collection Utility before upgrading to version 2.0.00. The installation process will automatically upgrade to the new version.When upgrading, run the installer as an administrator user.During the installation process, you will have the option to maintain the deployment settings from the previous version, or overwrite them in the new version.

Before upgradingBSA 8.2 to 8.6This section pertains to upgrading for BSA 8.2 to 8.6 only.

Before upgrading to BMC License Usage Collection Utility 2.0.00, BMC recommends that you delete any existing BSA deployments. Then after upgrading, add a new deployment for BSA 8.2 to 8.6 with the required information so that the database scripts can gather the BSA license usage.



IntegratingThe BMC License Usage Collection Utility 2.0.00 can integrate with the following BMC products to run :license usage reports

BMC product Supported versions

BMC Atrium Discovery and Dependency Mapping (ADDM)

8.3.2 to 10.2

BMC BladeLogic Database Automation (BDA) 8.3 to 8.7

BMC BladeLogic Network Automation (BNA) 8.3 to 8.7

BMC BladeLogic Server Automation (BSA) 8.2 to 8.6*

8.7

*See separate instructions in, , and Upgrading Configuring environment settings Adding

.deployments

BMC Client Management (BCM) 11.6 to 12.1.0

BMC Remedy AR System Server (ARS) 7.6.04 to 9

BMC TrueSight Capacity Optimization (TSCO) 10.5

Related topicsAdding deployments

https://docs.bmc.com/docs/display/LUCU/Reports



1.

Using the BMC License Usage Collection UtilityThis section provides information about using the BMC License Usage Collection Utility.

Accessing the BMC License Usage Collection UtilityGetting started with deployments and reportsManaging deploymentsReports

Accessing the BMC License Usage Collection UtilityThis topic describes how to access the BMC License Usage Collection Utility user interface.

From the menu, select > > Start All Programs BMC Software LicenseUsageCollector >

.Start LicenseUsageCollector

You can also navigate to C:\Program Files\BMC Software\LicenseUsageCollector\licenseusagecollector\startUI.bat.



1.

2.

1.

2.

3.

4.

Note

If the BMC License Usage Collection Utility was installed in the default path (C:\Program Files\BMC Software\LicenseUsageCollector), you should launch the utility using the Run

option:as Administrator

From the menu, select > > Start All Programs BMC Software

LicenseUsageCollector.

Right-click , then select .Start LicenseUsageCollector Run as Administrator

Tip

Local administrators can configure the utility shortcut to automatically run as an administrator. (The following does not apply to non-local administrators.)

To configure the shortcut:

From the menu or the desktop, right-click the Start Start

shortcut, select .LicenseUsageCollector Properties

On the tab of the Shortcut Start LicenseUsageCollector Properties

dialog box, click .Advanced

On the dialog box, select the Advanced Properties Run as

check box, then click .Administrator OK

Click to close the dialog OK Start LicenseUsageCollector Properties

box.

Related topicGetting started with deployments and reports

Quick tourAfter you have installed and configured the BMC License Usage Collection Utility, you can add deployments and run reports.

Click the screenshots below to walk through the steps. For detailed instructions, see Adding and .deployments Running reports



Adding a deployment

Running a report



Emailing a report



Scheduling a report



1.

2.

1.

2.

Managing deploymentsYou can add, edit, and delete deployments from the Manage Deployments tab. See the following topics for detailed instructions.

Adding deploymentsEditing deploymentsDeleting deployments

Adding deploymentsIn order to run license reports, the BMC product name must be listed in the Select Deployments list on the License Reports tab. If the product is not listed, follow the instructions below.

To add a deployment from the License Report tabThe License Report tab provides a link to the Management Deployment tab so you can add deployments.

Click the tab, then click .License Report Add Deployment

The opens.Manage Deployment tab

Follow the instructions below.

To add a deployment from the Manage Deployment tab

Click the tab, then click .Manage Deployment Add

Tip

If you do not see the button, you may be viewing the tab in edit mode. Click Add

and you should see the button.Cancel Add

In the list, select the BMC product, for example: BMC Remedy AR System Select Product

Server (ARS).

Complete the following steps for the respective products:

BMC Atrium Discovery and Dependency Mapping (ADDM) 8.3.2 to 10.2



1. a.

b.

c. d. e.

f.

g. h.

BMC Atrium Discovery and Dependency Mapping (ADDM)

In the section, in the list, select an option (for example, Enter Details Environment

or ).Production Pre-production

In the field, enter the server name where the ADDM web service is Server Name

hosted.In the field, enter the system user name.Server User

In the field, enter the password for the user specified above.Server Password

In the field, enter the password again.Server Confirm Password

In the list, Server Type WEBSRV is entered by default.In the field, the value entered in the Server Name field above will Report File Prefix

automatically appear, appended by "_1", for example: servername_1.You can edit the field value before saving the Manage Deployment tab.

Note

After the Manage Deployment tab is saved, the value Report File Prefix

becomes read only and cannot be changed.

In the Deployment Protocol list, select an option (HTTPS or HTTP).Click .Save

BMC BladeLogic Database Automation (BDA) 8.3 to 8.7



1. a.

b. c. d. e.

f.

g.

BMC BladeLogic Database Automation (BDA)



In the field, enter the server name where the BDA server is installed.Server Name

In the field, Server User enter the system user name.In the field, enter the password Server Password for the user specified above.In the field, enter the password again.Server Confirm Password

In the Server Type list, UNIX is entered by default. In the Report File Prefix field, the value entered in the Server Name field above will

automatically appear, appended by "_1", for example: servername_1. You can edit the field value before saving the Manage Deployment tab.

Note



Click Save .

BMC BladeLogic Network Automation (BNA) 8.3 to 8.7



1. a.

b.

c. d. e.

f.

g.

BMC BladeLogic Network Automation (BNA)



In the field, enter the server name where the BNA web service is Server Name

hosted.In the field, enter the web service user name.Server User



In the Server Type list, WEBSRV is entered by default. In the Report File Prefix field, the value entered in the Server Name field above will

automatically appear, appended by "_1", for example: servername_1. You can edit the field value before saving the Manage Deployment tab.

Note



Click .Save

BMC BladeLogic Server Automation (BSA) 8.2 to 8.6



BMC BladeLogic Server Automation (BSA) 8.2 to 8.6

Delete existing and add new BSA deployments for version 2.0.00

For BSA 8.2 to 8.6, before upgrading to BMC License Usage Collection Utility 2.0.00, BMC recommends that you delete any existing BSA deployments. Then after upgrading, add a new deployment for BSA 8.2 to 8.6 with the required information so that the database scripts can gather the BSA license usage.

Supported operating systems and database types/versions for BSA 8.2. to 8.6 license generation

Operating System Database type Database Version

Windows SQL Server 2008 R2

Windows Oracle 11 Release 2g

Unix Oracle 12c

Unix Oracle 11 Release 2g



1. a.

b. c. d. e. f.

g.

h. i.

j. i. ii.

k. l.

m. n.

In the section, in the list, select an option (for example: Enter Details Environment

).Pre-production

In the field, enter the BSA database server name.Server Name

In the field, enter the system user name.Server User



In the list, select the server type (Windows or UNIX). Server Type

In the field, the value entered in the Server Name field above will Report File Prefix


Note



In the list, select the server type (Oracle or SQL Server).Database Type

In the field, enter the SQL Server Database name or Database Name/Service Name

the Oracle Service name.In the field: Database Port

For an Oracle database, enter the port number.For a SQL Server database, NA automatically appears.

In the field, enter the Database user name.Database User

In the field, enter the password for the database user specified Database Password

above.In the field, enter the password again.Database Confirm Password

Click Save .

BMC BladeLogic Server Automation (BSA) 8.7



1. a.

b. c. d. e. f.

g.

h. i.

j. k.

l.

BMC BladeLogic Server Automation (BSA) 8.7


or Pre-production ).In the field, enter the server name where BSA is installed.Server Name

In the field, Server User enter the system user name.In the field, enter the password Server Password for the user specified above.In the field, enter the password again.Server Confirm Password

In the list, enter the server type (Windows or UNIX). Server Type



Note



In the field, enter the BladeLogic profile user name.Product User

In the field, enter the password for the BladeLogic user specified Product Password

above.In the field, enter the password again.Product Confirm Password

In the , enter a name for the profile.Profile Name field

This profile name will be used to gather information. Click Save .

BMC Client Management (BCM) 11.6 to 12.1.0



1. a.

b.

c. d. e. f.

g.

h.

BMC Client Management (BCM)



In the field, enter the server name where the BCM web service is Server Name

hosted.

Note

BCM accepts only the format in the Servername field.servername:port




In the list, WEBSRV is entered by default.Server Type



Note



In the list, select an option (HTTPS or HTTP).Deployment Protocol

Click Save .

BMC Remedy AR System Server (ARS) 7.6.04 to 9

http://servernameport/



1. a.

b. c. d. e. f.

g.

h.

BMC Remedy AR System Server (ARS)



In the field, enter the server name where the AR server is installed.Server Name


In the field, enter the password Server Password for the user specified above.In the field, enter the password again.Server Confirm Password

In the list, select the server type (Windows or UNIX).Server Type



Note



Click Save .




1. a.

b.

c. d. e. f.

g.

h. i.




In the field, enter the server name where the TSCO web service is Server Name

hosted.In the field, enter the system user name.Server User



In the list, WEBSRV is entered by default.Server Type

In the Report File Prefix field, the value entered in the Server Name field above will automatically appear, appended by "_1", for example: servername_1. You can edit the field value before saving the Manage Deployment tab.

Note



In the list, select an option (HTTPS or HTTP).Deployment Protocol

.Click Save

A confirmation message appears indicating that the deployment was saved or not.

In the grid, the Product Name, Server Name, and Validation Status appears.Deployments

The column displays the outcome of the deployment (Success or Failed). Validation Status

Note

If the validation fails, in the section, select the product name, in the Deployments Edit

section, re-enter the credentials, then click .Details Save

The deployments are validated for each user session, so each time the application is launched, the system validates the deployment details.



1. 2.

3. 4.

a. b.

c.

1. 2.

3. 4.

To edit a deployment

Click the tab.Manage Deployment

In the list, select the BMC product, for example: BMC Remedy AR System Deployments

Server (ARS).In the section, modify the fields using the information in .Edit Details Adding deploymentsWhen you are finished editing the details, click .Save

A confirmation message appears indicating that the deployment was saved or not.In the grid, the Product Name, Server Name, and Validation Status Deployments

appears.The column displays the outcome of the deployment (Success or Validation Status

Failed).

Note

The deployments are validated for each user session, so each time the application is launched, the system validates the deployment details.

To delete a deployment

Click the tab.Manage Deployment

In the list, select the BMC product, for example: BMC Remedy AR System Deployments

Server (ARS).Click .Delete

On the confirmation message, click .Yes

The deployment is removed from the list.Deployments

ReportsThe BMC License Usage Collection Utility enables you to view and email license usage reports for your BMC product deployments. Each license report is specific to each BMC product; therefore, the file format and contents vary depending on the product. Following is a report summary for each product deployment.

Product deployment Report contents summary

BMC Atrium Discovery and Dependency Mapping(ADDM)

Lists the discovered servers in the data center



1.

Product deployment Report contents summary

BMC Bladelogic Database Automation(BDA)

List of installed BDA agents managed by respective BDA managers

BMC BladeLogic Network Automation(BNA)

Number of online devices managed by BMC Network Automation

BMC Bladelogic Server Automation(BSA)

Information about active agent count and various manager modulesFor BSA version 8.7, two report files are created:

<DeploymentID>_ BSAv87License_details.csv<DeploymentID>_BSAv87License_summary.csv

BMC Client Management(BCM) Name—Displays the name of the license

The name can be either BMC Client Management for the basic license of the software, or the names of individually licensed modules, such as Remote Control

Count—Indicates for how many agents the basic license is valid

Available—Indicates the number of remaining licenses

Expiry date—Displays the expiration date if the license is a limited license, such as an evaluation license

Status—Displays whether the current License is valid, invalid, expiring, expired, or exceeded

BMC Remedy AR System Server (ARS) Maximum number of licenses that can be used concurrently (Currently Defined Limit)

Peak number of in-use floating licenses or assigned fixed licenses (Count)

BMC TrueSight Capacity Optimization(TSCO Audit count for overall number of managed systems and number of managed systems

imported from Capacity Agents

Related topicsRunning reports

Server clustering information in reports

Viewing reports

Emailing reports

To run a report

Click the tab. License Report



2.

3. a.

4.

5.

From the list, select a deployment (for example, BMC Remedy AR Select Deployments

System Server (ARS).To select multiple deployments, use your CTRL and Shift keys while selecting deployments.

Tip

To add more deployments to the list, see .Adding deployments

From the list, select a time (for example, Last Three Months).Duration

To select a custom time, select , then double-click to select the start date Custom

from the " " Calendar icon and the end date from the " " Calendar icon.From To

Note

The Duration option is not applicable for BNA, BDA, BCM, TSCO, and BSA 8.2 to 8.6 deployments, as noted in the tooltip on the icon.Information

Click .Run License Report

The box displays the real-time status messages while the Current License Report Run

report is running. "Process Finished" will appear once completed.To view the report, in the section, in the Previous License Report Details License Report

column, click the link.Click Here

The selected report opens in a CSV format for each product.

Note

Each time reports are run, they are stored in the folder where the user\Reports

License Utility is installed ($LicenseUsageCollectorHome\licenseusagecollector\user\Reports\timestamp folder).Folders containing the reports are named with the date and timestamp when the reports were run. For example, an ARS report generated on July 1, 2015 at 4:23 PM EDT, would appear in the following folder:$LicenseUsageCollectorHome\licenseusagecollector\user\

.Reports\Wed_150701_162314\ARS

Related topics

Viewing reports



Adding deployments

Server clustering information in reportsThe following provides details on the availability of server clustering information in BMC License

reports:Usage Collection Utility

Product

deployment

Notes on license reports containing consolidated licensing information for server clustering

BMC Atrium Discovery and Dependency Mapping(ADDM)

ADDM supports the notion of a clustered instance. The license report generated for a clustered instance of ADDM returns data for all members of the cluster. However, this ADDM cluster presents itself as a single logical instance of the product, so the licence report generated from a clustered instance of ADDM represents all the data in the cluster.

BMC Bladelogic Database Automation(BDA)

BDA supports server clustering. However, the license report contains separate licensing information for each of the servers in the cluster.

BMC BladeLogic Network Automation(BNA)

BNA does not support server clustering; the license report is for individual servers.

BMC Bladelogic Server Automation(BSA)

For BSA 8.7 and laterBSA has a server group concept; however, the licenses are extracted per Device ID. BMC License Usage

generates separate licensing information for each server.Collection Utility

For versions earlier than BSA 8.7reports do not contain consolidated licensing information for a server BMC License Usage Collection Utility

group.

BMC Client Management(BCM)

Not applicable – BCM does not support server clustering.

BMC Remedy AR System Server (ARS)

ARS supports server clustering. The servers in server groups use a shared database; therefore, license reports generated from this database contain consolidated licensing information.

BMC TrueSight Capacity Optimization (TSCO)

TSCO does not support server clustering; the license report is for individual servers.

Related topicsRunning reports



1.

2.

3.

Viewing reports

Emailing reports

Emailing reportsAfter reports are generated, you can email them as attachments from the License Report tab.

You can append a prefix to the file name, so that:

the license operation team can search for license report files received in the BMC mailbox that include the prefixes provided by customers.customers can easily find the license report zip file in their sent mailbox .

File names are formatted as follows: Prefix_TimestampDirName_LUCU.zip. The zip file contains the report in CSV and the native file format per product, such as XML or HTML. The emailed reports are also stored in the user\EmailReports folder where the License Utility is installed.

PrerequisitesAn email client be configured on computers where the License Utility is installed in order to use this feature. For supported email clients, see the Email client section in the topic.System requirements

To email reports:

On the tab, click the checkbox next to the report you want to email.License Report

You can select multiple reports at once.To append a prefix to the file name, in the text box, enter a Email Attachment File Prefix

prefix, for example: YourOrganizationName.The prefix can contain up to 15 characters except the following: | and \ / : * ? " < > .

Click .Email Reports

Your email client opens with a zip file of the report attachment, including the report name you specified along with a date/time stamp, in this format: Prefix_TimestampDirName_LUCU.zip.

Note

If an email client does not exist on the computer or the email client is not configured, a message appears.

By default, the following appears in the email message:

To: [email protected] can change the email recipient in your email client.

The following can be changed in the email message, but not in the License Utility application:



1.

Subject: BMC License Utility Reports.Message text: Please send this email to BMC Software.

To view reportsYou can view reports from the tab, or from the folder where the License Report user\Reports

License Utility is installed.

Note

Each time reports are run, they are stored in the folder where the user\Reports

License Utility is installed ($LicenseUsageCollectorHome\licenseusagecollector\user\Reports\timestamp folder).Folders containing the reports are named with the date and timestamp when the reports were run. For example, an ARS report generated on July 1, 2015 at 4:23 PM EDT, would appear in the following folder:$LicenseUsageCollectorHome\licenseusagecollector\user\

.Reports\Wed_150701_162314\ARS

Click the tab on the BMC License Usage Collector. License Report

The section provides the following summary of the last 10 Previous License Report Run

reports that were run, listed by execution date:Previous License Report Run section summary information

Execution DatesThe date and time the report was run

No. of Deployment in RunThe number of deployments included in the run, for example, 1 out of 4

Successful RunThe number of reports that successfully ran for the specific date/time

Failed RunThe number of reports that failed for the specific date/time



2.

3.

In the list, select a report.Previous License Report Run

The section provides the following detailed information Previous License Report Details

for each deployment in the report:Previous License Report Details section details

Product NameThe product name(s) in the report

ServerStatus

Success or FailedLicense Report

A link to the license reportLog Report

A link to the log reportIn the section, in the and Previous License Report Details License Report Log Report

columns, click the link.Click Here

The selected report opens in a format specific to the BMC product.

Scheduling reportsYou can schedule license usage reports to run at various intervals, such as daily, weekly, or monthly. The tab displays the deployments that have been set up on the Schedule Reports

tab. The section displays the details for Manage Deployment Scheduled Deployment Details

the scheduled reports.

If the scheduler service is running, it will gather license information for the deployments at their scheduled time. When a new deployment is scheduled for the first time, the following columns in the section are blank: , and Scheduled Deployment Details Last Run Time Start Date Used End

. After the scheduled reports are executed, this section is updated with the real-time Date Used

status for all fields. The scheduler.xml file is also updated. (The file is located in the following directory: C:\Program Files (x86)\BMC Software\LicenseUsageCollector\licenseusagecollector\user\repository.)



1. 2.

3. 4.

5. 6.

1.

2.

See also .Adding deployments

To schedule reports

Note

If the LUCService is stopped for any reason, scheduled reports will still run.Scheduled reports cannot be edited, but you can delete them.If you want to schedule reports to run for more than a year, you will need to set up the Duration from the Custom option on the License Report tab. See Running

.reports

Click the tab.Schedule Reports

From the list, select a deployment (for example, BMC Remedy AR Select Deployments

System Server (ARS).To select multiple deployments, use your CTRL and Shift keys while selecting deployments.From the list, select the recurrence (for example, Weekly).Schedule Frequency

In the field, enter the start date (for example, 03/09/2016).Start Time

To use the calendar, click the icon, then select the start date.Calendar

In the field, type or select the time from the up or down arrows.Time

Click .Schedule Report

The schedule is automatically saved. The details appear in the Scheduled Deployment Details section.

To delete a scheduled report

From the list, in the column for the deployment, Scheduled Deployment Details Action

click .Delete

On the message, click to delete.Delete Schedule Yes

The scheduled report is removed from the list.



© Copyright 2015–2016 BMC Software, Inc.

© Copyright 2015-2016 BladeLogic, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

Linux is the registered trademark of Linus Torvalds.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

UNIX is the registered trademark of The Open Group in the US and other countries. BMC Software Confidential.

The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation.

BMC Software Inc. 2103 CityWest Blvd, Houston TX 77042-2828, USA 713 918 8880 Customer Support: 800 537 1813 (United States and Canada) or contact your local support center.



Index

aadding deployments 31addm , , 20 31 41ars , , 20 31 41

bbcm , , , , 7 8 20 31 41bda , , 20 31 41bna , , 20 31 41bsa , , , , 7 8 20 31 41

cconfiguration 16contributor unapproved , , 7 8 9controller host 10credentials , , 7 8 9csv 31

ddefects 6deleting deployments 41deployments , , 7 8 9

eediting deployments 41email , , , 7 8 10 45enhancements , , 7 8 9environment , 16 20

f



failed 46fqdn 31

ggroup , 16 31

hhardware 10

iini 31installation , , , , , 7 8 9 10 12 12

jjava , , 7 8 9jre , , 7 8 9

kknown issues 6

llanguage 12linux 16localization 12log 46

ppassword , 16 31pcm 31permissions 16prerequisites 12



rreference 6reinstallation 12release notes , 6 6reports , , , 7 8 9 41

ssecurity 16server clustering 41size 10software 10specifications 10ssh , 12 16successful 46system requirements , 10 10

ttranslation 12truesight 31tsco 31

uui , , 7 8 9uninstallation 14unix , , , 12 16 16 31usage data 14user account 16user interface , , 7 8 9

vvc 31virtual center 31



wwebsrv 31windows , , , , , , 10 12 12 16 16 20 31windows server 2003 16wmi , , 12 16 16workarounds 6

bmc license usage collection utility 2.0...bmc license usage collection utility 2.0.00 bmc software...

Documents