Please enable JavaScript to view this site.

CopiaFacts Reference

CopiaFacts Control Panel

CFCP [remote]

This program allows remote monitoring and control of COPIAFACTS and FFEXTERN instances.  CFCP communicates using the Copia Message Center service (CFMSG), which must be running on the machine on which the Copia Application Data Area resides.  It operates in the following modes:

When run on the same machine as a COPIAFACTS or FFEXTERN instance, it can control and monitor these instances, and can also install or uninstall the service application CFESERVICE or CFXSERVICE to run these applications in service mode.

When run on the same local network as the COPIAFACTS or FFEXTERN instances, CFCP can be used to monitor and control any COPIAFACTS or FFEXTERN instance running as a service on the network; and to monitor but not control any COPIAFACTS or FFEXTERN instance running with a designated nodename on a desktop on the another network machine.  CFCP uses node names to connect to COPIAFACTS and FFEXTERN and cannot monitor instances started without a node name on the command line.

When run on a remote machine, and if the control IP port is open and forwarded to the machine on which the Copia Application Data Area resides and the CFMSG service runs, CFCP can monitor and control COPIAFACTS and FFEXTERN instances in the same way as when it is run on a local machine.

CFCP can only control COPIAFACTS and FFEXTERN instances started with a fixed node name on the command line.  It will not find instances started without a nodename on another node.

If you are new to CFCP, please first read the Introduction to Service Operations topic.

The modes of operation are described in more detail in the following sub-topics:

Using CFCP to control local applications

Using CFCP to control network applications

Using CFCP to control remote applications

The main screen of the CFCP application shows initially only a list of the CopiaFacts Engine and Document Converter nodes that have been configured in the FAXCOUNT.HWL file (using CFHWL).  None will be connected initially.  Select one of the named nodes to have CFCP locate it, either running locally, or found via CFMSG.  The screen then shows a summary status for the application, if running and connected to CFMSG.  The status values are not updated every time they change, but can be set to refresh manually or at 5-second intervals.

See the sub-topics for details of the CFCP actions.  The Actions button displays an 'action panel' with a list of selectable action descriptions appropriate to the current application and service status.

Status Cache Overrides

It is possible that manual actions on services and unexpected termination can cause the application status cache held by the CFMSG service to become invalid.  To handle this, two options are available when you right-click the Action button:

Display a window showing the content of the CFMSG cache for each service (shown as SV/nodename) and application.

Clear the CFMSG cache, and after a short while the running services and applications will report a fresh status.  This action is preferable to restarting the CFMSG service, which should normally be avoided.

When you are running CFCP on the same machine as the CMSG service, you also have an option to shut down CFMSG from a right-click on the Action button.  Do not do this unless you have already shut down the other services.

If you need to recover in this way from CFCP becoming unsynchronized from the running services, it may take some minutes to recover.  CFCP may also take a couple of minutes to react to unexpected manual termination of the service, for example from the Task Manager processes list.