|
|
 |
|
adTempus Version 2.1 (June 7, 2007)
adTempus version 2.1 is a maintenance release that addresses many issues discovered
since the release of version 2.0.4. It does not introduce any major new features.
This release is available to all users at no charge.
Users of version 2.0.x of adTempus should install this update if:
- You are experiencing any of the problems discussed below, or any other stability
issues.
- You are using File Triggers and want to make use of the new behavior described below.
- You need to run adTempus under Windows Vista.
- You want to make use of any of the other minor enhancements described below.
Customers who have many adTempus installations or whose policies require extensive
internal testing before rolling out a software update may wish to forgo this update
unless they are affected by the issues it addresses, as Arcana Development expects
to release a major update to adTempus in late 2007.
Upgrading From a Prior Version
Users of prior versions of adTempus can run the version 2.1 setup program to upgrade
their existing installations. No new license is required.
Microsoft Access Database is Deprecated
Previous versions of adTempus used a Microsoft Access database by default. Due to
reliability and performance issues, Arcana Development has long urged customers
to convert from the Access database to a SQL Server database.
With version 2.1, the setup program no longer gives the option to use the Microsoft
Access database, and this database will not be supported in future versions of adTempus.
If you are still using the Microsoft Access database, you should convert to SQL
Server or MSDE when you upgrade to version 2.1. This can be done in two ways:
- During installation. In the setup wizard, select either the SQL Server or MSDE option.
The setup program will create the new database and convert your existing data.
- After installation. In the setup wizard, select the option to not change your database
settings. After installation adTempus will continue to use your existing Access
database until you convert to SQL Server or MSDE as discussed
here.
For more information, please refer to the Arcana Development
Knowledge Base.
Changes in This Release
Changes to File Trigger Behavior
Customers who use File Triggers should note the changes to file trigger behavior
discussed below.
Other Changes
The following lists describes most of the significant changes made for this release.
Some issues that were corrected in the release may not be listed below.
|
General |
|
|
|
Group Duplication |
CR00000211
Enhancement |
|
The adTempus Console now allows you to duplicate a Job Group, which duplicates all
jobs in the group.
|
|
Search/Replace Capability |
CR00000212
Enhancement |
|
The Tools menu of the adTempus Console now has a Search/Replace command that can
be used to replace strings in various properties of jobs.
|
|
New Registry option to suppress job execution |
CR00000408
Enhancement |
|
A new option was added to allow the adTempus service to be started without executing
any jobs, e.g., if you need to start the service to modify jobs, but don't want
any jobs to be run while you do so. To suppress execution of jobs, run the Registry
Editor and go to (or create if necessary) the key "HKEY_LOCAL_MACHINE\Software\Arcana
Development\adTempus\options". Create a new String (REG_SZ) value named "Engine:RunJobs"
and set it to "0". Then start the adTempus service.
To re-enable job execution, delete the value you created above, or set it to "1",
then restart the adTempus service.
|
|
Main job status for a job now updated when job runs on
an Agent |
CR00000310
Defect |
|
For more information see Knowledge Base article
K00000228.
|
|
Job control action to set step status to Succeeded or Failed
does not work |
CR00000412
Defect |
|
When a Job Control Action was configured to set the status of a job step to Succeeded
or Failed, the action failed to change the step's status. |
|
Time portion of active range is ignored for schedule |
CR00000417
Defect |
|
When an active range (starting and ending date/time) is specified for a schedule,
adTempus ignored the specified time and used only the date.
For more information see Knowledge Base article
K00000231.
|
|
Timestamp may be incorrect in e-mail messages sent by adTempus |
CR00000430
Defect |
|
The Date header in e-mail messages sent by adTempus was sometimes formatted incorrectly,
causing mail clients to display the wrong timestamp for the messages.
For more information see Knowledge Base article
K00000249.
|
|
Job Groups do not inherit proper security settings |
CR00000444
Defect |
|
Job Groups should use the same default security settings as Jobs, and the same settings
should determine who is permitted to create Job Groups. Instead, groups were created
with no default security, and only Administrators were able to create new groups.
The software was corrected so that groups use the proper security settings.
|
|
Some event log records have message "UNKNOWN" |
CR00000454
Defect |
|
For more information see Knowledge Base article
K00000248.
|
|
Performance enhancement reduces service initialization
time |
CR00000457
Defect |
|
A performance enhancement was made that drastically reduces the initialization period
when the adTempus service is started, particularly for installations with a large
number of jobs.
|
|
adTempus service sometimes crashed during shutdown |
CR00000458
Defect |
|
If Event Log triggers were being used, they sometimes caused the adTempus service
to crash while it was being shut down. This problem did not affect adTempus data
or operation. The problem was corrected.
|
| Programs, scripts, and batch files run by adTempus can log messages to the adTempus Job Log | CR00000472
Enhancement | |
For more information see Knowledge Base article K00000264. |
|
|
Conditions |
|
|
|
A job will ignore conditions on the job that triggered
it |
CR00000497
Enhancement |
|
When Job A triggers Job B through a Response, Job B will ignore any conditions that
it has on Job A. Previously, conditions were enforced, resulting in situations where
Job B could not be executed as desired.
|
|
File conditions do not expand environment variables |
CR00000478
Defect |
|
If you include an environment variable such as "%FilePath%" in the file specification
for a file condition, adTempus did not resolve the variable to its value, so the
condition did not work properly. |
|
Problem when using job condition with "most recent instance
since last execution of dependent job" and no previous instances exist for dependent
job. |
CR00000498
Defect |
|
If Job A has a condition on another job that uses the rule "the most recent
instance since the last execution of the dependent job" or "any instance since the
last execution of the dependent job" and there is no previous instance of Job A,
a software problem caused Job A to become stuck in "Waiting for Condition" status
until the adTempus service was restarted. adTempus has been modified so that in
the case where Job A has no prior instances, the condition will consider the most
recent instance of the target job, regardless of when it ran. |
|
|
Triggers |
|
|
|
File Trigger can now start a separate instance of the job
for each file it finds |
CR00000183
Enhancement |
|
Previously, the File Trigger started a single instance of the job, regardless of
how many files it found in a given processing pass that matched the trigger criteria.
A new "Trigger separately for each file" option has been added to the File Trigger.
When this option is checked, a separate instance is started for each found file.
When the option is not checked, the trigger behaves as before.
The option to capture the triggering files has also been reinstated, and now works
correctly. When this option is checked, the file(s) that caused the job to run will
be saved as Captured Files for the job instance.
Note: The new option is checked by default when a new File Trigger
is created. If you want new triggers to use the old behavior, you must uncheck the
option after you create a trigger. File Triggers that already exist when you install
the update are not affected.
|
|
|
|