Rule 3 - Mapping of JDisc Asset Types to ServiceNow CMDB CI Classes

Rule Synopsis

These are the rule/s that determine the target CMDB CI Tables/Classes used by CI Sync for each JDisc Asset Type.

The target CI Table/CI Class is used by CI Sync for two purposes:

  1. To search for an existing CIs during a CI Update Operation.

  2. To write new CIs during a CI Insert Operation.

Rule Details and Default

The default table mappings for Primary/Parent Resource Types are shown below.

Primary/Parent Resource Types

Default Target Class/Classes

Computer Systems

Apple Mac

cmdb_ci_computer

HP-UX Server

cmdb_ci_hpux_server

Linux Server

cmdb_ci_linux_server

NAS Server

cmdb_ci_storage_server

Solaris Server

cmdb_ci_solaris_server

Unix Server

cmdb_ci_unix_server

Windows Server

cmdb_ci_win_server

Windows PC

cmdb_ci_computer

Windows CE

cmdb_ci_handheld_computing

Unclassified Computer

cmdb_ci_computer

Virtualization

Citrix Xen Server

cmdb_ci_hyper_v_server

VMWare vCentres

cmdb_ci_vcenter

VMware ESX Server

cmdb_ci_esx_server

XCP-ng Server

cmdb_ci_hyper_v_server

Docker Container

cmdb_ci_docker_container

Database Servers

DB2 Instances

cmdb_ci_db_db2_instance

Informix Instances

cmdb_ci_db_instance

MariaDB Instances

cmdb_ci_db_instance

MongoDB Instances

cmdb_ci_db_mongodb_instance

MSSQL Server Instances

cmdb_ci_db_mssql_instance

MSSQL Server Analysis Services

cmdb_ci_db_mssql_analysis

MSSQL Server Reporting Services

cmdb_ci_db_mssql_reporting

MySQL Instances

cmdb_ci_db_mssql_instance

Oracle Instances

cmdb_ci_db_ora_instance

PostgreSQL Instances

cmdb_ci_db_postgresql_instance

Progress OpenEdge Instances

cmdb_ci_db_instance

SAP MAxDB Instances

cmdb_ci_db_instance

Sybase Instances

cmdb_ci_db_syb_instance

Vertica Instances

cmdb_ci_db_instance

Blade Enclosures

Enclosures

cmdb_ci_hpe_bladesystem_enclosure

Servers

cmdb_ci_hpe_bladesystem_blade

Network Equipment

Access Points

cmdb_ci_wap_network

Access Point Controllers

cmdb_ci_ip_switch

Firewalls

cmdb_ci_ip_firewall

Routers

cmdb_ci_ip_router

Switches

cmdb_ci_ip_switch

Storage

Fibre Channel Switches

cmdb_ci_storage_switch

iOT

Automation Controllers

 

Other Hardware

Card Printers

cmdb_ci_printer

IP Phone

cmdb_ci_ip_phone

Multifunctional Device

 

Printer

cmdb_ci_printer

UPS

cmdb_ci_ups

Unidentified Devices

cmdb_ci

Web Servers

Apache Web Servers

cmdb_ci_apache_web_server

Apache httpd Web Servers

cmdb_ci_apache_web_server

Microsoft IIS Servers

cmdb_ci_microsoft_iis_web_server

NGINX Servers

cmdb_ci_nginx_web_server

Application Servers

JAR Applications

cmdb_ci_app_server

JBOX Server Archives

cmdb_ci_app_server_jboss

JEE Applications

cmdb_ci_app_server_websphere

JEE Web Applications

cmdb_ci_app_server

The default table mappings for Secondary/Child Records are shown below.

Secondary/Child Records

Default Target Class

Peripherals (for multiple record types)

cmdb_ci_peripheral

Network Adapter (for multiple record types)

cmdb_ci_network_adapter

Memory Modules (for multiple record types)

cmdb_ci_memory_module

Physical Disks (for multiple record types)

cmdb_ci_storage_device

Logical Disks (for multiple record types)

cmdb_ci_file_system

Software (for multiple record types)

cmdb_software_instance

Endpoint Security (for multiple record types)

u_cmdb_ci_endpoint_security

Java Installation (for multiple record types)

u_cmdb_ci_java_installation

Java Process (for multiple record types)

u_cmdb_ci_java_process

Java Risk Summary (for multiple record types)

u_java_risk_summary

SSH Configuration (for multiple record types)

u_cmdb_ci_ssh_config

Management Device (for Blade Enclosures)

cmdb_ci_ip_switch

Power Supplies (for Blade Enclosures)

cmdb_ci_pdu

Management Device (for multiple record types)

cmdb_ci_outofband_device

Patches (for multiple record types)

cmdb_ci_patches

Pending Updates (for multiple record types)

u_cmdb_ci_pending_update

Blade Switch

cmdb_ci_ip_switch

Virtual Machine Instances (for VMWare)

cmdb_ci_vmware_instance

Virtual Machine Instances (for Hyper-V)

cmdb_ci_hyper_v_instance

DB2 Database Catalog

cmdb_ci_db_db2_catalog

Informix Database Catalog

cmdb_ci_db_catalog

Microsoft SQL Database Catalog

cmdb_ci_db_mssql_database

MariaDB Database Catalog

cmdb_ci_db_catalog

MongoDB Database Catalog

cmdb_ci_db_catalog

MySQL Database Catalog

cmdb_ci_db_mysql_catalog

Progress OpenEdge Database Catalog

cmdb_ci_db_catalog

Oracle Database Catalog

cmdb_ci_db_ora_catalog

PostgreSQL Database Catalog

cmdb_ci_db_catalog

SAP MaxDb  Database Catalog

cmdb_ci_db_catalog

Sybase Database Catalog

cmdb_ci_db_syb_catalog

Vertica Database Catalog

cmdb_ci_db_catalog

Local Virtual Switch (for ESX Servers)

cmdb_ci_vcenter_network

Ports (for Switches)

cmdb_switch_port

Distributed Virtual Switch

cmdb_ci_vcenter_dvs

Data Centers

cmdb_ci_vcenter_datacenter

Clusters

cmdb_ci_vcenter_cluster

Override Options

Context

Customers may consider changing these mappings to target different CMDB CI Tables/Classes shown above.  This can often be required when existing CIs are already present in the CMDB (in Classes different to those shown below) and CI Sync is expected to correlate to the existing CIs.

Options

  1. The target CI Class can be amended per Asset Type.

  2. The target Related List/Child Record table can be amended per Asset Type.

Overriding via Connection Settings

Not Available - Requires a Custom Data Sync Rule (and therefore a Syncfish Support Plan to modify the default behavior).

Additional Information

N/A

N/A