The RDB via Table connector crawls content from any relational database that can be accessed using JDBC.
- The connector extracts data based on SQL statements and submits this data into Aspire for processing
- The connector directly extracts the data. This means that there is not a fetch data phase. However, if your database includes references to external data (say URLs to web sites or paths of external files), then a fetch stage may be invoked.
Introduction
The RDB via Table connector features include the following:
- Connects to a database server using JDBC drivers (which must be downloaded separately)
- Performs full crawling
- Performs incremental crawling, so that only new or updated documents are indexed, using tables to hold identifiers of updated content
- Fetches data from the database using SQL statements
- Is search engine independent
- Runs from any machine with access to the given database
Content Retrieved by the Connector
The content retrieved by the connector is defined entirely using SQL statements, so you can select all or subsets of columns from one or more tables. Initially, the data is inserted into Aspire using the returned column names, but this may be changed by further Aspire processing..
Environment and Access Requirements
Repository Support
DBC Drivers
The RDB via Table connects to databases via JDBC, so you'll need the appropriate JDBC client (driver) JAR file for the database you want to connect to. These are available for most (if not all) major database vendors, and your first port of call for the driver should be the vendor's website.
Account Privileges
Not relevant here
Environment Requirements
No special requirements here
Framework and Connector Features
Framework Features
| Name | Supported |
|---|---|
| Content Crawling | yes |
| Identity Crawling | no |
| Snapshot-based Incremental s | yes |
| Non-snapshot-based Incremental s | no |
| Document Hierarchy | no |
Connector Features
The Group Expansion connector has the following features:
- Seeds filtering using include and exclude lists.
- Custom mapping configuration for selected seeds
Content Crawled
The Group Expansion connector is able to crawl the following objects:
| Name | Type | Relevant Metadata | Content Fetch & Extraction | Description |
|---|---|---|---|---|
| Seed | container | NA | The identities are grouped by seeds and we crawl identities belonging to seeds | |
| Identity |
| NA | The identities with expanded groups |
Limitations
No limitations defined
Overview
Content Tools
Copyright © 2024 Accenture
