Open topic with navigation
You can configure the Enovia Connector by editing the configuration file. The configuration file is located in the connector’s installation folder. You can modify the file with a text editor.
The parameters in the configuration file are divided into sections that represent connector functionality.
Some parameters can be set in more than one section of the configuration file. If a parameter is set in more than one section, the value of the parameter located in the most specific section overrides the value of the parameter defined in the other sections. For example, if a parameter can be set in "
Default", the value in the
TaskName section overrides the value in the
FetchTasks section, which in turn overrides the value in the
Default section. This means that you can set a default value for a parameter, and then override that value for specific tasks.
For information about the parameters that you can use to configure the Enovia Connector, refer to the Enovia Connector Reference.
[Server] section specifies the ACI port of the connector. It can also contain parameters that control the way the connector handles ACI requests.
[Service] section specifies the service port of the connector.
[Actions] section contains configuration parameters that specify how the connector processes actions that are sent to the ACI port. For example, you can configure event handlers that run when an action starts, finishes, or encounters an error.
[Logging] section contains configuration parameters that determine how messages are logged. You can use log streams to send different types of message to separate log files. The configuration file also contains a section to configure each of the log streams.
[Connector] section contains parameters that control general connector behavior. For example, you can specify a schedule for the fetch tasks that you configure.
[Default] section is used to define default settings for configuration parameters. For example, you can specify default settings for the tasks in the
[FetchTasks] section lists the fetch tasks that you want to run. A fetch task is a task that retrieves data from a repository. Fetch tasks are usually run automatically by the connector, but you can also run a fetch task by sending an action to the connector’s ACI port.
In this section, enter the total number of fetch tasks in the
Number parameter and then list the tasks in consecutive order starting from 0 (zero). For example:
[FetchTasks] Number=2 0=MyTask0 1=MyTask1
[TaskName] section contains configuration parameters that apply to a specific task. There must be a
[TaskName] section for every task listed in the
[Ingestion] section specifies where to send the data that is extracted by the connector.
You can send data to a Connector Framework Server, Haven OnDemand, or another connector. For more information about ingestion, see Ingestion.
[DistributedConnector] section configures the connector to operate with the Distributed Connector. The Distributed Connector is an ACI server that distributes actions (
collect and so on) between multiple connectors.
For more information about the Distributed Connector, refer to the Distributed Connector Administration Guide.
[ViewServer] section contains parameters that allow the connector’s view action to use a View Server. If necessary, the View Server converts files to HTML so that they can be viewed in a web browser.
[License] section contains details about the License server (the server on which your license file is located).
[DocumentTracking] section contains parameters that enable the tracking of documents through import and indexing processes.