×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC License Usage Collection Utility 4.6 Configuring product servers

Configuring environment settings

This topic was edited by a BMC Contributor and has not been approved.  More information.

The following instructions describe how to configure BMC product servers to prepare for adding deployments to connect to the license utility.

Note

Configuration is not required for:

  • BMC Digital Workplace (MyIT) 3.1 to 3.3
  • BMC Network Automation (BNA)
  • BMC Release Package and Deployment (RPD)

Configuring BMC Digital Workplace (MyIT) 3.4 to 18.08 

  • Specify the user for the BMC Digital Workplace application with the administrator / super administrator role.

Configuring BMC Discovery (Discovery) 

  • Ensure that the BMC Discovery environment is configured with HTTPS.
  • Ensure that the BMC Discovery credentials have administrative rights to collect the BMC Discovery license information.
  • For BMC Discovery version 11.1, users need to have API access permission to query and get data.
  • For BMC Discovery versions 11.2x and later, enter the user with Rest API and license data permission over HTTPS.  Do not use the system user.

Configuring BMC Database Automation (BDA) 

UNIX

  1. Ensure that the SSHD process is running on the respective port.

Note

BDA license gathering is supported only for the root user.

Configuring BMC Server Automation (BSA 8.2 to 8.6)

  • Beginning with BMC License Usage Collection Utility 4.0.00, we are using the JDBC approach.
  • The database user should be the normal user with Read/Write permissions to the Database schema. 

Configuring BMC Server Automation (BSA 8.7 to 8.9.02) / TrueSight Server Automation 8.9.03  

Note

  • For BSA 8.7 Windows and UNIX: The “Profile User” must be assigned to the “BLAdmins” role.
  • For version 8.9.03, the product name has been changed to TrueSight Server Automation.

Windows and UNIX

Identify the servers where BMC Server Automation (BSA) Appserver is installed. 

Windows

Ensure that the NSH folder is in the system path. 

UNIX

Ensure that the SSHD process is running on the respective port.

Configuring BMC Client Management (BCM) 

Ensure that the BCM credentials have administrative rights to collect the BCM License information.

Configuring BMC Performance Manager Portal (BPM Portal v2.11) 

Windows and UNIX

  1. For UNIX, ensure that the SSHD process is running on the respective port.
  2. Identify the servers where the BMC Performance Manager Portal database is installed.
  3. Ensure that, on the Oracle database server, either the ORACLE_BASE or the DATASTORE_HOME environment variable is set.
    The License Utility will check for these two environment variables.
  4. Store the value in the PORTAL_PATH variable to refer it to the PORTAL_PATH\utility\BPM_Datastore_Utility.

Note

In Windows the user should belong to the group ora_dba. In Unix it is group dba.

Windows

Ensure that the "ORACLE_BASE or DATASTORE_HOME " environment variable is set for the logged-in user (Server user field value) on that server.

UNIX

  1. Ensure that the "ORACLE_BASE or DATASTORE_HOME " environment variable is set in the “. profile” file for the logged-in user (Server user field value) on that server.
  2. Make sure one of the following files has the execute permission:
    1. $ORACLE_BASE/utility/BPM_Datastore_Utility/DatastoreCliBMCPDS.sh
    2. $ DATASTORE_HOME/utility/BPM_Datastore_Utility/DatastoreCliBMCPDS.sh 
  3. If not, assign the permission (as per the screenshot) using the following command: chmod +x DatastoreCliBMCPDS.sh.

Configuring BMC Release Process Management (RPM)

The user must be in the "Root" group to have access to the v1 API.

Configuring Remedy AR System Server (ARS) based products

Windows

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

UNIX

  1. Ensure that the SSHD process is running on the respective port.
  2. Ensure that 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
  3. Ensure that the non-root user as read access permission for the $BMC_AR_SYSTEM_HOME/db/LicenseReport.txt file.
  4. If the BMC_AR_SYSTEM_HOME variable is not set:
    1. Log in to the Unix machine with the user name and credentials used in the "Server User" and "Server password" fields on the License Utility UI while adding the deployment.
    2. Copy the script from location:"<LU_Install_Directory>/licenseusagecollector/EnvVariableScripts" to the Unix machine.

    3. Give execute permission to the script using chmod +x <scriptname>.

    4. Execute the script.

Configuring TrueSight Operations Management (TSOM) 10.7 to 11.3.01

Only super and tenant administrator credentials are required to collect the TSOM license information.

Configuring TrueSight Capacity Optimization (TSCO) 10.7 to 11.3.01

  1. Log in to the TSCO console. 
  2. Enter the server name from Administration >COMPONENTS > Backend Services > API Providers - Data service.
    1.  Alternatively you can obtain your server name from the following path: Administration >COMPONENTS > Backend Services > API Providers - Data service).

For example: The API is exposed through a REST interface available at the following address:
https://xyz-tdr-abc.efg.com:8280/dh-services/data


Was this page helpful? Yes No Submitting... Thank you
Last modified by Gina Fevrier on Sep 10, 2018
environment bna addm bsa ars bda windows bcm contributor_unapproved

Comments

Log in or register to comment.

Configuring user settings
Administering deployments
© 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.