Entuity Device Synchronization with BPPM or TSIM using Direct Publishing v3.0

Version 6
    Share This:

    *Updated 9/25/2015* - includes support for Entuity v15.5, cool custom icons and minor fixes. Multi-server support.

    Summary of Integration:

    This is a BMC Communities provided and BMC Communities supported integration. The purpose of this integration is to populate TrueSight Infrastructure Manager (TSIM) or BMC ProactiveNet Performance Manager directly with Entuity device and optionally relationship/dependency (Layer-2 and Layer-3) data using Direct Publishing. Service Models and topology models can be represented regardless whether the Atrium CMDB is integrated with BPPM or not.The value is of this integration would be the following:

    • Event Management - event enrichment with "meta" data of devices managed from Entuity (Manufacturer, Model, Version, Location, ...)
    • Topology - provide the Manager of Manager (TSIM/BPPM) visibility into interconnected devices. Quickly answer the question - "What is connected to this device?"
    • Service Impact Management - by default Edge Switches to servers have Impacts enabled. You can use the topology for Downstream Correlation Use Cases.

    The following diagram shows the data flow from Entuity to BPPM or TSIM:

    ENM Direct Publishing Flowv.png

    The base event integration provided out of the box with BPPM +9.5 and TSIM v10. The integration relies on IIWS to integrate. You may need to modify the MRL to add refine rule to build alias format based on BMC_ComputerSystem:<hostname>. I will post that MRL change to the integration.

    So let's take a different approach to getting to an end-state ...


    5 Steps to the integration:

    Step 1 – Enable Direct Publish Publishing on BPPM or TSIM server

    Step 2 – Create Publishing Environment on BPPM Server

                    penv open -e ENTUITY -p OriginId=DirectPublish -p HomeCell= cellName

    Step 3 – Install and Configure Pentaho for ETL automation

    –SFTP or SCP the updated sw_data_export_def_atrium.cfg file to the Entuity server

    Re-run ./configure on the Entuity server to enable AtriumExport (*Atrium CMDB is NOT required for this integration. We are just enabling the default export to Data Warehouse)

    Download Pentaho CE (SourceForge) – local to BPPM Server

    Extract Entuity ETL files (KJB / KTR)

    Configure Variables for ETL and Input Step for Entuity SQL DB. Here is a screenshot of the Input Connection string:

    MySQL DB Input Step.png

    Step 4 – Run ETL and Validate Device Synchronization

    Here is a screenshot of BPPM Admin Console with Component Data Tables updated with Entuity Inventory data:

    BPPM Admin Console - Component Table.png

    Here is a screenshot of the BPPM Ops Console with a device or CI and an associated Entuity event:


    Step 5 – *Optional – Synchronize Layer-2 and Layer-3 Topology Relationships

    Here is a screenshot of the TSIM / BPPM Ops Console with Layer-2 and Layer-3 relationships. Default configuration is that ALL network device to network device (Switch --> Switch, Router --> Switch ...) relationships are configured as a Inactive Impact Relationships. Any Edge Switch to Servers, for example, is set to DIRECT and Active. You can configure and enable impacts and PropagationModel (DIRECT, DECREASING, JUST_WARNING, JUST_INFO ..):


    *Note - the ETL queries all the interface to interface or port to port connections, and summarizes all the connections to a single relationship. One value point is that BPPM can provide dynamic views of Entuity managed devices. A user can use the Find CI search in the BPPM Ops Console and quickly understand what network devices are connected to the CI (as seen above).

    FAQs (Frequently Asked Questions):

    1.What is the ETL engine? Do I need to purchase any additional software?

    Pentaho Data Integration Communities Edition is free of charge and is used as the ETL engine to extract, transform and load data. Download PDI from Sourceforge:


    2.How does the ETL connect to Entuity?

    The input step for Inventory and L2/L3 Relationships will connect to the Entuity data warehouse database (AtriumExport) using JDBC (SQL query). You will need to setup the dataware house database and a user which the ETL will leverage  for connection. See the integration documentation for details. Also, you will need to configure the Input Step and configure the Connection to the MySQL database (JDBC) or in Entuity +v15 MariaDB  for the following transformations: (you can edit these directly in the Spoon client)

    • Entuity_TrueSight_Integration_PPOSTER_BAROC.ktr
    • Entuity_TrueSight_Integration_PPOSTER_BAROC_Relationships.ktr

    3.How does the ETL handle changes (deltas)?

    As part of the ETL, the Relationships transformation will delete all the existing Entuity relationships in BPPM and then rebuild every time the ETL is  run. The ETL is very fast so there is no issue with rebuilding relationships every time the ETL is run (sheduled on a daily basis). This will keep the relationships current and prevent stale relationships. The Inventory ETL only adds new devices (ETL does not remove devices – manual step required).

    4.How do I delete a device with Direct Publishing?

    Since the ETL does not remove devices, you just need the mc_udid of the device and create a baroc file. See documentation Appendix on details.  More info on pposter from BMC Docs:


    5.How do I remove all CIs and Relationships from the integrations?

    If you want to reset or remove all CIs from then run munpublish from the BPPM server:

          munpublish -n <cell> "DirectPublish.ENTUITY"

    6.How do I remove the integration or the Direct Publishing environment?

    If you want to remove the DirectPublish.ENTUITY environment, then from the BPPM Server:

          penv close -e ENTUITY -p "OriginId=DirectPublish" -p "HomeCell=<cellName>"

    Integration Requirements:

    The following are required for this integration:

    • Pentaho PDI - Kettle (Open Source ETL)
    • Java SE (JRE) – no specific version required
    • BPPM +9.0, +9.5, 10 (TSIM)
    • Entuity +v10, *Separate ETL for v15.5
    • MySQL (or MariaDB) User to query Data Warehouse Tables

    Integration LoE:

    This integration will take about 20 minutes to setup. The ETLs can be scheduled and run on a nightly basis. See the attached PPT presentation (PDF file) and goto Appendix for details on how to schedule the ETL.

    Getting Started:

    Please review the following before starting the integration:

    1. TrueSight OM - Entuity Device Synch via Direct Publishing v1.0b (PPT presentation)
    2. Entuity_Device_Synch_with_BPPM_and_TSOM_Install_v1_0b (Install/Config documentation)

    Other related links and videos:

    With the relationships synched to BPPM/TSIM, you could start to do Downstream Correlation Use Cases. Here is a short 8 min Demo video on Downstream Correlation Use Case with TrueSight Operations Manager or BPPM:

    Dynamic Downstream Correlation with BMC TrueSight Operations Manager on Vimeo


    Integration Feedback:

    Please provide any feedback on the comments section below. Also, if you have any enhancements or ideas that you can contribute or list, that would be appreciated. Enjoy and keep Communities a sharing environment!


    Other Notes:

    If you have the VSM KM running and have setup the VSM KM Device Synch integration with BPPM: Automatically Create Virtual Topology using VSM KM and Direct Publishing with Simple Service Model Support - WINDOWS version then you can now "reason" between the EdgeSwitch (discovered by Entuity) and the hypervisor (ESXi Host) discovered from the VSM KM via vCenter. The integration ETL can be found on the VSM KM integration link above (and the ETL has been posted below). Here is a screenshot of connecting the 2 topologies:


    Validation of connectivity: Here is a screenshot of a vSphere client, which is showing the properties of the ESXi NIC or adapter and its uplink connection to a Cisco EdgeSwith:


    Note: the ETL does support vSwitch to VM connectivity. By default the ETL only connects EdgeSwitch to physical Host (ESXi).


    Next version:

    - WHAT do you want? Please let us know.