Breyta

Deila með

Copy data from Oracle Eloqua using Azure Data Factory or Synapse Analytics (Preview)

  • Grein

APPLIES TO: Azure Data Factory Azure Synapse Analytics

Tip

Try out Data Factory in Microsoft Fabric, an all-in-one analytics solution for enterprises. Microsoft Fabric covers everything from data movement to data science, real-time analytics, business intelligence, and reporting. Learn how to start a new trial for free!

Important

This connector will be deprecated on December 31, 2024. You are recommended to migrate to ODBC connector by installing a driver before that date.

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.

Supported capabilities

This Oracle Eloqua connector is supported for the following capabilities:

Supported capabilities IR
Copy activity (source/-) ① ②
Lookup activity ① ②

① Azure integration runtime ② Self-hosted integration runtime

For a list of data stores that are supported as sources/sinks, 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.

Getting started

To perform the Copy activity with a pipeline, you can use one of the following tools or SDKs:

Create a linked service to Oracle Eloqua using UI

Use the following steps to create a linked service to Oracle Eloqua in the Azure portal UI.

  1. Browse to the Manage tab in your Azure Data Factory or Synapse workspace and select Linked Services, then click New:

  2. Search for Oracle and select the Oracle Eloqua connector.

    Screenshot of the Oracle Eloqua connector.

  3. Configure the service details, test the connection, and create the new linked service.

    Screenshot of linked service configuration for Oracle Eloqua.

Connector configuration details

The following sections provide details about properties that are used to define Data Factory entities specific to Oracle Eloqua connector.

Linked service properties

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>"
            }
        }
    }
}

Dataset properties

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"
        }
    }
}

Copy activity properties

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.

Eloqua as 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>"
            }
        }
    }
]

Lookup activity properties

To learn details about the properties, check Lookup activity.

Related content

For a list of supported data stores in the service, see supported data stores.