Running Data Migration

[ngilday]

I have been writing scripts to load data in the NexJ.DM* tables.

I would like to test running the DM process to see if the data from the DM tables moves into the NexJ tables.

What is the best way to run this? In admin console via the Batch Broker?

What is the best way to run it and then check that the data showed up and then undo so it can be run again?

Can I run the data migration for a subset of the tables like perhaps only DMUsers to start?

Thanks

 

0

[ddonciu]

There are several ways to trigger the data import. For a detailed description of each, please refer to the Data Migration Operations Manual, specifically the Trigger Process section.

In a nutshell, you can use Admin Console to trigger Data Migration (this is described in the Manual Load section). As you become more familiar with the process, you should also try the other possibilities which support different business needs.

The processName parameter (the name of the runbook to be executed) determines the objects loaded by Data Migration. Out of the box two types of runbooks are created, a Data Migration runbook containing all objects supported in the proper order, and individual runbooks for each object. In your case you can use the runbook named Runbook LoadUser (unfortunatelly an error in the documentation refers to an older name for this runbook, this has already been fixed and will be present in future versions of the documentation).

0

[ngilday]

Where can I find out about the other ways to run RunBooks?

On Admin Console, Batch Broker what are the parameters to be put in?

Going through the instruction in the DM guides I am not sure what to put in as parameters.

I chose dm:DMRequst-create

then enter processName and batch Id

But what values do I put in?

processName:  LoadRunBook Users (?)

batchId: [I am guessing the batchId in the DM tables?]

Thoughts?

0

[David McAnuff]

The options for executing a load process/runbook is either manual, which by using the Admin Console or Automated.  Examples of automation can be via the DM_START stored procedure.  There is an example of using stored procedures in the automated load section of developers guide for starting and monitoring a load to NexJ CRM.

When doing a manual or automated load. The arguments to pass are the name of the runbook and the batchId.

How to use the Admin Console to perform a load is covered in the section of the document “Manual Load”.  The name of the arguments required by the “dm:DMRequest-create” are processName and batchId.  The values to assign to these two arguments are the name of the runbook for processName and identifier tagged to the records to processed.  The is a screenshot in the document how to add the arguments and assigned the values.

The list of runbooks and data associated to each runbook is covered in the specification document and the developers guide.

As an example, let’s say you want to load users into NexJ CRM.  Below are the steps you would follow:

1. populate the staging table DMUser with the users to be loaded into NexJ CRM.  In the staging table there is a column called batchId, that I will set to “101” one all the user records that you want to load into NexJ CRM
2. Bring up the NexJ Admin Console and click “Batch Broker” and for Batch Process select “dm:DMRequest-create”
3. Select the “+” next to Arguments and add these two arguments “processName” and batchId
4. Set the value for “processName” to “Runbook LoadUser”
5. Set the value for “batchId” to “101”
   1. User records that do not have a batchId of “101” will be skipped and not load into NexJ CRM.
   2. batchId can any thing a client’s wants to use to group a series of records together
6. Click “Ok”

 

 

0

[ngilday]

Much thanks. Make sense.

0

[ngilday]

Getting this error.

0

Attachments:

You must be logged in to view attached files.

[David McAnuff]

I am assuming that you launched the application from NexJ Studio.  If my assumption is correct to get the actual error message for reference Id “fso376″, do a search from the NexJ Console for by the reference Id ” that appears in the screenshot.  If the application was not launched from NexJ Studio then search for the reference Id in the application log.

0

[Author]

Posts