Page tree
Skip to end of metadata
Go to start of metadata

Status

FunctionalityStable
Support statusSupported
Support provided byEvolveum
OriginIdentity Connector Framework (Sun), many improvements by Evolveum
Target systemsGeneric database table (JDBC)

Description

Generic connector for simple database tables.

Protocol

Database-specific. Connector is using JDBC.

Framework

ConnId 1.4.x

Bundle name

com.evolveum.polygon.connector-databasetable

Connector name

org.identityconnectors.databasetable.DatabaseTableConnector

Additional requirements

Requires correct JDBC driver to be present on classpath

Capabilities and Features

SchemaYES

Provisioning

YES


Live Synchronization

YES

Using last modification timestamps

Password

YES


Activation

SIMULATED

Configured capability
ScriptingNO

History

This is almost entirely the original version from Sun ICF.

Versions

Version

Origin

Binary

Sources

Build Date

Framework version

Description

1.1.0.e6296

OpenICF trunk version, built and tested by Evolveum

download jar

OpenICF: trunk, revision 6296

Jan 2013


Well tested (now obsolete)

1.4.0.49Evolveumdownload jarEvolveum OpenICF git repository (tag connector-databasetable-v1.4.0.49)16 Jan 2015
Bundled with midPoint.
1.4.2.0Evolveumdownload jarEvolveum OpenICF git repository (tag connector-databasetable-v1.4.2.0)June 20161.4.2.0Current version. Bundled with midPoint 3.4.
1.4.3.0Evolveumdownload jarEvolveum OpenICF git repository (tag connector-databasetable-v1.4.3.0)October 20181.4.2.0Sync Order Column (contributed by Martin Lizner)
Current version. Bundled with midPoint 3.9.

Interoperability

This connector is supposed to work with all relational databases that follow the SQL standard and that provide a JDBC driver. The driver is not  part of the connector distribution (except for PostgreSQL driver, which is distributed with midPoint). The deployer is responsible for using correct JDBC driver.

Support

Only standard SQL behavior is supported. This means standard SQL operations and standard database schemas. Non-standard database operations and vendor-specific behavior is not supported.

Problems originating in JDBC driver, problem that are caused by non-compliance to SQL standard or vendor-specific behavior are not  covered by the support.

The bundled support does not include support for any specific database server. Support for specific database servers needs to be explicitly negotiated in the support contract.

Documentation

Resource Examples

Notes

DatabaseTable connector now assumes that UID is the same as NAME. See https://jira.evolveum.com/browse/MID-1127.

The following two configuration properties were reported to resolve problems with Oracle DATE attribute

<icfsdbt:nativeTimestamps>true</icfsdbt:nativeTimestamps>
<icfsdbt:allNative>true</icfsdbt:allNative>

In addition, the DATE column must be provisioned as string with correct formatting, e.g.: return new Date().format("yyyy-MM-dd HH:mm:ss"), otherwise "ORA-01861: literal does not match format string" occurs.

  • No labels