# Oracle Sales

<!-- BEGIN GENERATED:intro -->

The Oracle Sales connector is a [Palantir-provided driver](../../data-integration/foundry-provided-drivers/index.md) for Oracle Sales.

To create a new Oracle Sales source, follow the [standard setup flow for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#setup), then use the sections below for Oracle Sales-specific configuration and networking. For the complete property reference, see the [official Oracle Sales driver documentation ↗](https://cdn.cdata.com/help/EOK/jdbc/pg_connectionj.htm).

<!-- END GENERATED:intro -->

<!-- BEGIN GENERATED:capabilities -->

## Supported capabilities

| Capability | Status |
|---|---|
| Exploration | 🟢 Generally available |
| Batch syncs | 🟢 Generally available |
| Incremental | 🟢 Generally available |

<!-- END GENERATED:capabilities -->

<!-- BEGIN GENERATED:configuration -->

## Configuration

The properties below are mandatory or recommended.

| Property | Required? | Description | Default |
|---|---|---|---|
| [`HostURL` ↗](https://cdn.cdata.com/help/EOK/jdbc/RSBOracleSalesCloud_p_HostURL.htm) | Mandatory | The URL to the Oracle Sales server used for logging in. | `https://my.host.oraclecloud.com` |
| [`Password` ↗](https://cdn.cdata.com/help/EOK/jdbc/RSBOracleSalesCloud_p_Password.htm) | Mandatory | Specifies the password of the authenticating user account. | — |
| [`Username` ↗](https://cdn.cdata.com/help/EOK/jdbc/RSBOracleSalesCloud_p_Username.htm) | Mandatory | The username of the Oracle Sales account used to authenticate to the server. | — |

<!-- END GENERATED:configuration -->

<!-- BEGIN GENERATED:networking -->

## Networking

The table below lists the domains that the source must be able to access to run.

For each domain, add a corresponding [egress policy](../../administration/configure-egress/index.md). If the source is hosted on-premises and not directly reachable from Foundry, use an [agent proxy egress policy](../../administration/configure-egress/index.md#agent-proxy-egress-policies) instead. The agent host itself must also be able to reach the listed domains. See [using an agent as a proxy](../../data-connection/agent-proxy/index.md) for details.

| Domain  | Required |
|--- |--- |
| \<HostURL> | Always. HostURL connection property |

<!-- END GENERATED:networking -->