Adding domain names to the servers in BMC Server Automation

This topic provides information about adding domain names to the servers in BMC Server Automation. This procedure must be done on the computer where BMC Server Automation Application Server is installed and the same computer must have BMC Server Automation Console installed. Perform the following procedure to specify the FQDN (Fully-Qualified Domain Name) values for the servers in BMC Server Automation in the DNS_DOMAIN_NAME property.

Note

Before you start, verify that your RBAC role has BLAdmins or equivalent authorizations. Additionally, acquire a session credential for the authentication profile that connects with the BMC Server Automation Application Server.

Creating the NSH Script Job

  1. Copy the following files:
    • addServerProperty.nsh
    • getDetailsOfMachineAndAddProperty.nsh
    • getWindowsMachineFQDNName.bat
       from

      <BMC BladeLogic Atrium Integration installation folder>\NSHScripts
       to

      <BMC Server Automation installation folder>
      • (Windows) The default BMC Server Automation folder is C:\Program Files\BMC Software\BladeLogic\NSH
      • (Linux) The default BMC Server Automation folder is /opt/bmc/bladelogic/NSH
  2. Open a Windows command prompt or a Shell.
  3. Browse to the BMC Server Automation installation folder.
  4. Type nsh and press Enter.

  5. Set the BL_AUTH_PROFILE_NAME environment variable to your user profile by using the following command from the NSH command prompt: 

    {{export BL_AUTH_PROFILE_NAME= profileName}}
  6. Set the BL_RBAC_ROLE environment variable to your role. by using the following command from the NSH prompt:
{{export BL_RBAC_ROLE=roleName}}

roleName should be BLAdmins or its equivalent.

Best practice: Run a simple blcli command, such as Server listAllServers, to verify that the credentials are working properly.
 For more information, see the Setting-up-a-Network-Shell-client-to-run-in-proxy-mode.

Running the NSH Script Job

  1. Use the following command to execute the addServerProperty.nsh script: 

    {{nsh addServerProperty.nsh}}

     
    This creates an NSH Script named ADDM in the ADDMNSHSCRIPTS folder inside the Depot workspace in the BladeLogic console.
    Another NSH Script Job, ADDM_NSHSCRIPT_JOB is created in the ADDM_NSHSCRIPT_JOB folder in the Jobs workspace.

  2. Execute the ADDM_NSHSCRIPT_JOB NSH Script Job on all the enrolled servers on which you want to populate the DNS_DOMAIN_NAME server property.

  3. After you execute the job, the DNS_DOMAIN_NAME property for the target servers is populated with the appropriate value (the FQDN of the target). 

    Note

    • The NSH Script Job must be scheduled to run before every run of ETL to make sure that the DNS_DOMAIN_NAME server property is populated for any new servers that are added.
    • The DNS_DOMAIN_NAME server property must be set to Used in Reports in the Property Dictionary.
    • If the NSH Script Job is not run, no data is transferred to the CMDB.
    • If you want to rerun the scripts, delete ADDMNSHSCRIPTS from the Depot group and ADDM_NSHSCRIPT_JOB from the Job group.
    • Map the BMC Atrium CMDB Domain attribute to the BMC Server Automation DNS_DOMAIN_NAME attribute in the BladeLogic to Atrium Customization (see Customizing-data-mappings-between-BMC-Server-Automation-and-BMC-Atrium-CMDB for more details), before you restart the BMC Atrium Integration Engine service.

 

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