Multiple Creators, Single Executor - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
You can allow multiple users to access Data Mover and define work to be done but prevent them from executing the work. In this model, work is executed by only a limited set of trusted power users. A possible use case for this model is when multiple people or groups make data movement requests to the database administrator (DBA). Instead of the DBA creating all of the jobs, outside users can set up a job to do the requested work. The DBA can then review and configure the job as needed, schedule the work via outside scheduling processes, and execute the job. Outside users can view and monitor the progress and results of their requested work. This model allows multiple users to interact with Data Mover while maintaining an efficient and controlled work flow. To implement this usage model, do the following
  • Use job-level enforcement to control what outside users can do. Daemon-level enforcement would not be used in this case because you want to prevent users from editing other users' work.
  • Define requester role with daemon-level read and write permissions only. Users will automatically inherit job-level permissions on the jobs they create themselves.
  • Define executor role with daemon-level read, write, and execute permissions for the DBA.
  • When creating a job, the requester grants all job-level permissions (read, write, and execute) to the executor role so the DBA can access the job.