New Version 8.1 Features
CopiaFacts Version 8.1, released in January 2012, has the following principal enhancements:
New Version-Numbering Scheme
From this release, we have simplified CopiaFacts versioning so that we no longer use different version numbers for every program and library module. Instead we now use the standard hierarchy: Major Version, Minor Version, Release Version, Build Number, and in each build, all components will have the same four-element version number.
The elements will be used as follows:
|Major Version||The major version number (currently 8) will only change when Copia introduces a significant new release. As has historically been the case, we will expect all users to move to the release and, after a changeover period, support for earlier releases will be withdrawn.|
|Minor Version||The minor version (currently 1) will change when a new release occurs which is of sufficient importance that we announce it and encourage users to move to it.|
|Release Version||This version number (currently 0) will change when a build introduces an incompatibility between different major components of CopiaFacts. Separate components which interact will check that the first three elements of the version number must be the same.|
|Build Number||The build number will be incremented for each build. Not all builds will be released. Within a single component (for example the COPIAFACTS engine and its DLLs), the version numbers including the build number must be identical.|
The value of the FFVERSION system variable (previously 4 digits) will now consist of a six-digit number made up of the three single-digit major/minor/release numbers and a three-digit build number. For example 810123. For release 8.1, we have started build numbers at 64.
The COPIAFACTS engine and its principal DLLs must now have identical version numbers, as must FFEXTERN and CVSINGLE.
Appendix M of this reference manual, which formerly listed the old-style version numbers of each component, becomes redundant since all components will now have the same version number. Appendix M instead contains a summary of changes in each build. The changes database referenced by FFCHANGES has been retired.
Multiple COPIAFACTS Engine Instances on a Single Machine
Copia have always recommended that separate instances of COPIAFACTS should be run, servicing different TOSEND queues, whenever it necessary to mix multiple transmission types (for example fax and e-mail, or fax and voice). This prevents, for example, wasteful scanning of TOSEND queues for e-mail tasks to run on free e-mail threads when all the available FS files are for fax transmissions and fax lines are already busy.
For high-volume applications such as large-scale broadcasting there has been no problem in dedicating different machines to each broadcast type and limiting the range of TOSEND queues handled on each machine. However until now, smaller systems have required complex juggling of resources to handle a mixed workload efficiently on a single machine.
Starting with CopiaFacts version 8.1, we have made it possible to configure two (or more) COPIAFACTS nodes to run on the same machine. Each instance of COPIAFACTS must be started with the name of a configured CopiaFacts node on the command-line, and should normally enable scanning of fewer than all the defined TOSENDx queue folders, with each set of folders only used for one type of work. Failure to configure the nodes with exclusive access to TOSEND queues, or mixing work types in a TOSEND folder, would be a counterproductive use of this feature.
Nodenames must be unique and, as with multiple machines, each nodename can only be used for one instance. The same hardware type cannot be configured for more than one node per machine.
To help differentiate between COPIAFACTS nodes, use the $colorframe command to apply a different colored frame to each one. This command also overlays a matching color circle on the taskbar icon in Windows 7 and Server 2008R2.