Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Centennial integration

Centennial integration

Integration with the Centennial SQL Server database is achieved using a data source definition of type JDBC that connects directly using an allowed TCP/IP port, usually port 1433. A scheduled import is defined that executes the data loading and transformation periodically.

Note: The following integration is not part of the supported platform. The integration may require additional customization prior to operating correctly. This integration is typically performed by an experienced administrator or consultant.

JDBC Data Source

Configure a JDBC Data Source to connect to your Centennial Discovery database directly. Query all rows from TableqryClient. You can use the Test Load 20 Rows link to troubleshoot connectivity.
Figure 1. Centennial Data Source

SQL Server Connectivity

To connect to the Centennial SQL Server database, TCP/IP connection access through port 1433 must be accessible.

Transform Map

After the Centennial data is loaded, an Import Set Table is created. Next create a Transform Map specifying the import set table as the source table and a CMDB CI type table as the target. The example below shows the map configured for the Printer CI target table, note the script that would selectively run this map only if the Centennial device type maps to the word Printer. Using this technique, you can configure a group of maps for the same import set table and map the rows to different CI tables. When a tranform is run on an import set, all transform maps are applied to each row.
Figure 2. Table Tansform Map
An example of mapping the Centennial fields to CI fields is shown below, with coalescing set for the description to name mapping.
Figure 3. Example Mapping of Centennial Fields to CI Fields

Scheduled Import

A Scheduled Import runs on the specified interval, loading the import set table from Centennial, and applying all Transform Maps associated with the import set table. An example configuration follows.
Figure 4. Scheduled Data Import