16.20 - Configuring Data Mover Job Execution and Logs Download Using Ecosystem Manager - Teradata Ecosystem Manager

Teradata® Ecosystem Manager Installation, Configuration, and Upgrade Guide for Customers

Teradata Ecosystem Manager
December 2020
Follow these steps to trigger a Data Mover job and Job execution logs in a non-workflow environment. Use this method with Data Mover 15.00 and lower and when the Data Mover REST component is not installed on the Data Mover server.

To configure Data Mover job execution triggers and logs, ensure the following packages are installed and configured:

  • Data Mover dmDaemon
  • dmAgent
  • dmCommandline

Make sure the Ecosystem Manager Publisher and Agent packages are installed and configured on the Data Mover server.

  1. On the Data Mover server, write a script.
    Ensure the script contains datamove commands to interface with Data Mover. Datamove is an executable from Data Mover.
    In this example, note how datamove is used. The Data Mover job 'Spaces_Table_test_212_142829216634' uses as a source TDPID.
    uowid='datamove  start -job_name Spaces_Table_test_212_142829216634 | tao; - 1| cut  - f2 -d':' | cut -f2 -d ' ' `
    echo $uowid
    while [$count -eq 1]
    count=`datamover status -jobname Spaces_table_test_212_142829216634 | tail - 1|
    grep RUNNING | wc-1`
    echco $count
    sleep 1
    echo "Checking status:
    echo "$logile"
    datamove status -job_name Spaces_table_test_212_142829216634 -output_level 4 >$
    sendevent --et END --jid Spaces_table_test_212_142829216634 - t DM_PROCESS_SOURCE
    -w $uowide --tds --log "dm-agent4:$logfile" 
  2. In the Ecosystem Configuration portlet, click Actions, then do the following to add a new script.
    1. Click .
    2. Select Execute Script.
    3. Enter an Action Name.
      For example, TestScript.
    4. Complete the fields as needed, then click OK.
  3. In the Ecosystem Configuration portlet, click Jobs, then add a new job.
    1. Click .
    2. Enter the Job Name.
      For example, TestJob.
    3. Complete the fields as needed, then click OK.
  4. To associate the script with the job you created, do the following:
    1. Click the Action Rules tab.
    2. Click .
    3. Select a response.
      For example, if a START event type Normal severity occurs on, execute TestScript.
    4. Complete the fields as needed, then click OK.
  5. Issue a START event for the configured job.
    For example, the START event can be issued from the Ecosystem Manager server: sendevent --et START --tds -t DM_PROCESS --sc DM --jid TestJob -w TestJobUOWID
  6. After the action completes, in the Ecosystem Explorer portlet, click the Jobs tab.
  7. In the summary table, locate the job that executed.
  8. In the Log column, click the log file name.
    You can open or save the log file.