Deploying Applications

When deploying your ETL application to other locations and computers, e.g. test and production servers, at a minimum:

  • Ensure the target execution node or account is licensed by the "actionetl.license.json" license file
  • Switch to Release mode (unless you are specifically deploying a Debug build)
  • Clean the project (or solution)
  • Build the project (or solution)
  • Deploy the project output files
    • On .NET Framework, use the ...\<project-folder>\bin\Release\ output folder
    • On .NET 6+, first publish the build files to a new output folder
      • E.g. dotnet publish -c Release -f net6.0 <project-folder>, which puts the output files in .../<project-folder>/bin/AnyCPU/Release/net6.0/. See Publish .NET apps with the .NET CLI for details.
    • The above output folder with sub folders contains any executable, DLLs, configuration files etc. required to run the application, which all need to be deployed to the target location or computer.
    • Consider starting with a simple XCOPY deployment, by simply copying all the files from the Release folder to the deployment target folder, and only move to more involved deployment methods if and when required.
    • Consider automating the deployment, e.g. with:
    • Deploying the .NET Framework and Applications and .NET application publishing overview has in-depth information on various deployment options.
Note

Most organizations have well defined procedures for deploying .NET applications, consider adopting these also for your actionETL applications.

Running Applications

  • Run the executable in the deployed output folder: .../<deployed-folder>/<application-name>.exe.

Scheduling Jobs

To run the application on a regular schedule, trigger on other jobs etc., the most common option is to use whichever job scheduler your organization has standardized on. There are many free and commercial job schedulers available, which includes the free Windows Task Scheduler and on Linux the bare-bones crontab.

SQL Server installations often use the SQL Server Agent scheduler.

actionETL applications are normal executables and therefore easy to integrate with any job scheduler.

In some cases it can be useful to instead incorporate a job scheduler within your application, e.g. the widely used Quartz.Net.

See Also