title | description | titleSuffix | ms.author | author | ms.service | ms.subservice | ms.topic | ms.custom | ms.date |
---|---|---|---|---|---|---|---|---|---|
Copy data from Oracle Eloqua (Preview) |
Learn how to copy data from Oracle Eloqua to supported sink data stores using a copy activity in an Azure Data Factory or Synapse Analytics pipeline. |
Azure Data Factory & Azure Synapse |
jianleishen |
jianleishen |
data-factory |
data-movement |
conceptual |
synapse |
09/09/2021 |
[!INCLUDEappliesto-adf-asa-md]
This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Oracle Eloqua. It builds on the copy activity overview article that presents a general overview of copy activity.
Important
This connector is currently in preview. You can try it out and provide feedback. If you want to take a dependency on preview connectors in your solution, please contact Azure support.
This Oracle Eloqua connector is supported for the following activities:
You can copy data from Oracle Eloqua to any supported sink data store. For a list of data stores that are supported as sources/sinks by the copy activity, see the Supported data stores table.
The service provides a built-in driver to enable connectivity, therefore you don't need to manually install any driver using this connector.
[!INCLUDE data-factory-v2-connector-get-started]
Use the following steps to create a linked service to Oracle Eloqua in the Azure portal UI.
-
Browse to the Manage tab in your Azure Data Factory or Synapse workspace and select Linked Services, then click New:
:::image type="content" source="media/doc-common-process/new-linked-service.png" alt-text="Screenshot of creating a new linked service with Azure Data Factory UI.":::
:::image type="content" source="media/doc-common-process/new-linked-service-synapse.png" alt-text="Screenshot of creating a new linked service with Azure Synapse UI.":::
-
Search for Oracle and select the Oracle Eloqua connector.
:::image type="content" source="media/connector-oracle-eloqua/oracle-eloqua-connector.png" alt-text="Screenshot of the Oracle Eloqua connector.":::
-
Configure the service details, test the connection, and create the new linked service.
:::image type="content" source="media/connector-oracle-eloqua/configure-oracle-eloqua-linked-service.png" alt-text="Screenshot of linked service configuration for Oracle Eloqua.":::
The following sections provide details about properties that are used to define Data Factory entities specific to Oracle Eloqua connector.
The following properties are supported for Oracle Eloqua linked service:
Property | Description | Required |
---|---|---|
type | The type property must be set to: Eloqua | Yes |
endpoint | The endpoint of the Eloqua server. Eloqua supports multiple data centers, to determine your endpoint, login to https://login.eloqua.com with your credential, then copy the base URL portion from the redirected URL with the pattern of xxx.xxx.eloqua.com . |
Yes |
username | The site name and user name of your Eloqua account in the form: SiteName\Username e.g. Eloqua\Alice . |
Yes |
password | The password corresponding to the user name. Mark this field as a SecureString to store it securely, or reference a secret stored in Azure Key Vault. | Yes |
useEncryptedEndpoints | Specifies whether the data source endpoints are encrypted using HTTPS. The default value is true. | No |
useHostVerification | Specifies whether to require the host name in the server's certificate to match the host name of the server when connecting over TLS. The default value is true. | No |
usePeerVerification | Specifies whether to verify the identity of the server when connecting over TLS. The default value is true. | No |
Example:
{
"name": "EloquaLinkedService",
"properties": {
"type": "Eloqua",
"typeProperties": {
"endpoint" : "<base URL e.g. xxx.xxx.eloqua.com>",
"username" : "<site name>\\<user name e.g. Eloqua\\Alice>",
"password": {
"type": "SecureString",
"value": "<password>"
}
}
}
}
For a full list of sections and properties available for defining datasets, see the datasets article. This section provides a list of properties supported by Oracle Eloqua dataset.
To copy data from Oracle Eloqua, set the type property of the dataset to EloquaObject. The following properties are supported:
Property | Description | Required |
---|---|---|
type | The type property of the dataset must be set to: EloquaObject | Yes |
tableName | Name of the table. | No (if "query" in activity source is specified) |
Example
{
"name": "EloquaDataset",
"properties": {
"type": "EloquaObject",
"typeProperties": {},
"schema": [],
"linkedServiceName": {
"referenceName": "<Eloqua linked service name>",
"type": "LinkedServiceReference"
}
}
}
For a full list of sections and properties available for defining activities, see the Pipelines article. This section provides a list of properties supported by Oracle Eloqua source.
To copy data from Oracle Eloqua, set the source type in the copy activity to EloquaSource. The following properties are supported in the copy activity source section:
Property | Description | Required |
---|---|---|
type | The type property of the copy activity source must be set to: EloquaSource | Yes |
query | Use the custom SQL query to read data. For example: "SELECT * FROM Accounts" . |
No (if "tableName" in dataset is specified) |
Example:
"activities":[
{
"name": "CopyFromEloqua",
"type": "Copy",
"inputs": [
{
"referenceName": "<Eloqua input dataset name>",
"type": "DatasetReference"
}
],
"outputs": [
{
"referenceName": "<output dataset name>",
"type": "DatasetReference"
}
],
"typeProperties": {
"source": {
"type": "EloquaSource",
"query": "SELECT * FROM Accounts"
},
"sink": {
"type": "<sink type>"
}
}
}
]
To learn details about the properties, check Lookup activity.
For a list of supported data stores in the service, see supported data stores.