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:  Remedy AR System Server (ARS).

Complete the following steps for the respective products:

BMC Discovery (Discovery) 8.3.2 to 11.1

Click here to expand...

 

Note

  • Ensure that the BMC Discovery environment is configured with HTTPS.
  • Only English characters, numerals and special characters are allowed.

  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 BMC Discovery web service is hosted.
  3. In the Server User field, enter the BMC Discovery application user name.
  4.  In the Server Password field, enter the password for the user specified in step 3.
  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 in step 2 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 Database Automation (BDA) 8.3 to 8.9.01

Click here to expand...

Note

Only English characters, numerals and special characters are allowed.

  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 in step 3.
  5. In the Server Confirm Password field, enter the password again.
    In the  Server Type list, UNIX is entered by default.       
  6. In the SSH Port field, enter the system SSH port (required for non-default) for the UNIX server.

  7. In the  Report File Prefix  field, the value entered in the Server Name field in step 2 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. Click Save.

BMC Network Automation (BNA) 8.3 to 8.9.01

Click here to expand...

 

Note

Only English characters, numerals and special characters are allowed.

  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 BNA application user name.
  4.  In the Server Password field, enter the password for the user specified in step 3.
  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 in step 2 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 Server Automation (BSA) 8.2 to 8.6

Click here to expand...

  • 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

  • Only English characters, numerals and special characters are allowed.

 

  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 machine name where the BSA database is installed.

  3. In the Server Type field, JDBC is entered by default.

    Note

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

  4. In the Database Type list, select the server type (Oracle or SQL Server).
  5. In the Database Name/Service Name field, enter the SQL Server Database name or the Oracle Service name.
  6. In the Database Port field, enter the Database listener port number.
  7. In the Database User field, enter the Database user name of the BSA Schema.
  8. In the Database Password field, enter the password for the database user specified in step 7.
  9. In the Database Confirm Password field, enter the password again.
  10. Click Save.

BMC Server Automation (BSA) 8.7 to 8.9

Click here to expand...

 

Note

Only English characters, numerals and special characters are allowed.

  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 Appserver is installed.

 

For a Windows server where the License Utility and BSA are installed on the same computer:

 

 

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. 

  1. Enter one of the following:  localhost, computer name, or full computer name (FQDN).
  2. For deployments to a remote server: In the Server User field, enter the system user name.  
  3. For a Windows server, enter the system user name in the format: Domain name\system username.  

  4.  In the Server Password field, enter the password for the user specified in step 2.

    Note

     The license utility supports only Secure Remote Password (SRP) authentication. 

     

  5. In the Server Confirm Password field, enter the password again.
  6. In the Server Type list, enter the server type (Windows or UNIX).
  7. In the SSH Port field, enter the system SSH port (required for non-default) for the UNIX server.

  8. In the Report File Prefix field, the value entered in the Server Name field in step 2 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 BSA profile user name.
  10. In the Product Password field, enter the password for the BSA user specified in step 9.
  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.

    Note

    The profile name for the BSA SRP authentication profile must not contain spaces. 

  13. Click Save.

BMC Client Management (BCM) 11.6 to 12.6

Click here to expand...

Note

English Characters, numeral and special characters are allowed for all fields. Additionally German input characters and numerals are allowed only for server username and password fields.

  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 BCM application user name.
  4.  In the Server Password field, enter the password for the user specified in step 3.
  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 in step 2 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.

BMC Performance Manager Portal (BPM Portal) 2.11 

Click here to expand...

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

  • Only English characters, numerals and special characters are allowed.
  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 in step 2.
  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 SSH Port field, enter the system SSH port (required for non-default) for the UNIX server.

  9. In the Report File Prefix field, the value entered in the Server Name field in step 2 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.

  10. In the Database Type list, Oracle appears by default.
  11. In the Database Name/Service Name field, enter the SQL Server Database name or the Oracle Service name.
  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 in step 12.
  14. In the Database Confirm Password field, enter the password again.
  15. Click Save.

BMC Release Package and Deployment (RPD) 4.8.00 to 5.0.02

Click here to expand...

 

Note

Only English characters, numerals and special characters are allowed.

  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 RPD web service is hosted.
  3. In the RPD User Token field, enter the RPD User token for authentication.
  4. In the Server Type list, WEBSRV is entered by default.

  5. In the Report File Prefix field, the value entered in the Server Name field in step 2 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.

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

BMC Release Process Management (RPM) 4.6.00 to 5.0.02

Click here to expand...

 

Note

Only English characters, numerals and special characters are allowed.

  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 RPM web service is hosted.
  3. In the RPM User Token field, enter the RPM Root Group User token.
  4. In the Server Type list, WEBSRV is entered by default.

  5. In the Report File Prefix field, the value entered in the Server Name field in step 2 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.

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

Remedy AR System Server (ARS) 7.6.04 to 9.1.02

Click here to expand...

 

Note

English Characters, numeral and special characters are allowed for all fields. Additionally German input characters and numerals are allowed only for server username and password fields.

  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 in step 2.
  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 SSH Port field, enter the system SSH port (required for non-default) for the UNIX server.

  9. In the Report File Prefix field, the value entered in the Server Name field in step 2 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.

  10. Click Save.

BMC Digital Workplace (MyIT) 3.1 to 3.3

Note

For version 3.3.02, the product name has been changed to BMC Digital Workplace.

Click here to expand...

 

Note

  • Only English characters, numerals and special characters are allowed.
  • The following operating systems and database types/versions are supported for BMC Digital Workplace (MyIT) 3.1 to 3.3:

Operating System

Database type

Database version

Windows

SQL Server

2008

Windows

SQL Server

2012

Windows

Oracle

Oracle 11g Release 2

Unix

Oracle

12c

  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 machine name where the BMC Digital Workplace database is installed.
  3. In the Server Type list, JDBC is entered by default.

  4. In the Report File Prefix field, the value entered in the Server Name field in step 2 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.

  5. In the Database Type list, select the server type (Oracle or SQL Server).
  6. In the Database Name/Service Name field, enter the SQL Server Database name or the Oracle Service name.
  7. In the Database Port field: Enter the Database Listener port number.
  8. In the Database User field, enter the Database user name of the BMC Digital Workplace Schema.
  9. In the Database Password field, enter the password for the database of the user specified in step 8.
  10. Click Save.

TrueSight Capacity Optimization (TSCO) 10.5 to 10.7

Click here to expand...

Note

Only English characters, numerals and special characters are allowed.

  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 TSCO application user name.
  4.  In the Server Password field, enter the password for the user specified in step 3.
  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 in step 2 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.

TrueSight Operations Management (TSOM) 10.7

Click here to expand...

Note

Only English characters, numerals and special characters are allowed.

  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 TSOM web service is hosted (TrueSight Presentation Server).

    Note

    If the TSOM Presentation Server is configured in HA mode, then the Server Name should refer to the Load balancer (HAProxy) server name and port.

  3. In the Server User field, enter the TSOM application user name.
  4.  In the Server Password field, enter the password for the user specified in step 3.
  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 in step 2 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.

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*