Onboarding BMC Discovery

This topic describes a process for onboarding a connector for BMC Discovery. The process requires you to download and install a small program on your premises. Running as a service, the on-premise program is the connector that enables communication between SecOps Response and an instance of BMC Discovery. 

After onboarding, you can use SecOps Response and BMC Discovery to enable blind spot detection and filter vulnerability data on dashboards by application.

The following sections in this topic describe how to onboard the BMC Discovery connector.   

The following video demonstrates how to use SecOps Response to onboard a connector for BMC Discovery.


Before you begin

To set up a connector for BMC Discovery:

  • Confirm that a system connector for BMC BladeLogic Server Automation has already been installed. 
  • Confirm that the server running the Discovery connector meets the following minimum requirements:
      Page not found for multiexcerpt macro.
    The page: Minimum hardware and software requirements was not found. Please check/update the page name used in the 'multiexcerpt-include macro.


When onboarding connectors, a single machine cannot host more than one connector of the same type. For example, if you have onboarded a connector for Discovery on a host, you cannot successfully onboard another Discovery connector on the same machine.

To onboard a BMC Discovery connector

  1. Log on to SecOps Response as a SecOps Response administrator with your registered credentials.
  2. Click Add Connector.
    The Choose Connectors page opens. It lets you choose the connectors that interact with SecOps Response.
    Note that you cannot add an optional connector such as BMC Discovery without first adding a system connector for an endpoint manager such as BMC Server Automation. 
  3. On the Choose Connectors page, select BMC Discovery Connector.
  4. Click Download.
    The Download page opens. It presents the set of the connectors you have chosen.

  5. Download the connector by clicking on next to BMC Discovery Connector.zip.
    The connector is downloaded locally.
  6. Before installing the connector, ensure that Java 1.8 or later is running on the local environment.


    To check which version of Java is installed, use a command line and enter the following: java -version

  7. Using any standard compression tool, extract the BMC Discovery Connector.zip file to the location where you want to install the connector.
  8. Depending on the operating system, take one of the following actions:
    • (Windows) Perform the following steps:

      1. Using a command line, cd to the location of the extracted ZIP file contents.

      2. Install the connector by entering the command: discovery-connector.exe install

      3. Start the connector by entering the command: discovery-connector.exe start
        To stop the connector, enter the command: discovery-connector.exe stop

    • (Linux) Perform the following steps as the root user or using sudo:

      1. Cd to the location of the extracted ZIP file contents.

      2. Grant execute permissions to the install.sh file by entering the command: chmod +x install.sh

      3. Install the connector by running the command: ./install.sh file. 
        Grant execute permissions to the connector.sh file by entering the command: chmod +x connector.sh

      4. Start the connector by entering the command: systemctl start discovery-connector
        To stop the connector, enter the command: systemctl stop discovery-connector
        You may also want to run the command systemctl enable discovery-connector, which instructs the connector to start on reboot.

  9. Using the onboarding interface, click Configure.
    The Configure page asks for information needed to set up a connection to a connector. The information requested depends on which connector you are configuring. 
  10. Provide the following information for the BMC Discovery connector.


    If you have access to the BSA Application Server, you can obtain most of the following information by going to Configuration > Configuration Object Dictionary. Select Server Objects and then select Atrium Discovery in the list at left. The content panel at right provides Discovery connection information.

    ADDM Connection String

    URL for the Discovery instance, such as http://clm-aus-014680/ or

    ADDM PortPort number used to connect to the Discovery instance.
    ADDM User NameName of the Discovery user required to connect to the Discovery instance.
    ADDM PasswordPassword required to connect to the Discovery instance.
    ADDM Host Exclusion Pattern

    Comma-separated list of devices for which data should be filtered out. You can exclude individual IP addresses or host names. You can also mix host names and IP addresses. Special characters are not permitted in this list.

    Example IP address to exclude:

    Example of mixed formats:,,myserver1234.com

  11. Click Finish

Where to go from here 

Learn more about using BMC Discovery to detect blind spots and filter dashboard data by application.

Was this page helpful? Yes No Submitting... Thank you