Cloudaware CMDB Data Import Into ServiceNow Using Google BigQuery

Cloudaware can import CMDB data into the Google BigQuery and then automatically upload the data to ServiceNow on a regular basis. This article instructs you on how to set up and automate import of Cloudaware CMDB data into ServiceNow CMDB using a Google BigQuery table.

To see how Cloudaware seamlessly integrates with ServiceNow in action, request a demo.

Use case: Using Cloudaware and ServiceNow for asset management, a customer would like to download their app inventory or the list of AWS-related resources from Cloudaware CMDB to ServiceNow to enrich the existing data. Cloudaware uses Google BigQuery as temporary storage for the imported CMDB data file. The customer should set up data import in their ServiceNow to get data uploaded and mapped correctly. The data upload can be scheduled as one-time or recurrent (automated) action.

Prerequisites

1. Define the scope of Cloudaware CMDB data for download into ServiceNow. Contact your dedicated account manager or tam@cloudaware.com to specify the data scope.

2. Define whether you would like to use your Google BigQuery* or a Cloudaware-managed** one.

*If you have a Google BigQuery table preconfigured in your Google environment, contact your dedicated account manager or tam@cloudaware.com to get the resulting file.

**Contact your dedicated account manager or tam@cloudaware.com for Google BigQuery table configuration. Once the table and the file are prepared, Cloudaware will provide a path to the file for further setup.

3. You must be ServiceNow Admin to run a Cloudaware script required for data import automation. Otherwise, contact your organization’s ServiceNow Admin for assistance.

1 - Create Data Source

Create a data source in ServiceNow to store the imported Cloudaware data as the import set table (check ServiceNow Documentation). Fill in the form and click Submit:

If you don't have a Google BigQuery table preconfigured for data, the File path value should be provided by Cloudaware.

Click Load All Records to load data into the import set table:

2 - Create Target Table

The target table stores ServiceNow CMDB data. If you use ServiceNow as CMDB and have a target table already to import external data, skip to step 3.

Manually

Check ServiceNow Documentation for instructions.

Use consistent field names in both the target table and the import set table (stage table) to ensure automated mapping of matching fields.

Automatically using a custom script

To use this option, create the import set table (stage table) first as the script checks field names and uses them to create a target table to automatically map fields while transforming.

var attrs = new Packages.java.util.HashMap();
var table_label  = "target_table_label",  // specify your target table label name
  table_name = "target_table_name", // specify your target table name
  extends_table = 'cmdb_ci'; // specify where the target table to be created
  
var gr = new GlideRecord('u_gcp_import_set_table_label'); // specify your import set table (stage table)
gr.setLimit(1);
gr.query();
  
while (gr.next()) {
var fields = new GlideRecordUtil().getFields(gr);
  for (var i = 0; i < fields.length; i++){
    fieldName = fields[i];
    var labelName = gr[fieldName].getLabel();
  var ca = new GlideColumnAttributes(labelName);
  ca.setType("string");
  ca.setUsePrefix(true);
  attrs.put(labelName, ca);
  }
}

var tc = new GlideTableCreator(table_name , table_label);
tc.setColumnAttributes(attrs);
if(typeof extends_table != 'undefined') tc.setExtends(extends_table);
tc.update();

This script must be run before transform map creation in step 3.

3 - Create Transform Map

Set up a transform map to define and automate field mapping. Click Create transform map:

Check ServiceNow Documentation for instructions. Fill in the form:

Source table - the combination of data source and import set table data (see step 1)
Target table - the table that you create manually or automatically using the Cloudaware script (see step 2)

Click Submit.

Select one of the options in the section 'Related Links':

• Auto Map Matching Fields to create mapping automatically

• Mapping Assist to create mapping manually

If you created the target table using the script or maintained consistency of field names when creating the target table manually, select automated mapping. The Field Maps may look the following:

For one-time data import, values in the column Coalesce must be set to false.

If you would like to import data and update records on a regular basis, define the unique field and set Coalesce to true for it. Learn more here.

Click Transform.

Specify Import set and Transform map values. Сlick Transform to proceed.

The data will be loaded to the target table:

4 - Schedule Data Import

Once data tables are managed and mapping is set up, schedule data import runs - check ServiceNow Documentation for instructions.