Service Graph Connector for Jamf

  • Release version: Washingtondc
  • Updated May 30, 2025
  • 4 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Service Graph Connector for Jamf

    The Service Graph Connector for Jamf allows you to import data from Jamf into your ServiceNow instance, specifically into the Configuration Management Database (CMDB). This integration enables tracking of computers, disks, networks, and software applications, facilitating better asset management and compliance.

    Show full answer Show less

    Key Features

    • Supported Versions: Compatible with Jamf API v2.1.0, Jamf Pro API 10.28.0, and ServiceNow versions Washington DC, Xanadu, and Yokohama.
    • Use Cases:
      • IT Operations Management (ITOM): Detailed hardware and software inventory tracking for macOS, iPhones, and iPads.
      • Software Asset Management (SAM): Software package tracking, license reclamation, and usage monitoring.
      • IT Service Management (ITSM): Management of incidents, problems, and changes related to discovered configuration items.
    • Data Mapping: Utilizes the Robust Transform Engine (RTE) and Identification and Reconciliation Engine (IRE) to map and insert data into the CMDB.
    • Delta Data Synchronization: Allows for periodic updates from Jamf, enabling efficient data management.

    Key Outcomes

    By implementing the Service Graph Connector for Jamf, organizations can achieve:

    • Improved visibility and tracking of IT assets across macOS and mobile devices.
    • Enhanced compliance tracking and data accuracy through duplicate detection.
    • Streamlined management of software licenses and usage, supporting better financial decision-making.
    • Centralized monitoring of integration status and processing results through the CMDB integrations dashboard.

    For configuration, use the SGC Central view in the CMDB Workspace for a guided setup, as the older methods are being phased out.

    Use the Service Graph Connector for Jamf to pull data from Jamf into your ServiceNow instance.

    The Service Graph Connector for Jamf pulls data from computers, disks, networks, and software applications into the ServiceNow® Configuration Management Database (CMDB) application.

    Request apps on the Store

    Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

    Supported versions

    • Supported versions:
      • Jamf API v2.1.0
      • Jamf Pro API 10.28.0
      • Jamf Pro 10.35.0
    • Supported ServiceNow versions:
      • Washington DC
      • Xanadu
      • Yokohama

    Use cases

    The following are examples on how you can use the Service Graph Connector for different ServiceNow® applications:
    • IT Operations Management (ITOM) Visibility
      • Detailed hardware and software inventory tracking for macOS hardware and apps. The tracking can be done with or without Software Asset Management (SAM).
      • Detailed hardware and software inventory tracking for hardware and apps for both iPhones and iPads. The tracking can be done with or without Software Asset Management (SAM).
      • Compliance tracking for mobile devices and end-user computers.
      • Duplicate data detection on imports to improve performance of nightly imports.
    • Software Asset Management (SAM) and IT Asset Management (ITAM)
      • Software package and installation tracking.
      • License reclamation by detecting removed software.
      • Software Usage tracking.
    • IT Service Management (ITSM)
      • Incidents, problems, and changes on discovered configuration items (CI).
      • Automatic ownership assignment based on top users.

    Configuring a connection for the connector

    You can configure a connection for the connector by using the SGC Central view in the CMDB Workspace. The view enables you to discover and install connectors, and then effectively manage the full life cycle of creating, editing, monitoring, and debugging connections. To configure the connector using SGC Central, see Configure Service Graph Connector for Jamf using SGC Central.
    Important:
    Unless there are configuration issues, use the SGC Central view in the CMDB Workspace to configure the connection for the connector, as the guided setup method is being deprecated.

    CMDB integrations dashboard

    The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed integrations. You can see metrics for all integration runs. You can filter the view to a specific CMDB integration, a specific time duration, or a specific integration run. For more details about monitoring Jamf integrations in the CMDB Integrations Dashboard, see Using the CMDB Integrations Dashboard.

    Data mapping

    Data from the Jamf data source is mapped and transformed into the ServiceNow CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the ServiceNow CMDB using the Identification and Reconciliation Engine (IRE).

    When you complete setting up the connection, you can configure the integration to periodically pull data from Jamf.

    The delta data synchronization feature is available in Jamf version 2.14 and higher. You can configure the is_delta_enabled_for_computers and is_delta_enabled_for_mobiles connection properties for synchronizing only delta data from a Jamf instance. See Configuring data synchronization in Service Graph Connector for Jamf.

    The following data sources are included for the Jamf application:
    SG-Jamf Computers
    Imports data from computers and loads the imported data in the SG-Jamf Computers [sn_jamf_integrate_sg_jamf_computers] staging table.
    SG-Jamf Lookup Mac Software Bundle Ids
    Imports data from software applications installed on macOS devices and loads the imported data in the SG-Jamf Lookup Mac Software Bundle Ids [sn_cmdb_int_util_mac_software_bundleid_lookup] staging table.
    Note:
    To view the publisher information for applications installed on macOS devices, run the SG-Jamf Lookup Mac Software Bundle Ids data source before running the SG-Jamf Computers or SG-Jamf Mobile Devices data sources.
    SG-Jamf Mobile Devices
    Imports data from mobile devices and loads the imported data in the SG-Jamf Mobile Devices [sn_jamf_integrate_sg_jamf_mobile_devices] staging table.
    SG-Jamf Remove Computers Software
    Removes the imported computer software data that were later deleted from the source and updates the information in the SG-Jamf Remove Computers Software [sn_jamf_integrate_jamf_remove_software] staging table.
    SG-Jamf Remove Mobile Software
    Removes the imported mobile software data that were later deleted from the source and updates the information in the SG-Jamf Remove Mobile Software [sn_jamf_integrate_remove_mobile_software] staging table.
    SG-Jamf Software Usage
    Imports the software usage details from the Jamf environment to track which software data is being used infrequently, hasn't been used recently enough, or isn't being used at all and loads the imported data in the SG-Jamf Software Usage [sn_jamf_integrate_jamf_software_usage] staging table. Based on the software usage information, you can add a reclamation rule to aggregate usage records and to identify unused software devices. See Software reclamation rules.
    Note:
    The SG-Jamf Software Usage data source is available only when the Software Asset Management Professional plugin (com.snc.samp) is activated on your ServiceNow instance. See Request Software Asset Management.
    The imported data is then inserted into the following target tables:
    • CI Relationship [cmdb_rel_ci]
    • Computer [cmdb_ci_computer]
    • Disk [cmdb_ci_disk]
    • Handheld Computing device [cmdb_ci_handheld_computing]
    • IP Address [cmdb_ci_ip_address]
    • Network Adapter [cmdb_ci_network_adapter]
    • Printer [cmdb_ci_printer]
    • Serial Number [cmdb_serial_number]
    • Software Installation [cmdb_sam_sw_install] (If the SAM application is installed.)
    • Software Instance [cmdb_software_instance] (If the SAM application is not installed.)
    • Software [cmdb_ci_spkg] (If the SAM application is not installed.)
    • Software Usage [samp_sw_usage]
    Note:
    For the Computer [cmdb_ci_computer] and Handheld Computing device [cmdb_ci_handheld_computing] data sources, if you created multiple Jamf instances and want to know where the CIs originated from, you can identify the origins from the Key and Value columns. Additionally, you can view the Jamf Extension Attributes [sn_jamf_integrate_extension_attribute] and Most recent discovery [last_discovered] fields in both data sources. If you want to configure multiple instances, follow the steps in Configure Service Graph Connector for Jamf using the guided setup in step 4.

    For more information on where data is saved when pulling data from a Jamf application, see CMDB classes targeted in Service Graph Connector for Jamf.

    You can use the IntegrationHub ETL app to view the data maps. See IntegrationHub ETL for more information.