The RDB via Tables Connector can be configured using the Aspire Admin UI. It requires the following entities to be created:

• Credential
• Connection
• Connector
• Seed

Bellow are the examples of how to create the Credential, Connection and the Seed. For the Connector please check this page.

Create Credential

1. On the Aspire Admin UI go to the credentials tab 
2. All existing credential will be list. Click on the new button 
3. Enter the new credential description. 
4. Select Rdb-Tables from the Type list.
5. Enter User and Password. Note: The password will be automatically encrypted by Aspire.

Create Connection

1. On the Aspire Admin UI go to the connections tab 
2. All existing connection will be list. Click on the new button 
3. Enter the new connection description. 
4. Select Rdb-Tables from the Type list.
5. In the "JDBC Url" field in the Properties section, enter the JDBC URL for the database to be crawled.
6. In the "JDBC Driver Jar:" field, enter the name of the JAR file containing the driver for your database.
7. In the "JDBC Driver Class" field, enter the Java class name for the driver (optional)
8. If your JDBC Driver jar does not contain all the necessary classes, you may add additional jar files in to the class path. To do this, select "Specify classpath" and enter the classpath to the jars containing the classes. The classpath may include jar files, directories or individual classes.
9. etc.

The description of all "connection" fields  can be found here.

Create Connector

For the creation of the Connector object using the Admin UI check this page

Create Seed

1. On the Aspire Admin UI go to the seeds tab 
2. All existing seeds will be list. Click on the new button 
3. Enter the new seed description. 
4. Select Group Expansion from the Type list.
5. Scope: Include/exclude lists of the seeds its identities should be crawled. Default is all seeds
   
6. Custom mapping: Configure custom mapping for specific seeds:
   1. Seed to apply the attribute mapping
   2. Type local/external:
      1. local:
         1. The attribute to be used as the identity key
      2. external:
         1. The attribute to be used as the identity key
         2. The external seed id for looking up the identity
         3. The attribute used for lookup in external seeds identities
7. Connector: The id of the connector to be used with this seed. The connector type must match the seed type.
8. Connection: The id of the connection to be used with this seed. The connection type must match the seed type.
9. Workflow: The ids of the workflows that will be executed for the documents crawled.
10. Tag: The tags of the seed, these can be used to filter the seed.
11. Policies
    1. Throttle Policy: Select the throttle policy that applies to this connection object.
    2. Routing Policies: Select the routing policies that this connection will use.