> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/developers-guide/ovaledge-connectors-sdk-for-java.md).

# OvalEdge Connectors SDK for Java

Connectors serve as interfaces that integrate external data sources with the application. They enable metadata extraction, cataloging, and visualization from systems such as databases, reporting platforms, ETL tools, and file systems, using supported protocols like REST APIs, JDBC, SDKs, and others.

Users can leverage prebuilt [connectors](https://docs.ovaledge.com/connectors/connector-repositories) to integrate with commonly used data sources. If a suitable connector is not available for a user-specific use case, they can develop a custom connector using the OvalEdge Connector SDK.

The OvalEdge Connectors Software Development Kit (SDK) provides a standardized framework for building custom connectors to integrate unsupported systems with OvalEdge. Using the SDK, connectors can retrieve metadata, catalog assets, and enable data discovery across diverse platforms.

**Repository:**[ https://github.com/ovaledge/oe\_csp\_sdk](https://github.com/ovaledge/oe_csp_sdk)

This repository includes a ready-to-use SDK template, a unified API for connector testing, reference implementations (such as MonetDB and AWS Console connectors), and scaffolding tools to accelerate connector development. It also provides comprehensive end-user documentation to guide users through developing, testing, and deploying connectors independently.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release7.2/developers-guide/ovaledge-connectors-sdk-for-java.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.