Connector guides

The current tapstate preview publishes MySQL, PostgreSQL, Oracle, SQL Server, and Db2 as source engines and MongoDB as the operational-state target. Sources support an initial snapshot followed by CDC. The Quickstart demonstrates one pipeline that assembles MySQL orders and PostgreSQL shipments into a MongoDB document.

Select a current connector to prepare its external system and author the connection resource. Before using a real endpoint, run a server-side connection test.

6 current connectors·GA 5Preview 1

Current connector path

Published database sources, including the Db2 preview, and the MongoDB operational-state target.

Connector	Guide maturity	Published role	Read mode
MySQL	GA	Source	Snapshot·CDC
PostgreSQL	GA	Source	Snapshot·CDC
Oracle	GA	Source	Snapshot·CDC
SQL Server	GA	Source	Snapshot·CDC
Db2	Preview	Source	Snapshot·CDC
MongoDB	GA	Target	—

Documentation status

The directory uses a status separate from Maturity:

• Current path means the connector has a published role in the current product path. MySQL, PostgreSQL, Oracle, SQL Server, and the Db2 preview are current sources; MongoDB is the current target.

Other connector preparation material is not published in this public documentation site and is not presented as a supported workflow.

GA and Preview describe guide or configuration-contract maturity. They do not change the documentation status or prove that an artifact is bundled or registered.

Maturity labels

• GA means the connector guide and configuration contract are mature.
• Preview means the guide or configuration contract can still change.

Maturity does not mean that a connector JAR is bundled with every tapstate release or that every listed role and mode is available in the current product path.

Connector distribution and lifecycle

Tapstate manages connector artifacts and licenses separately from the core server image:

• Self-hosted base images start without connector JARs. The Cloud image stages a fixed connector set separately from the core runtime.
• Quickstart automation downloads and registers MySQL, PostgreSQL, and MongoDB. Register Oracle, SQL Server, or Db2 explicitly when needed.
• Persistence across upgrades keeps registered connector metadata and bytes in the backend store. Re-registering identical bytes is an idempotent no-op. Treat a different JAR as a connector upgrade: retain the old artifact, test the replacement, and plan any affected pipeline restart.
• Offline seeding lets an operator mount pre-staged JARs in TAPSTATE_CONNECTORS_SEED_DIR for registration at startup. In a cluster, use one entry member for registration to avoid concurrent-registration ambiguity.

See Register and test connectors for CLI syntax, remote mirrors, and offline workflows.

How to read roles and modes

Hover a label or its information icon to see its exact meaning.

• Source reads from the listed system in the shown mode.
• Target writes data to the listed system.
• Snapshot reads the selected data once. CDC starts with existing data, then captures later committed changes.
• A dash means a read mode does not apply to the published target role.