Template Jobs Vs. Custom Jobs - Novell ADMINSTUDIO 9.5 User Manual

Chapter 23: Automating Tasks Using Job Manager
About Job Manager

Template Jobs vs. Custom Jobs

When you create a new Job, you can either base it on an existing Template that has pre-defined Job Steps, or build
a Custom Job by choosing which Job Steps you want to perform and in what order. Each type of Job serves a
particular purpose and provides certain benefits.
Template Jobs
Creating Jobs based on pre-defined Templates enables an organization to enforce consistent business practices.
System Administrators can create a Template to define a series of Job Steps that they always want performed on a
certain type of package before it is deployed. Then, when a package that falls into that category needs to be
prepared for deployment, a Job based on that Template can be created and run.
For example, if all users of a specific department of an organization use the same disk image (Operating System
and set of applications), all packages that are distributed in that department would need to have conflict analysis
performed against that OS Snapshot and those target applications. The System Administrator could create a
Template that uses those specific target applications, and could include very specific ICE and ACE rules in the
conflict analysis, based upon requirements specific to that target environment.
In Template Jobs:
• Target packages
•
Source packages
• An Import Job Step cannot be
• A Directory Monitoring Job Step can be included
packages and then automatically import or reimport those packages into the Application Catalog. This is
equivalent to using the Application Manager Package Auto Import Wizard to automatically import packages
from a network directory. However, subsequent Job Steps cannot perform any actions on packages imported
or reimported as part of a Directory Monitoring Job Step.
Note •
Custom Jobs
When creating a new Custom Job, you can include only the Job Steps that you want to perform, in the order you
want to perform them, using the source and target packages that you select when you create the Job. In Custom
Jobs:
• Both Source and Target packages are selected
• An Import or Directory Monitoring Job Step can be
part of those steps as Source packages in subsequent Job Steps.
Because you can insert an Import or Directory Monitoring Job Step, a Custom Job is well-suited to automate a
bulk import process.
1748
are selected when a Template is created.
are selected when a Job based on a Template is created.
See About Automatically Importing Packages from a Network Directory
included.
to examine the specified directory for new or modified
when the Custom Job is created.
included, and you can use packages imported as
for more information.
ADS-0950-UG00 AdminStudio 9.5 User Guide