VOOZH about

URL: https://www.cdata.com/kb/tech/servicenow-sync-vertica.rst

⇱ Automated Continuous ServiceNow Replication to Vertica

Automated Continuous ServiceNow Replication to Vertica

👁 Mohsin Turki
Mohsin Turki
Technical Marketing Engineer
Use CData Sync for automated, continuous, customizable ServiceNow replication to Vertica.

Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live ServiceNow data into your Vertica instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.

About ServiceNow Data Integration

CData simplifies access and integration of live ServiceNow data. Our customers leverage CData connectivity to:

  • Get optimized performance since CData uses the REST API for data and the SOAP API for schema.
  • Read, write, update, and delete ServiceNow objects like Schedules, Timelines, Questions, Syslogs and more.
  • Use SQL stored procedures for actions like adding items to a cart, submitting orders, and downloading attachments.
  • Securely authenticate with ServiceNow, including basic (username and password), OKTA, ADFS, OneLogin, and PingFederate authentication schemes.

Many users access live ServiceNow data from preferred analytics tools like Tableau, Power BI, and Excel, and use CData solutions to integrate ServiceNow data with their database or data warehouse.


Getting Started


Configure Vertica as a Replication Destination

Using CData Sync, you can replicate ServiceNow data to Vertica. To add a replication destination, navigate to the Connections tab.

  1. Click Add Connection. 👁 Add a new connection.
  2. Select the Destinations tab and locate the Vertica connector. 👁 Configure a Destination connection to Vertica.
  3. Click the Configure Connection icon at the end of that row to open the New Connection page. If the Configure Connection icon is not available, click the Download Connector icon to install the Vertica connector. For more information about installing new connectors, see Connections in the Help documentation.
  4. After the connected is added, enter the Basic connection properties:
    • Connection Name: Enter a connection name of your choice.
    • Server: Enter the host name or IP address of the Vertica database.
    • Port: Enter the port for Vertica (5443 by default). This property is optional.
    • User: Enter the username of the authenticating Vertica database user.
    • Password: Enter the password of the authenticating Vertica database user.
    • Database: Enter the name of the database hosted on the Vertica Server.
    5. 👁 Enter the connection details.
  5. Once connected, click Create & Test to create, test and save the connection.

You are now connected to Vertica and can use it as both a source and a destination.

NOTE: You can use the Label feature to add a label for a source or a destination.

👁 Add a label.

In this article, we will demonstrate how to load ServiceNow data into Vertica and utilize it as a destination.

Configure the ServiceNow Connection

You can configure a connection to ServiceNow from the Connections tab. To add a connection to your ServiceNow account, navigate to the Connections tab.

  1. Click Add Connection.
  2. Select a source (ServiceNow).
  3. Configure the connection properties.

    ServiceNow uses the OAuth 2.0 authentication standard. To authenticate using OAuth, register an OAuth app with ServiceNow to obtain the OAuthClientId and OAuthClientSecret connection properties. In addition to the OAuth values, specify the Instance, Username, and Password connection properties.

    See the "Getting Started" chapter in the help documentation for a guide on connecting to ServiceNow.

    👁 Configuring a Source connection (Salesforce is shown).
  4. Click Connect to ServiceNow to ensure that the connection is configured properly.
  5. Click Save & Test to save the changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

👁 Select Source and Destination connections for the replication.

Replicate Entire Tables

To replicate an entire table, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of ServiceNow tables you wish to replicate into Vertica, and click Add Tasks again.

👁 Choose entire tables to replicate (Salesforce is shown).

Customize Your Replication

You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication with the help of SQL queries. 👁 Configure a replication Transform.

Schedule Your Replication

Select the Overview tab in the Job, and click Configure under Schedule. You can schedule a job to run automatically by configuring it to run at specified intervals, ranging from once every 10 minutes to once every month.

👁 Schedule your job to run automatically.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your ServiceNow data to Vertica.

Run the Replication Job

Once all the required configurations are made for the job, select the ServiceNow table you wish to replicate and click Run. After the replication completes successfully, a notification appears, showing the time taken to run the job and the number of rows replicated.

👁 Run the job.

Free Trial & More Information

Now that you have seen how to replicate ServiceNow data into Vertica, visit our CData Sync page to explore more about CData Sync and download a free 30-day trial. Start consolidating your enterprise data today!

As always, our world-class Support Team is ready to answer any questions you may have.