Breadcrumbs

Setup Overview (SaaS Agent for Existing On-Prem Customers)

Contents of this Page

  1. Intended Audience

  2. Overview Diagram

  3. Overview of the High Level Setup Steps

  4. Links to Detailed Setup documentation and SME involvement

Intended Audience

  • These steps are for existing Syncfish customers, who already use a CI Sync Instance with the CI Sync Multi-Source On-Prem Agent, and are now adopting the CI Sync SaaS Agent (i.e. are running both CI Sync Agents at the same time).

  • For customers in the above situation, many of the components are already in place (e.g. their CI Sync SaaS is already registered in their Entra ID, and their ServiceNow instance is already configured for CI Sync). As such, there are fewer instructions for adding the CI Sync SaaS Agent (and the relevant source systems to the SaaS Agent).

Overview Diagram

CI Sync On-Prem and SaaS Agent to SN - High Level Topology (inc Step Bubbles).svg

Overview of the High Level Setup Steps

Each of the high level steps reference the CI Sync Detailed Setup Instructions. After reading the High Level Steps below we recommend visiting the Detailed Setup Instructions (for customers with an existing On-Prem Agent) Context and FAQs page here Context and FAQs.

#

Component

High Level Supporting Notes

1

DEV/TEST ServiceNow

Nothing to do (ServiceNow will already have been setup for CI Sync when originally implemented with the CI Sync On-Prem Agent).

2

Enterprise Application object in Entra ID

Nothing to do (your CI Sync SaaS instance will already be registered as an Enterprise Application in Entra ID when CI Sync was first implemented with the CI Sync On-Prem Agent).

3

Cloud Source Systems
(data sources for the CI Sync SaaS Agent)

Each source system has it’s own unique requirements for authentication and API/data access.

Your SME/Admin of each source system needs to create a credential for the CI Sync SaaS Agent and perform any other configuration in the source system itself.

Syncfish provide setup instructions for each source system within Steps to Add Cloud Connectors (Existing Customers). For example:

  1. For AWS: Add AWS to SaaS Agent

  2. For Azure: Add Azure to SaaS Agent

  3. For Lansweeper Cloud:Add Lansweeper Cloud to SaaS Agent

  4. For GCP: Add GCP to SaaS Agent

  5. and so on.

4

CI Sync Web UI
(to add ServiceNow as a destination, and add cloud data sources for the CI Sync SaaS Agent)

  1. You will add each cloud source (e.g. AWS, Azure, etc) as a source connection using the CI Sync Web UI. Visit Steps to Add Cloud Connectors (Existing Customers). That page contains an index of each supported source system. For example:

    1. For AWS: Add AWS to SaaS Agent

    2. For Azure: Add Azure to SaaS Agent

    3. For Lansweeper Cloud:Add Lansweeper Cloud to SaaS Agent

    4. For GCP: Add GCP to SaaS Agent

    5. and so on.

5

CI Sync SaaS

You then do the following using your Non-Production ServiceNow Instance (e.g. ServiceNow DEV or TEST)

  1. See Run a Small Initial Sync Job (then run more) of the Detailed Setup Instructions.

  2. You will assess the resulting data in your non-Production ServiceNow instance.

  3. Once you are satisifed your non-production results/data is satisfactory you will progress to Production (see #6 below).

6

PROD ServiceNow

Nothing to do (except of course to perform testing in Non-Production ServiceNow before doing any sync’s into Production)

Step-by-Setup Setup Process and SMEs Required

Step

SME Audience

Estimated Time to Complete the Step

Step 1 - Pre-Read Materials


Project Manager
Source System Admins
CI Sync Admin

10 minutes

Step 2 - Add one/more source system connections using the CI Sync Web UI

(Use the instructions below to create access credentials in the relevant source system and then add a source system connection within your CI Sync SaaS Instance using the CI Sync Web UI)


Add Azure to SaaS Agent

Azure Admin
CI Sync Admin

10 minutes per source system

Add AWS to SaaS Agent

AWS Admin
CI Sync Admin

Add Lansweeper Cloud to SaaS Agent

Lansweeper Admin
CI Sync Admin

Add GCP to SaaS Agent

GCP Admin
CI Sync Admin

Step 3 - Run sync jobs from the source system to the destination CMDB


Run a Small Initial Sync Job (then run more)

Note: In addition to the instructions above, Syncfish highly recommend reading the following page before your first sync

FAQ - What are the Top Tips when first synchronizing data to my non-PROD CMDB?

CI Sync Admin

Source System admin/s

One or more of the following:

  • ServiceNow Admin

  • ServiceNow platform owner

  • CMDB Manager

  • IT Asset manager