Scheduling the Scribe Package

Scheduling can be used to automatically migrate any new record from source to destination as soon as it is created in the source. This process is also known as Scribe Integration. When we schedule the Scribe package, we do not need to run it manually by opening it in Scribe Workbench as shown in my previous article Data Migration from Microsoft SQL Database to Dynamics CRM.

This article assumes that you already have a Scribe package that is ready to be executed. If you do not have it, you can follow the aforementioned article to create one.

To schedule the scribe package, follow these steps.

 

Step 1: Update the Scribe Package

Click on "Configure Source" button.

Figure 1

A message box window will popup. Select "Keep existing links" radio option. Click OK button.
On the next window, select the "Source Keys" button.

Figure 2

You will get the following popup.

Figure 3

Click the button on the right of "Source Key Field(s)" as shown above. On the next window, select the primary key from the left column and move it to the right column.

Figure 4

Click OK. Repeat the same process for "Source Name Field(s)" button. You do not need to change the default options.

Now you will have the primary key in both fields. Select OK.

Figure 5

Click on "Update Source" button now. 

Figure 6

Make the selections as highlighted below. Then select OK.

Figure 7

On the next screen select OK as well.

Figure 8

Close the Scribe package.

Now open Scribe Console. The desktop icon looks like the following.

Figure 9

You will get the screen similar to the following. Select "Site Settings" as highlighted below.

Figure 10

Make sure that the "Collaborations root" path is valid. You can verify that by navigating to that folder using windows explorer.

Click Save. You might get this message "Changes to these settings will not take effect until scribe services are restarted." To restart services, you can manually go to services by using Run → services.msc and restart them or you can use the following approach that is described at this URL.
https://community.dynamics.com/crm/b/koorbconsultingteamblog/archive/2012/06/06/start-stop-scribe-service-using-batch-file.aspx

Right click ->New ->Text Document, Select text file and rename to StopScribe.bat
net Stop "Scribe Monitorserver"
net stop "Scribe MessageServer"
net stop "Scribe EventManager"
net stop "Scribe BridgeServer"
net Stop "Scribe AdminServer"

Right click ->New ->Text Document, Select text file and rename to StartScribe.bat
net start "Scribe AdminServer"
net start "Scribe BridgeServer"
net start "Scribe EventManager"
net start "Scribe MessageServer"
net start "Scribe MonitorServer"

Expand the default node under collaborations folder. This is how the folders are organized in windows explorer.

Figure 11

Copy your Scribe packages into this folder. If you want your packages on different path, make sure it appears/added into the Administration →Security → Console Shared Folders.
I recommend creating a new folder inside the Default folder as highlighted above to leave the scheduling process go smoothly.
Click Add button to add a new job.

Figure 12

In "Process Event" section, select the option as highlighted. Then select the "Browse" button. Make sure that you follow the previous steps correctly otherwise you might get this or similar error when you click the browse button.

Cannot browse c:\scribe\Scribe Collaborations not authorized by access settings.

Figure 13


Select your Scribe package and click "OK".
Change the Process name if required. Click on Step 2, 3, 4, 5. I did not have to change any values in the next steps. Click the "Finish" button at the bottom that should be enabled by now.

Figure 14

Now you can insert the record into CRM table by using the SQL Query or CRM. It should be automatically moved to the destination CRM after two minutes or 120 seconds.