Dataworks Enterprise Build and Versioning

From time to time, as defined in the Product Roadmap, a new version of Dataworks Enterprise is built and released. The build/release cycle is largely governed by the requirements of the product strategy and the needs of those who develop Dataworks Enterprise (and other TF) business opportunities. The actual build/QA/Test process is carried out by Dataworks Enterprise Development team.

When a new version of the product is released, we carry out a phased rollout, initially only upgrading boxes used by other TF development groups. The system is then migrated to our Hubs and then to production sites managed by our group. Finally, the upgrade is delievered to customers either directly or through the appropriate FM or field service groups. Note, that there can be some delay between the time of a release, and the time at which it is installed. In this respect, we are naturally conservative.

Version Numbering

Each release of Dataworks Enterprise has an associated version number. This number is "burnt" into every binary distributed as part of the build process. A program distributed with the release (RTVers.exe) can be used to display the versions of each binary installed on a particular box. This program can be found in the Launcher tools menu and in the standard Windows "Start" menu.

The format of the version number is:

The BuildNumber is always incremented on each build and so uniquely identifies any particular build. Within each released version, patches are indicated by changes to the revision number.

For instance, at the time of writing, recent release versions are:

November 2001
April 2001
September 2000

Distribution Formats

Each distribution of Dataworks Enterprise consists of a "CD image". The current CD image can be located on the Downloads page of this site.

The CD contains a complete setup for all the standard components of Dataworks Enterprise plus additional documentation and other information. Subsequent to a release being made available, there is sometimes a need to create "patches" to the standard install. In some cases, the number of patches makes it a requirement that we reissue the entrie CD image. However, usually a patch simply consists of one or two files which are intending to be copied onto the target host.

The CD uses a standard installation utility called InstallShield. To install the software you simply run the setup program. One problem some people have when installing the software is that dependent modules are not included as part of the install. In other words, if you need to install the XML handler, you may find that you will need to pre-install the correct version of the MS XML Parser. We do not automatically install software from third parties or indeed from other parts of TF. This was a deliberate policy decision, since engineers and operators need to be fully aware of what has or has not been installed on a target.

Dataworks Enterprise distribution CD is not packed up as is normal for most Installation CDs. If you explore the CD, you will find all the individual programs and other files separately stored (rather than being archived in a .cab file). This is designed to assist the user in isolating specific faults in installation.

In addition to the standard installation, the Release CD image also contains other additional support files. In the Documents directory are some additional documentation describing the product.

During installation, two separate installations are performed in the background. The first is to install the notifier driver using the program InstallNotify.exe. The driver is responsible for cross process communications in Dataworks Enterprise. During this process, it is possible you will be asked to reboot, though we do try to avoid this eventuality. The second install is an option to install VB support files. This option avoids problems with missing Visual Basic support files such as VBVM60.DLL or controls used by some of the standard tools. The distribution CD has a directory called VBSupport containing this setup program. The distribution CD also contains an SDK directory that is used by developers of Dataworks Enterprise related products.