If you are upgrading from a previous adTempus version, you can (and should) install version 3.0 without removing the previous version. The setup program will upgrade your existing installation.
Please review the information below for changes that cause problems for upgrading users. See the What's New topic for an overview of new features, and the adTempus Web site for more information about changes in this version of adTempus.
|
|
The upgrade process will upgrade your adTempus database, making it incompatible with previous versions of adTempus. Before you install, we highly recommend that you back up your adTempus database so that you can restore it if it is necessary to revert to the previous software version. |
If you are using the MSDE database engine for adTempus, we recommend that you upgrade to the newer SQL Server 2005 Express engine. To do this, be sure to check the Install, configure, or reconfigure the adTempus database option on the Database Information page of the Setup wizard. Setup will install SQL Server Express and migrate your database automatically.
The Microsoft Access database format is no longer supported by adTempus. If you are still using an Access database for adTempus, it will be converted to SQL Server Express.
If you are using the Distributed Scheduling features of adTempus, note that jobs are no longer associated directly with Remote Agents. Instead, all jobs are assigned to Job Queues, and Distributed Scheduling options can be set for each Queue. During the upgrade process, adTempus will create new queues and assign jobs to them automatically based on your existing Distributed Scheduling settings. When you start adTempus for the first time after the upgrade, review the settings for each queue to ensure they are correct, and check that jobs are assigned to the correct queues.
The new security model supports security inheritance. See the Security Changes topic for more information.
Some "breaking" changes in adTempus 3.0 may cause problems for some users:
adTempus does not support side-by-side installations of the server software
adTempus 3.0 cannot interoperate with previous versions of adTempus
The adTempus export/import format has changed
The adTempus API has changed
The simple Web-based monitoring tool available for adTempus 2.0 will not work with this version. A new ASP.NET interface is planned for the future.
Some little-used features have been removed: the Application Exception trigger, SMS notification using modems, and the ability to send keystrokes to applications.
Command-line options for the adtexec utility have changed.
The sections below provide more information on these points.
You cannot have more than one version of the adTempus server software (the adTempus service) installed on a computer. If you install the server software, Setup will upgrade any existing installation.
If you install only the client software (the adTempus Console), it is possible to install it on a computer where an earlier version is installed, without removing that version. That is, you can install two different versions of the adTempus Console on the same computer.
Note that you can install the adTempus 3.0 Console on a computer with version 2.x installed, but you cannot install the version 2.x Console on a computer after you have installed version 3.0. Therefore if you need to be able to run both versions of the Console on a computer, be sure to install the 2.x version first and then the 3.0 version.
adTempus 3.0 uses a different communications mechanism than previous versions of adTempus. Therefore:
If you are using Distributed Scheduling, you must upgrade the Master and all Agents at the same time. If you upgrade only one computer, it will not be able to communicate with the other computers.
If you use inter-job dependencies (conditions or responses), you must upgrade all linked computers at the same time.
If you do a full installation of adTempus on a computer, you will not be able to use the Console on that computer to administer computers running earlier versions of adTempus. See the previous section for information on side-by-side installations of the Console.
adTempus 3.0 uses a new XML-based file format for data export and import. This format is not compatible with prior versions. adTempus 3.0 cannot read export files created by previous versions, and previous versions cannot read export files created by adTempus.
Therefore if you have exported data that you will need in adTempus 3.0, you need to import it into adTempus 2.x before upgrading. You can then re-export the data in the new format after the upgrade.
The adTempus API has changed for version 3.0. Though the architecture is the same, many changes have been made to support new features. The new API is not binary-compatible with code built for previous versions.
In previous versions of the adTempus API, collections used "one-based" indexing, consistent with Visual Basic practices. In this version the API has been modified so that all collections use "zero-based" indexing, consistent with modern C++ and .NET practices. As a result, all customer code that manipulates collections exposed by the API must be modified to use the new zero-based indexing.
The collections now expose enumerators, so customers may wish to change to enumerator access to the collections rather than index-based access.
At a minimum you will need to recompile your applications that use the API, and in many cases will have to make minor code changes. See the adTempus API page for the latest information.
Due to the API changes discussed above, the simple ASP-base Web monitoring tool available for adTempus 2.0 will not work with adTempus 3.0. A new ASP.NET Web interface is planned for the future.
The following features have been removed from adTempus:
The Application Exception trigger
SMS notification using modems
The ability to send keystrokes to applications
If you are currently using these features, contact us to discuss alternatives.
The command-line syntax for the adtexec utility has changed. If you are using the adtexec utility to submit jobs for execution, you may need to modify your batch files, scripts, etc. See the adtexec topic for information on the new command-line syntax.
