Setting up BMC Discovery


 BMC Discovery is required to support the Dynamic Service Model that is used in the following products:

  • BMC Helix Operations Management
  • BMC Helix AIOps
  • BMC Helix Continuous Optimization


Important

  • In BMC Helix Operations Management and  BMC Helix AIOps, the Dynamic Service Model is used for the BMC Helix Intelligent Integrations features. To leverage the BMC Helix AIOps capabilities, procure an add-on BMC Helix AIOps license with BMC Helix Operations Management.
  • A BMC Discovery appliance is optional if you are deploying only BMC Helix Continuous Optimization. 

If you do not have a separate BMC Discovery license, you cannot use the following BMC Discovery capabilities:

  • Native discovery capabilities
  • Dependency Mapping Content including the out-of-the-box Technology Knowledge Updates


To install BMC Discovery , see Installing the virtual appliance.

Related topics

To set up BMC Discovery

Perform the following actions after you deploy 

BMC Discovery

:

  1. Log on to the BMC Discovery URL. 
    The default username is system and the default password is system.
  2. On the Change password screen, set the following three passwords and note them down:

    Example
    Smart Appliance URL
    Username / password : system / myP4sswd#

    tideway login
    ssh login : tideway / myP4sswd%

    Root login
    su root
    password: myP4sswd$
  3. Set the hostname.
    For more information, see The netadmin user.

    su - netadmin
    [root@dhcp-10-128-127-93 tideway]# su - netadmin

    ADDM Appliance Network Administration Shell
    -------------------------------------------

     G  Configure General Settings
     I  Configure Network Interfaces
     P  Change netadmin password
     R  Exit & Reboot the appliance
     Q  Exit *without* rebooting

    Select option: G

    Configure General Settings
    --------------------------

     H  Change Hostname: localhost.localdomain
     G  Change Gateway: None
     D  Discard changes
     C  Commit changes
     Q  Return to the Main menu

    Select option: H
    Hostname or FQDN [localhost.localdomain] : <hostname>

    Configure General Settings
    --------------------------

     H  Change Hostname: <hostname> [CHANGED]
     G  Change Gateway: None
     D  Discard changes
     C  Commit changes
     Q  Return to the Main menu

    Select option: C
    Are you sure [n] ? y

    Configure General Settings
    --------------------------

     H  Change Hostname: <hostname>
     G  Change Gateway: None
     D  Discard changes
     C  Commit changes
     Q  Return to the Main menu

    Select option: Q

    ADDM Appliance Network Administration Shell
    -------------------------------------------

     G  Configure General Settings
     I  Configure Network Interfaces
     P  Change netadmin password
     R  Exit & Reboot the appliance
     Q  Exit *without* rebooting

    Select option: R
  4. Create a DNS alias for the URL created for BMC Discovery with the IP of the BMC Discovery machine.
    For example, acme-disc-private-poc.lab.bmc.com
    Make sure that the format of the URL is as shown in the example.

    The DNS is derived from the the COMPANY, TENANT_TYPE, ENVIRONMENT, and DOMAIN parameters from the helix-on-prem-deployment-manager/ configs/infra.config  file.
    For more information, see Configuration-file-settings.

  5. Apply the Technology Knowledge Updates (TKU). For more information, see Knowledge management (for BMC Discovery appliance).


Important

After deploying BMC Discovery make sure that you disconnect it from an existing BMC Helix Single Sign-on . If BMC Discovery is connected to an LDAP, make sure that it is removed from the protocol.

This is because during the BMC Helix Operations Management installation, a new BMC Helix Single Sign-on service is deployed. The installer connects BMC Discovery to the new service.

After BMC Helix Operations Management is deployed, you can add BMC Discovery back into the LDAP manually.

To import the CA-bundle for BMC Discovery

If you want to deploy BMC Helix IT Operations Management with custom CA certificates, you must import the CA-bundle for BMC Discovery. 

  1. Log on to BMC Discovery. 
  2. From the main menu, click Administration admin_icon.png.
  3. In the Security section, select Single Sign On.
    SSO_23.1.02.png
  4. On the Web Authentication: Helix SSO page, scroll down to the Trusted CA section.
  5. Click Choose file, upload the CA certificate, and then click Update CA Bundle.SSO_TrustedCA_23.1.02.png

    The following message is displayed: CA Bundle uploaded.

To configure the smart-graph-tenant-config configmap for BMC Discovery

If you want to deploy BMC Helix IT Operations Management with custom CA certificates, you must add the BMC Discovery mapping details in the smart-graph-tenant-config configmap :

  1. In the deployment namespace, run the following command to view the smart-graph-tenant-config configmap:

    kubectl -n <namespace> get cm smart-graph-tenant-config -o yaml

  2. Run the following command to edit the smart-graph-tenant-config configmap:

    kubectl -n <namespace> edit cm smart-graph-tenant-config -o yaml

  3. Add the tenant name, address, username and password.
    Example:

    apiVersion: v1
    data:
      tenants.yaml: |
        acmeonprembhompsr:
          address: acmeonprembhompsr-disc-private-poc.aus-ranchpdvm.bmc.com
          username: "system"
          password: "bmcAdm1n$"

    Enclose both username and password within double quotation marks.

    Do not begin the password with '@'.

  4. Save the .yaml file.


 

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