COPIAFACTS normally runs on a Windows Workstation (networked or a stand-alone). See the separate notes for installation and configuration details.
Use the Windows Control Panel "System" applet to set any environment variables you need. Normally the only ones you may need are FAXMSG or SVP. You can also emulate Windows environment variables with the $environment configuration command.
You can start COPIAFACTS manually from a shortcut or the start menu, or you can place a shortcut in the startup group to start it automatically when Windows starts up.
There is one command-line switch and one command-line option (the switch must come first, if used):
|-m||Causes the program to start in management mode, in which only the Options, Queues, Lines and FS counts pages are enabled, and the Start button is disabled. When started without a nodename parameter, settings changes apply to any COPIAFACTS node started on the machine; with a nodename parameter the settings changes only apply to the specific node on the same machine. When CFESERVICE is used to run COPIAFACTS as a service, starting COPIAFACTS in management mode from CFCP can modify settings for the running service application.|
|nodename||Used to run multiple COPIAFACTS instances on a single machine. Do not specify the nodename if you only need one instance. Specify the nodename for all instances if you run multiple instances.|
Management mode is useful to manage queues and schedules from a central machine. You can select different nodes using the pull-down on the Options page and then view and edit the schedules as if you were interacting with COPIAFACTS on the selected node.
From CopiaFacts release 8.1, you may specify a nodename on the COPIAFACTS command line. This allows multiple COPIAFACTS instances to be run on the same machine. Use the $colorframe command to distinguish each instance with a different color frame in its window. The frame is only displayed when multiple nodes are configured and running on a single machine.
On the Queues and Lines pages, you can check what node you are operating on by the caption on the leftmost of the three buttons at the foot of the page.
Starting with CopiaFacts version 8.1, we have made it possible to configure two (or more) COPIAFACTS nodes to run on the same machine. To enable multiple-node operation on a single machine,
|Every instance of COPIAFACTS must be started with the name of a configured CopiaFacts node on the command-line|
|The first time you run COPIAFACTS with a nodename on the command-line, you MUST currently use a command session, not STARTCOPIA.|
Each node 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.
Typically you would use this feature if you have a single machine and want to run significant volumes of both fax and e-mail outbound operations. If you use only one COPIAFACTS instance, time may be wasted scanning fax FS files when all fax lines are busy but some e-mail lines are free, and vice-versa.
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.
|Do not use command-line nodenames when only one instance COPIAFACTS is needed on a physical machine, and remove them from STARTCOPIA and from any desktop or start menu shortcuts if you reconfigure your system in this way.|
|When you first start COPIAFACTS with a nodename on the command-line, a new set of program settings will be created in the Registry tied to that nodename, copied from your existing settings. Thereafter, the set of program options selected will depend on what you specify on the command-line. So if you revert to using COPIAFACTS with no command-line argument, and then for example select node M3, you will end up with the program settings from your original 'without nodename' instance, not with those you may have modified when you started with node M3 on the command-line.|
|If you use management mode, you must use the nodename on the command line to affect the settings for when a nodename is in use.|
Graphical User Interface
The COPIAFACTS.EXE program implements the server engine and displays its status. When you click the icon COPIAFACTS will be started with the default options or those you selected and saved for the previous run, if different. To change options and parameters, click the PAUSE button before the COPIAFACTS engine starts up, and then click START when you have set the required options. Click the large SAVE button to save options for future use. You can also change many of the trace options, runtime options, and debug settings while the program is running.
The graphical interface has seven display options on a tabbed dialog box. The Options display allows setting tracing and debugging flags. The Summary screen shows transaction counts, line status and the event log. The Trace screen shows only the event log. The Scrollback display freezes the event log and allows you to scroll up to earlier records. The Queues and Line Schedules displays allow schedules to be changed dynamically. The FS Count display shows the number of active and processed items in the system. Help is provided for all functions in the form of pop-up hint windows, and you can also link to this PDF file from the options screen.
Graphical Customization for cover sheets or other applications is implemented in the CF8GCOVER DLL loaded by COPIAFACTS.EXE.
Note that all Windows fonts specified for graphical customization annotation fields must be present on each node running the CopiaFacts engine, and not just on the machine on which the GCT or GTT is designed.
If you specified at install time that COPIAFACTS should be run automatically at startup, STARTCOPIA will run at startup to start it..
On the first options screen you can add a delay before starting CopiaFacts, which is often necessary to ensure that the hardware drivers for fax/voice boards have completed initialization.
The normal way to shut down COPIAFACTS is to click the Stop button. This will do a 'controlled shutdown, which waits until current calls and operations finish and suppresses the starting of new transactions. During a controlled shutdown, you have options to shut down immediately, without waiting for calls to finish, or to cancel the shutdown:
If you check the box to restart after shutdown, note that the Windows environment variables used by COPIAFACTS are not refreshed. To refresh the environment you must close COPIAFACTS completely and restart it, or you can use the $environment command to specify global variables instead.