Gareth Tucker: Introduction to Scribe Online’s Replication and Integration Services
Scribe Software has historically been a strong player in the Microsoft CRM space, offering a configuration-based, no-code solution to both data migration and integration requirements.
In this post I have a look at their newer offering: Scribe Online.
This post will give you an overview of the installation experience, introduce you to the configuration process and demonstrate just how easy it is to get up and running very quickly.
What is Scribe Online?
The Scribe Online solution is a Scribe hosted solution that covers 2 functional areas:
Scribe’s Synchronisation Services offers similar functionality to the Scribe Insights product. It supports one off data migration scenarios and on-going integration scenarios with Microsoft CRM as either Source or Destination system. Again it’s Scribe hosted, and again it provides support for CRM Online but is equally suitable for an on premise installation of CRM.
I’ll keep this brief, I just want to give you a feel for the process. Scribe offers 14 day free trials from their website for the Scribe Online products so you can easily get your hands dirty.
You follow your nose through that trial sign up process, give them some contact details and they then email you a link like this:
That link, directs you to the Scribe Online console. You’ll be prompted to update your Silverlight if you are not on the latest (the console is a Silverlight app) and then asked to sign in:
The Console is divided horizontally with Replication Services residing in the top half of the screen and Synchronisation Services sitting at the bottom:
Now, you do need to install a local Agent in order to use Scribe Online, so it’s not 100% SAS. The Agent is required for connection to the source and destination systems. It’s installed as a Service.
I’m running on a Windows 2008 VM and I just went ahead and installed it locally:
You can see it installed and running here under my VM’s Services:
and for those that are curious, here’s what the Scribe Online architecture looks like:
That’s the install process. On to configuration…
Configuring Scribe Online Replication Services
From the Scribe Online console you kick off a wizard to add a new Replication Services solution:
You select the Agent that you installed earlier and then provide the connection details to your CRM Organisation and to your SQL Server database.
Your source can be CRM Online, a CRM on premise install or an IFD/ADFS install:
Your destination can only be a SQL Server database, and you need to create an empty database in advance:
Next, you select which CRM Entities / SQL tables you wish to replicate:
And then finally you pick when you want the replication to run. You have all the normal sort of scheduling options here, you can go daily at a certain time, you can deselect weekends, or have it only run once a month. You can also have it run every x minutes (but 15 minutes is the lowest number you can go with):
And that’s it. The Solution is now listed back on the Console screen and I can kick it off immediately if I want:
And before too long you will have a nice little replica of your CRM database sitting on your SQL Server ready for you to write reports against or to feed into a data warehouse or integrate into an ERP system:
To keep the replication going and your local database up to date the only trick is to make sure your Agent Service remains running and make sure you set your schedule correctly.
Configuring Scribe Online Synchronisation Services
The Synchronisation Services is Scribe Online’s integration and data migration engine.
Here the process is pretty similar. From the console we create a Solution and work our way through a wizard:
You pick the Agent you wish to use and then define at least 1 Map records. A Map is required for each source-destination table combination.
For this demo I am going to map a local SQL staging database’s table of Contact records to the CRM Contacts entity (but I could be reading those source records from a text file or other ODBC/OLE DB source).
You pick your data source type:
And then provide the connection string details:
Similar story for the destination connection. The same connection types are offered:
Here’s my connection:
Once you have specified the connection paths to your Source and Destination systems you need to provide a few more connection details and explain how Scribe should match existing records and what to do when records are matched. Lots of options there:
Last part of the mapping is to drop down to field level and map the individual fields. It’s a drag and drop experience. If some transformation is required you can easily add formulas to each mapping through a nice formula editor:
And we’re done with the mapping. Last step is to set the schedule. We see the same options here that we saw earlier:
And that’s it. I can wait for the schedule to kick off the synchronisation or I can run it manually.
In my example I have a local SQL table containing this data:
And this is how that data looks once my Scribe solution successfully loads it into CRM:
Here’s the Job History back in Scribe Online:
That gives you a feel for what a one-off data migration would be like. My solution was created with integration in mind though. I configured a unique key between my source and destination systems and informed Scribe how I wanted it handle updates vs. inserts.
I’ve also told Scribe to refer to the ‘UpdatedLast’ date field in my source table when performing subsequent synchronisations so that it only bothers to process records where that field is ahead of the last run date (indicating a recent change).
To simulate a subsequent interface run I change the phone number on 2 records and then bump the UpdatedLast field forward:
I kick the synchronisation job off again and see those 2 source record updates successfully synchronised up to CRM:
There you go, a quick walkthrough on the basics of Scribe Online. The Silverlight user interface and the end-to-end configuration user experience speaks volumes for the maturity of Scribe’s development processes and quality of their application architecture.
Let me know your experience and opinions via the comments below.
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
|Опции темы||Поиск в этой теме|