Configuring the RScan Client Connector

This section implies that the connector has already been added.

See Creating a Standard Connector.

See Also
Introducing the RScan Client Connector
  1. Configure the following options.

    Parameter

    Description

    Host

    Specifies the server hosting the remote scan service.

    Port

    Specifies the network port where the remote RSCAN service is listening.

    URL prefix

    Specifies the URL prefix used to reach the RSCAN remote servlet. For example, with the following settings:

    • Host: myserver.com
    • Port: 5000
    • URL prefix: path/to/service

    The RSCAN servlet URL is:

    http://myserver.com:5000/path/to/service/rscan/

    Route documents to this connector

    Routes the documents of your remote unmanaged connectors back to the RScan Client connector instead of sending them to the indexing-server directly. This option is required if you want the documents pushed by unmanaged connectors, to go through the RScan Client connector PushAPI filters.

    Disable this option if you do not use Push API filters and want to keep high performances (CPU...).

    Use configuration of existing connector

    Sends the specified connector configuration to the remote connector. If the configuration changes in the Administration Console, the new configuration is sent to the remote connector at the next full scan operation.

    Retrieve fetch protocol

    Specifies the fetch server's protocol:

    • v1 – Exalead CloudView Retrieve Protocol V1
    • v2 – Exalead CloudView Retrieve Protocol V2
    • rpv3 – Exalead CloudView Retrieve Protocol V3
    • networkRetriever – Use NETVIBES Web Crawler. If specified, the Document server URL option must be stored as publicName|fetcherName

  2. Optionally, to retrieve the configuration parameters of your remote unmanaged connector, click Retrieve default.
  3. Click Apply.

    You can now start scan operations and use Push API filters on your unmanaged connectors.