Understanding The Modes of Operation
- • oracle.documaker.ecmconnector.applications.Singleton
Batch or one-shot mode – In this mode, Documaker Connector creates the configured number of Documaker Source instances, calls each one once to fetch and process a single batch of transactions (if any are available) and then terminates. No socket is opened for commands and there is no subsequent polling of the Documaker Source instances. In the case of the Documaker source, this allows for a single pass through any records in the database table for each configured source instance.
This is typically used for a non-persistent, static document source, rather than with the Oracle Documaker source. For example, you could use this to read a named input text file. Such a source does not continually receive new documents, so once the configured source of documents (such as the single named input file) is exhausted, there is no need for Documaker Connector to continue to run. This would function similarly to the WebCenter Content BatchLoader application.
- oracle.documaker.ecmconnector.applications.Server
Server or Normal continuous mode – Documaker Connector runs until it receives a shutdown command, polling the source instances for documents to process. To receive control commands, Documaker Connector opens a TCP/IP socket and listens for incoming messages. The port number can be controlled by a configuration parameter and a password can be established which must be supplied along with any commands.
- oracle.documaker.ecmconnector.applications.Commander
Command mode – Documaker Connector can also be run solely to send a command to another copy of Documaker Connector running in Server mode. You specify the command as a parameter on the command line. When run in this mode, Documaker Connector sends the command to the designated host name and port with the supplied password, if any, and immediately terminates.