Connector Configuration
Drupal Configuration
Drupal Instance Settings
Configuration Options for the setup of the connection to the target Drupal instance.
| Name | Description |
|---|---|
Use Authentication |
Flag to connect to Drupal with authentication. |
Drupal Username |
Username of the technical user. This user must be able to login to Drupal and see all needed content. |
Drupal Password |
Password of the technical user. |
Drupal URL |
URL of the Drupal instance to connect to. |
Use Proxy |
Flag to connect to Drupal via a proxy. |
Proxy URL |
URL for targeting Proxy. |
Use Proxy Authentication |
Flag to connect to proxy with authentication. |
Proxy Username |
Username of the authenticating user against proxy. |
Proxy Password |
Password of the authenticating user against proxy. |
Drupal Comment Settings
Configuration Options on how to treat comments
| Name | Description |
|---|---|
Enable Comments |
If true, comments are crawled from Drupal. |
Embed Comments |
If true, Comments are embedded in the content and metadata of their parent. |
Comment Type include List |
Included Drupal Comment Types: If this list is empty all non-excluded comment types will be processed by the connector. Otherwise, only those types in this list. |
Comment Type exclude List |
Excluded Drupal Comment Types: Comment types in this list will not be processed. |
Drupal Connection Settings
Configuration options for fine-tuning the Http connection parameters.
| Name | Description |
|---|---|
Max. Connections |
Maximum number of open connections. |
Max. Requests per Second |
Maximum number of requests per second. |
Request Timeout in Milliseconds |
Timeout of requests to Drupal. |
Socket Timeout in Milliseconds |
Timeout of the socket connected to Drupal. |
Drupal Node Settings
Configuration Options for node types.
| Name | Description |
|---|---|
Node Type include List |
Included Drupal Node Types: If this list is empty all non-excluded node types will be processed by the connector. Otherwise, only those types in this list. |
Node Type exclude List |
Excluded Drupal Node Types: Node types in this list will not be processed. |
Drupal Pagination Settings
Configuration options for paginated API requests.
| Name | Description |
|---|---|
Node Page Size |
Number of Nodes requested with a single call. |
Comment Page Size |
Number of Comments requested with a single call. |
Attachment Page Size |
Number of Attachments requested with a single call. |
User Page Size |
Number of Users requested with a single call. |
Role Page Size |
Number of Roles requested with a single call. |
Type Page Size |
Number of Types requested with a single call. |
Lucidworks Fusion 5 Configuration
Instance Configuration
Configuration options for the setup of the connection to the target Fusion instance including authentication/authorization settings.
| Setting | Description |
|---|---|
Technical User |
Username for the technical account with at least the permissions: |
Password |
Password for the specified technical account. The connector will store the value encrypted. |
URL |
URL to the target Fusion instance. |
Use Proxy |
If enabled, the target Fusion instance will be connected through a proxy. |
Proxy URL |
URL of the proxy server including protocol, host and port. |
Proxy Authentication |
If enabled, the connector uses the specified credentials to authenticate towards the proxy. |
Proxy Username |
Proxy authentication username. |
Proxy Password |
Proxy authentication password. The connector will store the value encrypted. |
Indexing Configuration
Configuration options specifying the target indexing pipeline and Solr index for content ingestion.
| Setting | Description |
|---|---|
Indexing Pipeline |
Name of the indexing pipeline. |
Collection Name |
Name of the target Solr index for content ingestion. |
Data Source Configuration
Configuration options specifying the target data source.
| Setting | Description |
|---|---|
Data Source ID |
ID of the Data Source ID. The Connector assigns for the processed documents and principals an ID for the Data Source in the field _lw_data_source_s. |
HTTP Connection Configuration
Configuration options for fine-tuning the Http connection parameters.
| Setting | Description |
|---|---|
Session Timeout |
The connector uses session-based authentication via cookie. This option specifies the session timeout for preemptively re-creating the session. The default value is set to 1 hour which is also the default defined in Fusion. |
Max. Requests per Seconds |
Max. number of requests per seconds. |
Connection Timeout |
Timeout value after the connection should be closed regardless of its current state. |
Socket Timeout |
Timeout value waiting for data after establishing the connection. |
Max. Number of Retries |
Max. number of retries for failed requests. |
General Configuration
Database Configuration
| Setting | Description |
|---|---|
URL |
JDBC URL for the target database. Out of the box, the connector will use H2 file database. For productive usage, use PostgreSQL specifying the URL in format: |
Username |
Database Username to read and write to database. |
Password |
Database Password for the specified user |
Traversal Configuration
| Setting | Description |
|---|---|
Traversal History Length |
Max. number of traversals to store in the history. Once the limit is exceeded, the connector will automatically remove oldest entries in the history. (default: 100) |
Number of Traversal Workers |
Number of workers to execute the traversal in parallel. Increasing this value might improve the performance, but will footprint higher memory consumption. It is recommended to keep the default value. (default: 10) |
Traversal Job Poll Interval |
Interval between the workers to be triggered to fetch and process the next tasks. (default: 10ms) |
Completion Timeout |
If the search engine indexes the items asynchronously, there might be some processing still in-flight during the completion process of a traversal. This value specifies the timeout value until all asynchronous callbacks are expected to return before completing the traversal. (default: 10m) |
Principal Aliaser Configuration
Principal Aliasing is applied on user information as part of Content ACL processing during Content Synchronization and Principal processing during Principal Synchronization. It’s purpose is to map external source system user to the corresponding user in search engines domain. You can configure a list of aliasers in the connector which will be applied in sequence and in order on user ACEs and user principals. The Connector supports following custom aliasing mechanism.
Custom Aliaser Disabled
If the Custom Aliaser checkbox is not selected, the connector will process user information on ACE and user principals unchanged to Search Engine. If all relevant users in the source system can be found with the same identifier in the search engine, this setup is sufficient to reflect the same secure search experience in the search engine as defined by the policy in the source system. The connector uses this option as default to process user information.
Custom Aliaser Enabled
If custom aliasing is enable then there are four types of aliaser avaialble:
Static Mapping Aliaser
Static Mapping entries which will be applied to all user processed by the connector as part of the document ACL and principal information. If this type of aliaser is configured any user token without a mapping entry will be dropped from being synchronized to the search engine.
| Setting | Description |
|---|---|
Mappings |
Mapping Entry with |
Simple XML Table Aliaser
Static mapping table which can be uploaded as XML file. The connector uses the uploaded file as lookup table to map a user in the source system to a user in the search engine. Users missing a record in the file will be dropped from the ACE and during Principal Synchronization. This option is only recommended for environment with a manageable amount of users as for each user the corresponding mapping entry needs to be specified in the file.
| Setting | Description |
|---|---|
XML Mapping File |
Browse and upload or drag and drop. |
Sample XML mapping file:
<?xml version="1.0" encoding="UTF-8"?>
<storeddata>
<entry keyValue="user1">user1@raytion.com</entry>
<entry keyValue="user2">user2@raytion.com</entry>
<entry keyValue="user3">user3@raytion.com</entry>
</storeddata>
Regex Replacer Aliaser
Regex Replacer Aliaser computes aliases based on a regular expression. Principals that match the regular expression are replaced by the Substitution String.
| Setting | Description |
|---|---|
Pattern |
The regular expression to match, this is the part that will be replaced. If braces (…) are used in the pattern then the matched value can be retrieved using $1 |
Substitute String |
String to replace the matching part of the find string. Matched value is accessed by employing $1 |
Regex Extractor Aliaser
Regex Extractor Aliaser computes aliases based on a regular expression. Principals that match the regular expression are inserted into the Insert-Into String.
| Setting | Description |
|---|---|
Pattern |
The regular expression to match, this is the part that will be inserted into the new value. If braces (…) are used in the pattern then the matched value can be retrieved using $$ |
Insert-Into String |
String to replace the matching part of the pattern. Matched value is accessed by employing $$ |
LDAP Aliaser
Ldap Aliaser searches for an LDAP entry with the requested name in the input value and returns the specified output attribute.
| Setting | Description |
|---|---|
Host |
Fully Qualified Domain Name of an LDAP server |
Port |
Port to use for LDAP connection, defaults are 389/636 or (recommended) 3268/3269 for simple/SSL |
AccountDN |
AccountDN for bind to LDAP |
Password |
Password part of credentials |
Input Field |
The Active Directory attribute name for this equality filter |
Search Root DN |
Distinguished Name of the subtree which is searched. The smaller the subtree the better the performance but the higher the chance of encountering principals which are not part of this subtree |
Output Field |
Attribute that should be returned in result entries |