Set up and Run the Connector

You can set up the connector using the instructions in Run the Connector. SimpleSynchronize.dll must be in the connector directory, and you must set the following parameters in connectorLibCpp.cfg:

       ConnectorLibrary=SimpleSynchronize

This example connector ingests a document for each integer from 2 up to a configured limit. The default limit is 1000, but this can be changed by setting the configuration parameter IntegerLimit in the task section of the configuration file.

If you run the connector without CFS running, you should see information like this logged to synchronize.log:

       00-Always: Starting SYNCHRONIZE for task 'MYTASK1'
       30-Normal: MYTASK1: Queuing Add: 2	
       30-Normal: MYTASK1: Queuing Add: 3
       70-Error: MYTASK1: INGESTION: Send error: ACI error: Cannot Connect
       30-Normal: MYTASK1: INGESTION: Pending:0 Sending:0 Done:0 Failed:2
       70-Error: MYTASK1: Ingestion failed for 2
       70-Error: MYTASK1: Ingestion failed for 3
       00-Always: Finished SYNCHRONIZE for task 'MYTASK1' 

For each document generated, a “Queuing Add” message is logged automatically by the Ingester.Add method. Following that is an error from the Ingester showing that it could not connect to CFS. After that there are failure messages from the ingest result handler (ResultHandler) which was called for each file that could not be ingested.

The default [Ingestion] section in the connector's configuration file points to a CFS listening on port 7000. If a CFS is listening on this port when you run the connector, the log messages are different:

       00-Always: Starting SYNCHRONIZE for task 'MYTASK1'
       30-Normal: MYTASK1: Queuing Add: 2
       30-Normal: MYTASK1: Queuing Add: 3
       30-Normal: MYTASK1: INGESTION: Pending:0 Sending:0 Done:2 Failed:0
       30-Normal: MYTASK1: Document 2, ingest Add succeeded!
       30-Normal: MYTASK1: Document 3, ingest Add succeeded!
       00-Always: Finished SYNCHRONIZE for task 'MYTASK1'

This time ingestion succeeds and the ingest result handler is called for each document that was successfully ingested.