Datahub Import (DataSetImporter)

Owned by Conor McCann
Last updated: Nov 03, 2017

Following the installation of iQSonar Datahub. You will need to setup the datasetimporter configuration. There are two was if importing a dataset. Using the DataSetImporter as well as a Manual Import.

 

Setting up the importer settings and running the importer.

  1. Navigate to the Datahub directory

    This is a default directory, so if you have specified another directory you will need to navigate to that directory.

    You should see the following list of files

  2. Run DSIConfigurator, you will be presented with the following window:


  3. 1: iQsonar DB connection details.

    2: Datahub Staging DB connection details.

    3: Datahub EDW DB connection details.

    You must use integrated authentication in order for Datahub import to complete successfully.

    1: IQsonar DB connection details.

    2: Datahub Staging DB connection details.

    3: Datahub EDW DB connection details.

    Note: you can use either the SA account or Integrated Security.

  4. Running the importer. To run the importer you will need to use CMD command line interface as an Administrator or a User that has local Administrator privileges.



  5. Using CD command navigate to the Datahub directory

    Run the following command: DataSetImporter.exe config.xml .

    Where config.xml is the name of the configuration file you have saved earlier.

    Once CMD is finished. Check DataSetImporter.txt for Errors this is a log file and should be used to verify dataset import is complete.

 

Manual import:

  1. In case you need to run dataset importer manually you will need to log in to the DB with Datahub user level of privileges or higher.Navigate to the Integrated Services Catalogs and run the packages below
     

 

 

 

 

 

 

 

 

 

 

 

 

 

 

              By right clicking on individual packages and selecting Execute option. You will need to run packages one at the time,

              you will need to allow processing of each package to complete before moving onto a next one.

             

        2.   The order of execution is crucially important as they feed one into another.

       The order is as follows:

  • 2.14 to Staging
  • Staging
  • WSToEDW
  • DerivedSoftware
  • PostImportProcessing (You will need to run all the packages in this section top to bottom)

 

Back to Top