ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (15.4.0) 15.3.0 15.2.0 15.1.x 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Configuring Initial Loads to RDM Tables

When the RDM logical model is created and deployed for the first time, tables created in the web application are empty. To fill an empty table with data, you can either perform a bulk import from a text file in the web application (see Importing and Exporting Data in RDM) or configure a plan, which can load data from any number of sources, transform and join them in any required way, and then populate the chosen RDM table.

It is also possible to generate a plan that imports records together with their editing history: a separate plan is generated for this case.

To configure an initial load plan for a table:

  1. Make sure the Initial load or Initial load - history option or both are selected for the table that needs to be populated: expand RDM Logical Model > Tables and then double-click [your table]. See Tables for details.

    When Initial load - history is selected, a separate plan with the _history suffix is generated.

  2. Right-click the table and select Generate initial load plan(s). Plans are generated to Files > plans > batchLoadPlans.

    To generate plans for all tables, right-click the Tables node and select Generate.

  3. Right-click the table and select Open initial load plan or Open initial load history plan.

  4. Configure your plan:

    1. If you are configuring a simple load plan (no history), then the configuration is very similar or the same as the one described in Configuring Tasks for Importing Data from Text Files.

    2. If you are configuring a load plan with history (suffixed with _history), the general logic is the same, but a different RDM step is used—RDM History Importer—which has a slightly different Columns tab configuration:

      1. Two columns are required and automatically generated here: d_from and d_to, which define the beginning and end of validity for a particular edit of any given record. These columns have From Column and To Column marked, respectively. Make sure your source data has columns containing this data.

      2. You need to mark one or several columns as Grouping Column: these act like a primary key.

        The following is a sample configuration:

        RDM History Importer configuration

  5. Save your project and reload metadata.

    After you run a plan that contains the History Importer step, you need to restart the RDM web application configuration to ensure the changes are correctly synchronized. For details, see How to Deploy an RDM Web App Configuration.

Was this page useful?