|
Step # |
Additional Details |
Link |
SME Audience |
|
Step 1 |
Review the Pre-Installation Checklist |
All SMEs |
|
|
Step 2 |
Enrol the CI Sync SaaS application into Entra ID |
AAD Admin |
|
|
Step 3 |
Create an Entra ID App Registration for the CI Sync Agent |
AAD Admin |
|
|
Step 4 |
Install the Multi-Source CI Sync Agent (on a VM) |
Infrastructure SME
|
|
|
Step 5 |
Register the CI Sync Agent, then Setup one/more Source System Connections |
Source System Admins
|
|
|
Step 6 |
Configure ServiceNow to be ready for CI Sync |
ServiceNow Admin |
|
|
Step 7 |
Add your ServiceNow destination connection |
CI Sync Admin |
|
|
Step 8 |
Run a small first synchronization and then progressively run more larger syncs |
CI Sync Admin
|
|
|
Other recommended sections to read |
|||
|
Appendix A |
Understand how the CI Sync Agent Authenticates to SQL Server |
Infrastructure SME
|
|
|
Appendix B |
Review SQL DB Health and Configure SQL Maintenance Plans |
SQL DBA#3 |
|
Footnotes
|
#1 |
On-Prem Active Directory SME only required if your SQL server is hosted separately (remotely) from the server that will run the CI Sync Agent. |
|
#2 |
Entra ID SME is required if you intend to use synchronization source connections for cloud hosted products which require an Entra ID App Registration (service principal) for authentication. |
|
#3 |
A SQL DBA is required if the person performing the CI Sync Agent installation does not have SQL sysadmin rights on the relevant SQL server. |