Canto RoboFlow is a server-only component. By itself, Canto RoboFlow has no user visible component. However, there is an administration user interface embedded in Cumulus Web Server Console allowing the configuration of Canto RoboFlow and definition of workflows.
Cumulus WebServer Console as a part of Cumulus Web Solutions communicates with the RoboFlow back-end service ordaemon over port 8998.
If both components are installed on different servers, make sure that this port (8998) is open and permitted by both services on both servers!
RoboFlow and Cumulus
Canto RoboFlow automates the IN's and OUT's of Cumulus. It can import (catalog) files into Cumulus and it can export (converted) files out of Cumulus. It can import metadata into Cumulus and export metadata from Cumulus.
Deployment
Canto RoboFlow can be deployed on a server without any other Cumulus components. However, if Canto RoboFlow should be able to change a catalog, it needs network access to the respective Cumulus Server. Canto RoboFlow uses the Cumulus Java Classes for the communication with a Cumulus installation.
A workflow is deployed on exactly one Canto RoboFlow server. A sub-sequent workflow can only by triggered by a workflow on the same server. However, it is possible to have several servers with Canto RoboFlow executing different workflows on the same catalog.
How to Proceed
The main steps to get RoboFlow up and running are:
• Install (and where required, make run as service.) For details see Installing.
• Additionally, configure a daily restart of the RoboFlow service or daemon by means of the respective operation system.
• If required, activate RoboFlow (via the Remote Admin module of the Cumulus Server Console or Web Server Console). For details see Activation.
• Configure global settings (via the RoboFlow module of the Web Server Console.) For details, see the Web Server Console help “Configuring RoboFlow: Defining Global Workflow Settings.”
• Start working with RoboFlow and set up workflows (via the RoboFlow module of the Web Server Console.) For details, see the Web Server Console help “Configuring RoboFlow: Defining Workflows.”
