Connector Configuration
Configuration for Drupal Connector
Please note that certain settings can affect the performance of content traversals. Refer to Performance section of the FAQ for details.
Basic Settings
Instance Setup
Use these settings to specify how the connector accesses your Drupal instance. The configured Technical Account must have privileges to read the desired node types and comments.
Name |
Key |
Description |
Drupal Base URL |
|
Base URL of your Drupal instance (e.g., |
Use Authentication |
|
Enable or disable Basic Authentication. |
Username |
|
Technical Account username (with privileges). |
Password |
|
Technical Account password (can be stored encrypted). |
JSON:API Path Prefix |
|
Path prefix for JSON:API endpoints (default: |
Query Parameter for API |
|
Optional Drupal query parameter (e.g., |
Use Proxy |
|
Set to |
Proxy Base URL |
|
URL of the proxy server (e.g., |
Proxy Username |
|
Username for proxy authentication (if enabled). |
Proxy Password |
|
Password for proxy authentication (can be stored encrypted). |
Use Proxy Authentication |
|
Enable or disable authentication for the proxy (if |
Comments
Enable or disable the traversal of Drupal comments, including embedded comments within nodes.
Name |
Key |
Description |
Enable Comments |
|
Set to |
Enable Embedded |
|
Set to |
Included Comment Types |
|
Array of specific comment types to include (e.g., |
Excluded Comment Types |
|
Array of comment types to exclude (e.g., |
Node Type
Only nodes are traversed, but the connector will not auto-discover node types.
You must explicitly define which node types (e.g., page, article) are to be included.
Name |
Key |
Description |
Content Types File |
|
Upload a file listing the Drupal content types to traverse (one per line). Example: |
Advanced Settings
Only Published Content
Limit the connector to traverse only published content if desired.
Name |
Key |
Description |
Include Only Published Content |
|
Set to |
Language
Configure language options for nodes in a multi-language Drupal setup.
Name |
Key |
Description |
Default Language |
|
Primary content language (e.g., |
Additional Languages |
|
Specify additional languages as an array, e.g., |
Enable Other Languages |
|
Set to |
Language Filter Name |
|
Query parameter or field name for filtering by language (e.g., |
Pagination
Configure pagination for nodes, comments, attachments, roles, types, and users to optimize performance.
Name |
Key |
Description |
Node Page Size |
|
Number of nodes fetched per page (default: 50). |
Comment Page Size |
|
Number of comments fetched per page (default: 50). |
Attachment Page Size |
|
Number of attachments fetched per page (default: 50). |
Role Page Size |
|
Number of roles fetched per page (default: 50). |
Type Page Size |
|
Number of content types fetched per page (default: 50). |
User Page Size |
|
Number of users fetched per page (default: 50). |
Connection
Configure the HTTP client for timeouts, retries, and connection limits.
Name |
Key |
Description |
Max Connections |
|
Maximum number of open HTTP connections. |
Max Requests Per Second |
|
Limit on the number of requests sent per second (e.g., 50). |
Request Timeout |
|
Time (in ms) to wait for a request to complete (e.g., |
Socket Timeout |
|
Inactivity timeout for a socket (e.g., |
ServiceNow AI Search Configuration
Instance Configuration
Configuration options related to specifying the ServiceNow AI Search instance.
| Setting | Description |
|---|---|
ServiceNow Instance Hostname |
Host Name of your ServiceNow Platform e.g. |
AI Search External Content User |
Username of the technical user with at least the role |
AI Search External Content User Password |
Password for the specified technical user. |
User Proxy |
If enabled, the connection to ServiceNow will be established through an HTTP/HTTPS proxy. |
Proxy Endpoint |
Target proxy URL including protocol, host and port. |
Connection Configuration (Optional)
Configuration options for fine-tuning the Http connection parameters.
| Setting | Description |
|---|---|
Requests per second |
The Number of requests sent per second. The default is set to |
Connection Timeout |
Timeout value for establishing a connection to host. Modify the value only if you modified system property |
Max. Number of Connections |
Max. number of allowed connections maintained by the connection manager. Modify the value only if you modified system property |
Payload Configuration (Optional)
Configuration options for fine-tuning AI Search payload constraints. Each batch must fulfill both the size constraint and the count constraint.
| Setting | Description |
|---|---|
Max. Content Batch Payload Size |
Max. batch payload size for ingesting documents. Modify the value only if you modified system property |
Max. Principal Batch Payload Size |
Max. batch payload size for mapping users. Modify the value only if you modified system property |
Max. Content Batch Item Count |
Max. number of items per batch for ingesting documents. |
Max. Principal Batch Item Count |
Max. number of users per batch for mapping users. |
General Configuration
Database Configuration
| Name | Property Key | Description |
|---|---|---|
Configuration Type |
|
Supported are PostgreSQL, MS SQL Server, H2 and JDBC URL configuration. |
JDBC URL
| Name | Property Key | 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 |
PostgreSQL
| Name | Property Key | Description |
|---|---|---|
Host |
|
Domain name or IP address of the database server. |
Port |
|
Specifies the port number PostgreSQL is listening on, default is 5432. |
Database Name |
|
Name of the database. |
Username |
|
Username to authenticate with. The regarding user has to have read and write permissions to the database. |
Password |
|
Password of the configured database user. |
Add Custom Parameter |
|
Enables the configuration of additional parameters. |
H2
| Name | Property Key | Description |
|---|---|---|
Filename |
|
Name for file-based H2 database. Name must be at least three characters long and must not contain a semicolon. May include absolute or relative path to the database file. |
Username |
|
Username to authenticate with. The regarding user has to have read and write permissions to the database. |
Password |
|
Password of the configured database user. |
Add Custom Parameter |
|
Enables the configuration of additional parameters. |
MS SQL Server
| Name | Property Key | Description |
|---|---|---|
Host |
|
Domain name or IP address of the database server. Instance to connect to on server can be specified by '‹server_name>|<instance_name>'. |
Port |
|
Specifies the port number MS SQL Server is listening on, default is 1433. |
Database Name |
|
Name of the database. |
Username |
|
Username to authenticate with. The regarding user has to have read and write permissions to the database. |
Password |
|
Password of the configured database user. |
Add Custom Parameter |
|
Enables the configuration of additional parameters. |
Oracle
| Name | Property Key | Description |
|---|---|---|
Host |
|
Domain name or IP address of the database server. Instance to connect to on server can be specified by '‹server_name>|<instance_name>'. |
Port |
|
Specifies the port number Oracle is listening on, default is 1521. |
Username |
|
Username to authenticate with. The regarding user has to have read and write permissions to the database. |
Password |
|
Password of the configured database user. |
Connection Type |
|
Specifies whether to connect to the database via the instance’s unique SID or a service name. |
Service |
|
A name of a given service / a TNS alias of the Oracle database instance. |
Traversal Configuration
| Name | Property Key | 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) |
Include Checksum |
|
If enabled, any changes made to the pipeline e.g. configuration, the subsequent incremental run triggers a refeed of all items. |
Change Processing Interval |
|
Interval between change processing traversals. |
Resume on Start |
|
If enabled, any traversals in paused state are automatically resumed after the connector restart. Otherwise, the traversal remains in paused state. |
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) |
Executor Size |
|
The executor size restricts the max. number of concurrent running traversals. |
Queue Size |
|
The queue size restricts the max. number of queued traversals. If the value is exceeded, the connector rejects further traversal requests until the queue size is below the configured size. |
Traversal Jobs
| Name | Property Key | Description |
|---|---|---|
Job Timeout Check Frequency |
|
Configures how often the connector checks for timed out jobs. |
Job Timeout |
|
The duration for which a job can stay idle before it is timed out. |
Job Cache Size |
|
Max. cache size of Jobs waiting for processing in memory. When cache is empty, next batch is fetched. |
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:
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.
| Name | 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.
| Name | Property Key | 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.
| Name | PropertyKey | 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.
| Name | Property Key | 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 |