> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/organizational-setup/connector-onboarding-guide/spotfire.md).

# Spotfire

This guide sets up the Spotfire connector. Datalogz extracts Spotfire metadata directly from the underlying Oracle repository database; support for other repository database types is not available at this time. Datalogz reads metadata only.

### Before you start

Have the following ready, and decide whether you will connect via **hostname and Service Name/SID** or via **DSN**:

* The **hostname** of the database server.
* A database **username and password** with access to the Spotfire repository.
* The Oracle **Service Name or SID** (for hostname connections) or the **DSN**.
* Optionally, the Oracle **protocol** (TCP or TCPS for SSL).

### Create the connector in Control Tower

1. Sign in to Datalogz Control Tower and go to **Settings > BI Connectors**.
2. Click **New Connector** and select **Spotfire**.
3. Enter the connection details for your chosen method (see the parameter reference below), then click **Connect**.
4. Enter a **Connector Name** and select the snapshot frequency (for example Daily or Weekly).
5. Click **Next**, then **Confirm and Finish**.

### Parameter reference

| Parameter          | Description                                                                                                           |
| ------------------ | --------------------------------------------------------------------------------------------------------------------- |
| Username           | The database user for the Oracle repository (not your Spotfire user). Must have read access to the Spotfire metadata. |
| Password           | The password for that database user.                                                                                  |
| Hostname           | The network address (domain name or IP) of the database server.                                                       |
| Protocol           | The communication method used to reach the database. TCPS enables SSL/TLS encryption.                                 |
| Service Name / SID | Oracle identifiers for the database instance. Service Name is the modern, preferred option; SID is the older form.    |
| DSN                | For DSN connections: the data source name configured for the repository database.                                     |
| Is SSL Connection? | Whether communication with the database is encrypted using SSL/TLS.                                                   |

For questions or help with this setup, contact <support@datalogz.io>.


---

# 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.datalogz.io/guides/organizational-setup/connector-onboarding-guide/spotfire.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.