Configuring environment settings

Follow the links below to configure BMC product servers.

Note

Configuration is not required for:

  • BMC Client Management (BCM)
  • BMC Network Automation (BNA)
  • BMC Release Package and Deployment (RPD)
  • BMC TrueSight Capacity Optimization (TSCO)

BMC Atrium Discovery and Dependency Mapping (ADDM)

Click here to expand...

Ensure that the ADDM environment is configured with HTTPS.

Configuring BMC Bladelogic Database Automation (BDA) systems

Click here to expand...

UNIX

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

Click here to expand...

 

  1. Identify the servers where the BMC BladeLogic Server Automation (BSA 8.2 to 8.6) database is installed. 
  2. 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.

Windows

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

UNIX

 Ensure 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 to 8.9) systems 

Click here to expand...
Note

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

Windows and UNIX

Identify the servers where BMC BladeLogic 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 standard ports.

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

Click here to expand...

Windows and UNIX

  1. Identify the servers where the BMC Performance Manager Portal database is installed.
  2. Ensure that on the Oracle database server machine, either the ORACLE_BASE or the DATASTORE_HOME environment variable is set.
    The License Utility will check for these two environment variables.
  3. 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)

Click here to expand...

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

Configuring BMC Remedy AR System Server (ARS) based products

Click here to expand...

Windows

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

UNIX

Verify each of the following:

  1. The SSHD process is running on standard ports.
  2. The user whose credentials are being used by the License Utility to connect to this server:
    1. 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. The $BMC_AR_SYSTEM_HOME/db/LicenseReport.txt file has read access permission for the non-root user.

 

 

 

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