Spanish English German Portuguese
Spanish English German Portuguese

JDBC Connector (Source and Sink)

JDBC Connector (Source and Sink)

att_0_for_1847165010.png

Connector to exchange records, tables, collections, and data changes between GlobalSuite and JDBC in the enabled scenarios.

Tags: Databases | Source and Sink

Tool or system

JDBC

Tool manufacturer

Standard / open protocol

Connector provider

Confluent, Inc

Connector name

JDBC Connector (Source and Sink)

Connector type

Source and Sink

Tags

Databases | Source and Sink

Information it handles

records, tables, collections, and data changes

Details

The JDBC Connector (Source and Sink) allows exchanging information between GlobalSuite and JDBC, combining input and output flows depending on the use case.

It facilitates keeping records, tables, items, and data changes aligned in both environments, with particular application in catalog synchronization scenarios, change auditing, regulatory reporting, and eliminating manual workloads.

Features

  • Bidirectional exchange of records, tables, collections, and data changes between GlobalSuite and JDBC, according to the enabled flow.

  • Selection of tables, collections, views, or fields to synchronize only information with functional value.

  • Support for additions, modifications, and deletions when the source or target system allows it.

  • Mapping of keys, fields, and entities to maintain consistency with corporate catalogs and inventories.

  • Traceability of changes and results for auditing, reconciliation, and data quality control.

Key benefits

  • Keeps catalogs, inventories, and critical records synchronized with less manual intervention.

  • Reduces errors due to duplication or misalignment between databases and GlobalSuite processes.

  • Facilitates change auditing, information reconciliation, and regulatory reporting.

  • Allows incorporating operational information into the GRC flow without waiting for specific exports.

  • Improves data quality by working with structured sources and defined mapping rules.

Installation

Configuration note: Before activating the integration, validate credentials, permissions, functional scope, and a data test with the responsible area.

  1. Access the GlobalSuite® Marketplace and select JDBC Connector (Source and Sink).

  2. Configure the connection with JDBC: URL or endpoint, credentials, permissions, and environment.

  3. Define the direction of each flow and the functional scope: records, tables, items, and data changes, filters, and frequency.

  4. Configure field mapping for input, output, or both scenarios.

  5. Run separate tests by direction, validate results, and activate the integration.

More information

https://docs.confluent.io/kafka-connectors/jdbc/current/

Use this connector when JDBC and GlobalSuite need to exchange information in both directions, for example, for catalog synchronization, change auditing, regulatory reporting, and eliminating manual loads. It is advisable to clearly separate which data is incoming, which is outgoing, and who is responsible for resolving discrepancies.