There is one configuration file per connector; it is a simple XML file that contains the connector properties and the location when the connector is implemented. Perceptive Enterprise Search looks for the connector configuration files in the Perceptive Enterprise Search\WebFederator folder.
<ISYSfederator name=â€NameOfConnector†description=â€textâ€>
<properties>
<property name=â€PropertyA†value=â€ValueA†caption=â€â€ type=â€â€/>
<property name=â€PropertyB†value=â€ValueB†/>
</properties>
<driver type=â€.net|COM†class=â€{GUID}†module=â€module.dll†/>
</ISYSfederator>
The configuration file contains the following elements.
ISYSfederator |
The root element of the XML file, has the following attributes: |
properties | Contains the set of connector properties of the connector, there can be only one <properties> node in the configuration file. |
property |
Each property node contains configuration options for the connector,
the <property> node must appear within a <properties> node. Properties
can have the following attributes: |
driver |
Contains the location of the federated connector logic, there can
be only one <driver> node in the configuration file. The driver can have the
following attributes: class – this attribute is dependent on the type. When set to “COMâ€, class indicates the CLSID of the COM object to create. When set of “.netâ€, class indicates the class name of the .net object to create. module – only required for .net, indicates the .dll that contains the class indicated in the class attribute. |
The connector logic is stored in a DLL implemented in either .net or a language that supports the creation of COM objects. This DLL is referenced in the configuration file under the <driver> section. You must provide the information about the type, class and module of the connector logic.