×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC License Usage Collection Utility 2.5.00 ... Using the BMC License Usage Collection Utility Managing deployments

Adding deployments

The License Usage Collection Utility supports two models for deployment:  1) The license utility installed on one computer and the BMC product installed on another and accessed remotely, or 2) The license utility installed on the same computer as the BMC product. For BSA, ARS, and BPM Portal, see instructions below for Windows servers where the license utility and the BMC product are installed on the same computer.

Note

In 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 tab

The License Report tab provides a link to the Management Deployment tab so you can add deployments.

  1. Click the License Report tab, then click Add Deployment.
    The Manage Deployment tab opens. 
  2. Follow the instructions below.

To add a deployment from the Manage Deployment tab

  1. Click the Manage Deployment tab, then click Add.

    Tip

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

     

  2. In the Select Product list, select the BMC product, for example: BMC Remedy AR System Server (ARS).

Complete the following steps for the respective products:

 

BMC Atrium Discovery and Dependency Mapping (ADDM)

    1. In the Enter Details section, in the Environment list, select an option (for example, Production or Pre-production).
    2. In the Server Name field, enter the server name where the ADDM web service is hosted.
    3. In the Server User field, enter the system user name.
    4.  In the Server Password field, enter the password for the user specified above.

    5. In the Server Confirm Password field, enter the password again.
       In the Server Type list, WEBSRV is entered by default.

    6. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

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

    8. Click Save.

BMC BladeLogic Database Automation (BDA)

    1. In the Enter Details section, in the Environment list, select an option (for example, Production or Pre-production).
    2. In the Server Name field, enter the server name where the BDA server is installed.
    3. In the Server User field, enter the system user name.
    4.  In the Server Password field, enter the password for the user specified above.

    5. In the Server Confirm Password field, enter the password again.
      In the  Server Type  list, UNIX is entered by default.       

    6. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

    7. Click Save .

BMC BladeLogic Network Automation (BNA)

    1. In the Enter Details section, in the Environment list, select an option (for example, Production or Pre-production).
    2. In the Server Name field, enter the server name where the BNA web service is hosted.
    3. In the Server User field, enter the web service user name.
    4.  In the Server Password field, enter the password for the user specified above.

    5. In the Server Confirm Password field, enter the password again.
      In the  Server Type  list, WEBSRV is entered by default.     

    6. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

       

    7. Click Save.

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.5.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

11g Release 2

Unix

Oracle

12c

Unix

Oracle

11g Release 2



    1. In the Enter Details section, in the Environment list, select an option (for example, or Pre-production ).

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

    3. For a Windows server where the License Utility and BSA are installed on the same computer, enter one of the following: localhost, computer name, or full computer name (FQDN).

      Note

      Connection using an IP address is not supported. 


      The following fields are disabled and automatically appear with "NA": Server User, Server Password, Server Confirm Password, and Server Type (Windows).
      These are not required since the product and license utility are on the same computer. 

    4. For deployments to a remote server: In the  Server User  field, enter the system user name.
      For a Windows server, enter the system user name in the format: Domain name\system username.  

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

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

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

    8. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

       

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

    10. In the Database Name/Service Name field, enter the SQL Server Database name or the Oracle Service name.
    11. In the Database Port field:
      1. For an Oracle database, enter the port number.
      2. For a SQL Server database, NA automatically appears.

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

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

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

    15. Click Save .  

BMC BladeLogic Server Automation (BSA)  8.7

    1. In the Enter Details section, in the Environment list, select an option (for example, or Pre-production ).

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

    3. For a Windows server where the License Utility and BSA are installed on the same computer, enter one of the following: localhost, computer name, or full computer name (FQDN).

      Note

      Connection using an IP address is not supported. 


      The following fields are disabled and automatically appear with "NA": Server User, Server Password, Server Confirm Password, and Server Type (Windows).
      These are not required since the product and license utility are on the same computer.
       

    4. For deployments to a remote server: In the  Server User  field, enter the system user name.
      For a Windows server, enter the system user name in the format: Domain name\system username.  

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

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

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

    8. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

       

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

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

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

    12. In the  Profile Name field , enter a name for the profile.
       This profile name will be used to gather information.

    13. Click Save .

BMC Client Management (BCM)

    1. In the Enter Details section, in the Environment list, select an option (for example, Production or Pre-production).

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

      Note

      BCM accepts only the servername:port format in the Servername field.
    3. In the Server User field, enter the system user name.
    4.  In the Server Password field, enter the password for the user specified above.
    5. In the Server Confirm Password field, enter the password again.

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

    7. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

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

      Click Save .

BMC Performance Manager Portal (BPM Portal) 2.11 

Note

Supported operating systems and database types/versions for BPM 2.11 license generation  

Operating system

Database type

Database version

Windows

Oracle

11.2.0

Unix

Oracle

11.2.0

    1. In the Enter Details section, in the Environment list, select an option (for example, or Pre-production ).

    2. In the Server Name field, enter the server name where the BPM Portal database is installed.

    3. For a Windows server where the License Utility and BPM Portal are installed on the same computer, enter one of the following: localhost, computer name, or full computer name (FQDN).

      Note

      Connection using an IP address is not supported. 


      The following fields are disabled and automatically appear with "NA": Server User, Server Password, Server Confirm Password, and Server Type (Windows).
      These are not required since the product and license utility are on the same computer. 

    4. For deployments to a remote server: In the  Server User  field, enter the system user name.
      For a Windows server, enter the system user name in the format: Domain name\system username.  

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

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

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

    8. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

       

    9. In the Database Type list, Oracle appears by default.

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

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

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

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

    14. Click Save .

BMC Remedy AR System Server (ARS)

    1. In the Enter Details section, in the Environment list, select an option (for example, Production or Pre-production).
    2. In the Server Name field, enter the server name where the AR server is installed.
      1. For a Windows server, enter the system user name in the format: Domain name\system username.

    3. For a Windows server where the License Utility and ARS are installed on the same computer, enter one of the following: localhost, computer name, or full computer name (FQDN).

      Note

      Connection using an IP address is not supported. 


      The following fields are disabled and automatically appear with "NA": Server User, Server Password, Server Confirm Password, and Server Type (Windows).
      These are not required since the product and license utility are on the same computer. 

    4. For deployments to a remote server: In the  Server User  field, enter the system user name.
      For a Windows server, enter the system user name in the format: Domain name\system username.  

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

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

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

    8. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

    9. Click Save .

BMC TrueSight Capacity Optimization (TSCO) 10.5

    1. In the Enter Details section, in the Environment list, select an option (for example, Production or Pre-production).

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

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

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

    7. 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

      After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot be changed.

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

    9. Click Save.


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

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

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

Note

If the validation fails, in the Deployments section, select the product name, in the Edit Details section, re-enter the credentials, then click Save.

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

 


Was this page helpful? Yes No Submitting... Thank you
Last modified by Gina Fevrier on Jul 20, 2016
adding_deployments addm bda bna bsa ars unix websrv pcm ini csv group virtual_center vc fqdn password windows bcm tsco truesight

Comments

Log in or register to comment.

Managing deployments
Adding deployments (with PATROL)
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.