Grass Valley iTX Delivery Manager v.2.6 - Manual (Page 95)

89
Delivery Manager
Configuration and Setup Guide
Monitoring Active Jobs in Delivery Manager
The Active Jobs tab lists all the jobs currently being progressed by this instance of Delivery
Manager.
The table below describes the columns in this dialog:
Column Description
Job Name Lists the type of job in progress.
Job ID Indicates the order that the jobs are being progressed in and can be used to
track the progress of any particular job in the trace logs.
Filename Displays the original name of the file on the remote store and the network path
from where it is being copied
Status DisplaysDelivery Manager the current status of any job in the queue. It has
four states that are important to the user:
Idle • - this means the job is either waiting to start or is waiting for a user
response before moving to the next stage (Media QC for instance).
Active • - The job is currently in progress (a file is in mid transfer for exam-
ple)
Aborted • - The Job has either failed or has been cancelled by a user
action. In the case of a failure, use the Job ID to track the job's progress
through the trace logs.
Completed • - The job has now finished completely (the file has trans-
ferred and the database has been updated with new metadata etc.).
In diagnostic terms, this is the most important column.
Verifying the Database Update
Once the batch files have been executed, you can verify the Core or iTX 1.4 database has
been updated successfully by checking for the following:
• ‘Trigger On’ table
• Store procedures
• Required functions
• The Service Broker is present
Verifying the 'Trigger On' table is present
To verify the ‘Trigger On’ table is present:
1 Using your SQL Server Manager application, access the Core/iTX1.4 database.
2 Locate the table dbo.Omnibus_CLD_ClipDetails and expand Triggers .
3 Check there is a table named otg_OPUS_DM_Core_PushClipChanges .