I am new to Adtempus and want to know if there are some guidelines to help keep things organized. For example, we have several different systems, each with a designated “owner”. Is it better to segregate systems with queues or with folders?
Is there a good way to identify job names, or sql jobs that are called by Adtempus jobs?
"System" meaning what here, like a set of applications or separate server that you're managing as agents in adtempus?
If it's the first one then groups (folders) are probably better. Queues are usually for when you need to limit jobs running at the same time or when you are assigning jobs to run on remote agents.
I didnt understand your question about job names.
By "system", I mean a groups of programs and database. For example, the "accounting" system might be maintained primarily by John. The "timecard" system might be maintained primarily by Mike. And so on...
By the sounds of your comment, folders would be a good way to segagate jobs for the accounting system versus the timecard system.
As for job names, there might be several jobs that are dependent on each other. The order is important and when you're looking at a list of job names, there's no way to tell which one comes first, second, third, and so on.
For example, are developers here using names like "begin-day-101" and "begin-day-102" (obviously job 101 comes before 102)?
What other best practices are you using? Do you start each job with a comment about dependencies?
Groups will be best for organization in your case.
My job streams and dependencies are not so complicated, I guess, that I have to put numbers in the names. I use the job flow diagram to see dependencies when I get confused. Depending on your work-flow it might make more sense to combine the jobs into different steps in the same job instead of having many jobs.
Replies are disabled for this topic.
