Connecting a Database Table to DivePort

The example assumes that system authentication is used for the database user.

To respecify an existing database table:

1. On the DivePort toolbar, select ADMIN > Input Tables.

   The Input Tables page opens.

2. Click New.

   The Add Input Table dialog box opens.

   

3. Enter the table Name as defined in the database.

4. Optionally, clear the Record creation and modification times check box, and then click OK.

   The following files are added to the DI_Solution\webdata\<diveport>\tables subdirectory:

   • <tablename>.txt
   • <tablename>.xml

   NOTE: The created by, created at, updated by, and updated at attributes do not appear in the list of attributes in the Input Table Settings dialog box, but they do appear in the Table, and in the Edit Input Table Editor dialog box.

5. Add the back-end configuration information to the xml file directly below the <repository-infos> tag. Specify the:

   • ODBCSOURCE: The system Data Source name configured on the System DSN tab in the ODBC driver.
   • TABLENAME: The name of the table as defined in the database.
   • PRIMARYKEYCOLUMN: The column that is indicated as the Primary Key in the table constraints.

   For example:

   <?xml version="1.0"?>

   <repository-database version="3.0">

   <repository>

   <repository-infos>

   <repository-info name="backend" value="DiveLineSQL"/>

   <repository-info name="backend-config" value="{";source";:";ODBCSOURCE";,"; table;:;TABLENAME;}"/>

   <repository-info name="version" value="1"/>

   </repostitory=infos>

   <repository-keys>

   <repository-key>PRIMARYKEYCOLUMN</repository-key>

   </repository-keys>

   <repository-attributes>

   <repository-attribute name="id">

   <repository-attribute-infos>

   <repository-attribute-info name="highest-seen" value="4"/>

   </repository-attribute-infos>

   </repository-attributes>

   </repository>

   <repository-roles default="privuser">

   <member type="guest" role="user"/>

   </repository-roles>

   </repository-database>

    

This example assumes database authentication is in use. Therefore, a username and password are required.

To respecify an existing database table:

1. On the DivePort toolbar, select ADMIN > Input Tables.

   The Input Tables page opens.

2. Select New.

   The Add Input Table dialog box opens.

   

3. Enter the table Name as defined in the database.

4. Select the Record creation and modification times check box, and then click OK.

   The following files are added to the DI_Solution\webdata\<diveport>\tables subdirectory:

   • <tablename>.txt
   • <tablename>.xml

   NOTE: The created by, created at, updated by, and updated at attributes do not appear in the list of attributes in the Input Table Settings dialog box, but they do appear in the Table, and in the Edit Input Table Editor dialog box.

5. Add a command string that contains the back end configuration information to the xml file directly below the <repository-infos> tag. The command string includes DSN= and specifies the attributes required by the ODBC driver. For example, if the source is a Microsoft SQL server, the required attributes and format are:

   • SOURCENAME: The system Data Source name configured on the System DSN tab in the ODBC driver.
   • USERNAME: The userid.
   • PASSWORD: The password string for the userid.
   • TABLENAME: The name of the table as defined in the database.
   • PRIMARYKEYCOLUMN: The column that is indicated as the Primary Key in the table constraints.

    
   

   For example:

   <?xml version="1.0"?>

   <repository-database version="3.0">

   <repository>

   <repository-infos>

   <repository-info name="backend" value="DiveLineSQL"/>

   <repository-info name="backend-config" value="{";connect_string";:";DSN=SOURCENAME; UID=USERNAME;PWD=PASSWORD";,";table";:"; TABLENAME";}"/>

   </repostitory=infos>

   <repository-keys>

   <repository-key>PRIMARYKEYCOLUMN</repository-key>

   </repository-keys>

   <repository-attributes>

   </repository-attributes>

   </repository>

   <repository-roles default="privuser">

   <member type="guest" role="user"/>

   </repository-roles>

   </repository-database>

    

   TIP: When specifying the connect string, required attributes and syntax varies by database vendor.