Triggering Imports

An alternative to start an import in the designer, is to run it with the console. This gives you alot of flexibility. You can configure it as scheduled task, start it within a batch-file or you probably have a service, which can start an external tool, when a file is placed in a folder.

Run it in a batchfile

Simply insert the following line in your bat-file:

C:\Program Files\IntegrationTool\IntegrationTool.ConsoleProjectStarter.exe --projectpath "C:\your projectpath\theproject.xml" --packagenames "your packagename"

The ConsoleProjectStarter does the same as if you would run it from within the integration tool designer, so when it finished, you can examine the logs of the run from within the designer! If you want to run multiple packages, just separate them with comma. They’ll run in the order you pass them.

Run it from scheduled task

Each windows-installation comes with a nice tool called scheduled-tasks. It allows you to run programms on a regular base. In the next step we will configure an import to run every night.

  1. Click Windows + R
  2. In the Run-window enter taskschd.msc /s
  3. Menu > Action > Create Basic Task
  4. Enter a Name and Description for your scheduled task and click Next
  5. Select Daily and click Next
  6. In the desired start-time and click Next
  7. Select Start a program and click Next
  8. Browse to the path C:\Program Files\IntegrationTool\ and select the IntegrationTool.ConsoleProjectStarter.exe. In the parameter-field pass the parameters
    --projectpath "C:\your projectpath\theproject.xml" --packagenames "your packagename".
  9. Review the summary page and click finish!

We’re almost done. The task would now start under your user and only if you’re logged on. I think that’s not what you want normally. Follow the next steps to have a better configured scheduled task.

  1. Doubleclick the created task
  2. On the general-tab click Change User or Group…
  3. Search for the user under which the tool should execute.
  4. Select Run wether the user is logged on or not
  5. Check Run with highest privileges