Connector Configuration
Confluence Configuration
Confluence Instance Settings
Configuration Options related to establish connection to the target Confluence instance.
| Name | Property Key | Description |
|---|---|---|
URI |
|
URI of the confluence instance to connect to. |
Enable Basic Authentication |
|
Toggles the usage of a Basic Authentication against Confluence. |
Custom Default Headers |
|
Default Headers to be added to HTTP requests to Confluence. |
Enable SSL Authentication via KeyStore |
|
Activates configuration options allowing the configuration of a KeyStore that is used to authenticate against the configured Confluence Instance via SSL. |
Basic Authentication
| Name | Property Key | Description |
|---|---|---|
Username |
|
Username to connect to Confluence. This user must be able to log into Confluence and be registered with the Raytion Confluence Plugin. |
Password |
|
Password for the user to connect to Confluence. Encryption is recommended. |
SSL Authentication
Configuration options for authenticating the Connector against Confluence via SSL with the help of a KeyStore.
| Name | Property Key | Description |
|---|---|---|
KeyStore File |
|
A KeyStore to use when connecting to Confluence. |
KeyStore Type |
|
The type of the KeyStore-file given. We strongly recommend using PKCS12, as JKS may be deprecated in a future update. |
KeyStore Password |
|
The password to access the keystore. |
Key Alias |
|
The alias from the KeyStore to use. You can leave this empty if the KeyStore only contains one alias. |
Key Password |
|
The password to access the Key Alias within the KeyStore. |
Confluence Connection Settings
Configuration Options related to fine-tuning the connection to the Confluence instance.
| Name | Property Key | Description |
|---|---|---|
Socket Timeout |
|
An inactive connection will be treated as terminated after this duration. |
Connection TTL |
|
Unused connections of the pool will be discarded after this duration. |
Requests per second |
|
Maximum amount of requests which are started towards the Confluence instance. |
Connection Pool Size |
|
Maximum number of parallel requests to Confluence. |
Batch Size |
|
Number of items that are requested in one request. |
Confluence Space Filter Settings
Configuration options determining which Confluence Spaces to crawl.
| Name | Property Key | Description |
|---|---|---|
Included Space Keys |
|
Only the Spaces with keys defined here will be crawled. If no include filters are defined, all keys are included. |
Excluded Space Keys |
|
Spaces with a key in this list will not be crawled. This overrides the key being allowed by Included Space Keys. |
Included Space Categories |
|
Only the Spaces with at least one category defined here will be crawled. However, no include filters being defined is synonymous to all categories being included. |
Excluded Space Categories |
|
Spaces with a category in this list will not be crawled. This overrides the Space being included through Included Space Keys or Included Space Categories. |
Confluence Hierarchy Cache Settings
Configuration Options determining how much and long to cache hierarchical data of Spaces and Pages.
| Name | Property Key | Description |
|---|---|---|
Cache Time To Live |
|
Maximum age of cache entries. Larger improves performance and requires more memory. |
Maximum Cache Weight |
|
Maximum cache size. Spaces and Pages weigh more the more entries they have. Larger improves performance and requires more memory. |
Confluence Type Filter Settings
Configuration Options related to which types of search targets should be generated
| Name | Property Key | Description |
|---|---|---|
User Profiles |
|
User Profile pages will become search targets, if this value is enabled. |
Labels |
|
Labels will become search targets, if this value is enabled. |
Page Contributors |
|
In addition to the creator and the last modifier of a page or blogpost, all other modifiers are queried, too. This is an expensive operation. |
Comment Handling |
|
NONE: Comments will not be indexed. INDEX_WITH_PARENT: Comments will be indexed with the parent page or blog post. INDEX_SEPARATELY: Comments will be indexed separately in an individual document. |
Drafts of Pages and Blog Posts |
|
Pages and Blog Posts in draft status will be indexed. |
Deleted Pages and Blog Posts |
|
Pages and Blog Posts in deleted status will be indexed. |
Maximum Attachment Size |
|
Attachments with a larger size will not have their content indexed. |
Ignore content file extensions |
|
Attachments with a file extension from this list will not have their content indexed but only their metadata. Entries will automatically be converted to lowercase with US locale. |
CSM Configuration
Required Configuration Properties
Optional Configuration Properties
CSM Connection Settings
Configuration options for fine-tuning the Http connection parameters.
| Name | Description |
|---|---|
Concurrent Connections |
Maximum number of concurrent open connections. |
Requests Rate |
Maximum number of requests per second. |
Connect Timeout in Milliseconds |
Timeout of the connect request. |
Socket Timeout in Milliseconds |
Timeout of the socket connected to CSM. |
Request Timeout in Milliseconds |
Timeout of a request to CSM. |
Microsoft SharePoint Configuration
Submission Repository Settings
Connector needs caching Submissions before sending them for indexing to SharePoint.
| Name | Property Key | Description |
|---|---|---|
Repository Filename |
|
Full Path of the Repository filename. Filename must end with (.db). |
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. |
Submission Repository Limit Settings (Optional)
Settings for limiting the Submission number the Repository can have, so that the used disc space is limited.
| Name | Property Key | Description |
|---|---|---|
Max. Unprocessed Submissions |
|
Maximum unprocessed Submissions inside the repository. If Submissions exceed this number then insertions are blocked until other Submissions are removed from repository. |
Max. Insertion Waiting Time |
|
Maximum insertion waiting time in case the Repository reaches the maximum size limit. After this duration the Submission will be rejected and marked as failed from the Connector. |
Repository Size Retrieval Interval |
|
Duration interval in which the connector retrieves the current number of unprocessed Submissions in the Repository. |
Submission Crawl Settings (Optional)
Settings for fetching Submissions to SharePoint.
| Name | Property Key | Description |
|---|---|---|
Crawl Trigger Size |
|
The size of cached Submissions to trigger a BCS Crawl. |
Crawl Interval |
|
Duration interval for checking if a crawl has to be triggered. |
Inserting Idle Duration |
|
Time duration that no other Submission is inserted to cache. After this time, a Crawl will be triggered even if the Trigger Size was not exceeded. |
CrawlTrigger Service Settings
CrawlTrigger Service settings for fetching Submissions to SharePoint.
| Name | Property Key | Description |
|---|---|---|
Endpoint |
|
Endpoint of the CrawlTrigger Service. |
Content Source Name |
|
Name of the content source configured in SharePoint. |
Domain |
|
User Domain for the Authentication process. |
Authentication Scheme |
|
HTTP Authentication Scheme used to authenticate with the SharePoint CrawlTrigger service. NTLM or NEGOTIATE. |
Username |
|
Username to authenticate to CrawlTrigger Service. |
Password |
|
Password to authenticate to CrawlTrigger Service. |
Connection Timeout |
|
Specifies the amount of time, in milliseconds, that the consumer will attempt to establish a connection before it times out. 0 is infinite. |
Receive Timeout |
|
Specifies the amount of time, in milliseconds, that the consumer will wait for a response before it times out. 0 is infinite. |
General Configuration
Database Configuration
| 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 |
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) |
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:
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 |