skip to main content
Using DataDirect Hybrid Data Pipeline : Creating a Data Source definition : Oracle Eloqua parameters
  

Try Now

Oracle Eloqua parameters

You define the information that Hybrid Data Pipeline needs to connect to the data store in a data source. These default connection values are used each time you or your application connects to a particular data store. In addition to user credentials, the data store may provide other options you can use to tune performance.
The following tables describe parameters available on the General tab of a Oracle® Eloqua Data Source dialog.
*General tab
*OData tab
Note: Hybrid Data Pipeline provides read-only access to the Eloqua data store account.
Note: The OpenAccess Server component is required for the Eloqua data source to perform correctly. Refer to the Installation Guide for detailed information on how to install the OpenAccess Server component with the Hybrid Data Pipeline Server.

General tab

Click the thumbnail to view the screen. Required fields are marked with an asterisk.
General tab of the Eloqua data source setup dialogGeneral tab of the Eloqua data source setup dialog
Table 50. General tab connection parameters for Eloqua
Field
Description
Data Source Name
A unique name for this Data Source definition. Names can contain alphanumeric characters and underscores only, they cannot contain any special characters.
Description
A description of this set of connection parameters.
User Id, Password
The login credentials for your Eloqua data store account.
Note: By default, the password is encrypted.
By default, the characters in the Password field you type are not shown. If you want the password to be displayed in clear text, click the eye Watchful eye password button button. Click the button again to conceal the password.
In addition to the user ID and password, the company identifier must be set in Custom Properties.
You can set Custom Properties, which are a required set of values that provide the information required to create a connection to Eloqua. Click the + next to Set Custom Properties to display these fields. When the Set Custom Properties button is expanded in the dialog, you may need to scroll to see all of the options.
Table 51. Eloqua General tab custom properties
Custom property
Required
Default value
Valid value
Description
Activity Bulk Page Size
No
2000
2 to 50000
The number of records to be fetched from Activity_XXX tables in a single request when using the bulk interface.
Bulk Page Size
No
500
2 to 50000
The number of records to be fetched from Eloqua in a single request when using the bulk interface. 1 2
Bulk Timeout
No
18000
3600 to 120960
The timeout duration for bulk transfer in seconds.
Oracle Eloqua automatically clears out the bulk transfer area after this timeout, so if the query is large and the data takes more than this time to run, the query could be aborted midstream. This property only has an effect if the bulk interface is enabled.
Bulk Top Threshold
No
1000
An integer greater than 0
For a Select query that qualifies for the bulk operations and the TOP n clause is used:
If the specified value is less than 1000, the standard mechanism would be used to process the query.
If the specified value is greater than 1000, bulk operations would be used to process the query.
Check Box As Text
No
0
0 or 1
Specifies whether the checkbox values of the user-defined columns should be returned as a string or as a boolean.
If set to 0, the checkbox value is returned as a boolean, which is described as BIT in the schema. Any values that cannot be matched to the current 'checkedValue' or 'uncheckedValue' are returned as NULL.
If set to 1, the stored literal value of the checkbox is returned as a string, which is described as WVARCHAR in the schema.
Company
Yes
The company identifier that Eloqua issues after registration. For example, if your company name is My Company LLC, Eloqua might issue the company identifier as mycompany.
Note: If you do not know this value, ask the person who registered for the Eloqua account.
Enable Bulk Load
No
1
0 or 1
Enables or disables the bulk support.
If set to 1, the bulk support is enabled. If set to 0, the bulk support is disabled.
Fail On Incomplete​ Data
No
0
0 or 1
Specifies how Hybrid Data Pipeline processes a query when Eloqua returns no data for some columns.
For these columns, which together form incomplete data, the connectivity service can either return NULL values or throw an exception.
If failOnIncompleteData=0, the connectivity service returns NULL values for such columns. Otherwise, if failOnIncompleteData=1, if possible, the connectivity service tries to retrieve the complete data using the bulk interface.
While using the bulk interface, if the number of columns exceeds 100 and the interface is therefore unable to satisfy the requirements of the query, the connectivity service throws an exception.
Note: It is preferable that you enable bulk support (bulkversion), as this allows more options for retrieving the data.
Keyword Conflict Suffix
No
empty string
A string of up to five characters that the connectivity service appends to an object or a field name that conflicts with an SQL keyword.
Page Size
No
500
2 to 1000
The number of records to be fetched from Eloqua in a single request when using non-bulk interfaces. Typically, Hybrid Data Pipeline may make multiple requests for a query result.34
Web Service Timeout
No
180
0 to 100000
Timeout for Eloqua web service calls. If set to 0, the Hybrid Data Pipeline connectivity service does not time out a Web Service call.
Web Service Retry Count
No
1
0 to 10
Specifies the number of times to retry the Eloqua Web service after an initial unsuccessful attempt. A positive integer sets the number of retries.
If set to 0, no retry attempts are made.
If set to 1 or higher, Hybrid Data Pipeline retries the Oracle Eloqua web service the specified number of times. Unless your logs show a high number of retries, values higher than 1 are unlikely to provide significant value.

1 Generally, higher page sizes return results more quickly. However, Oracle Eloqua imposes a 32 MB limit on response package size. If queries return large records, too many records within a single page will exceed that limit, causing the query to fail.

2 All of the objects returned within a page must be materialized as the page is retrieved, so sufficient Java heap space is necessary with large page sizes containing many small columns.

3 Generally, higher page sizes return results more quickly. However, Oracle Eloqua imposes a 32 MB limit on response package size. If queries return large records, too many records within a single page will exceed that limit, causing the query to fail.

4 All of the objects returned within a page must be materialized as the page is retrieved, so sufficient Java heap space is necessary with large page sizes containing many small columns.

OData tab

The following table describes the controls on the OData tab. For information on using the Configure Schema editor, see Enabling OData and working with Data Source groups. For information on formulating OData requests, see Formulating queries .
Click the thumbnail to view the screen. Required fields are marked with an asterisk.
OData tabOData tab
Table 52. OData tab connection parameters for Oracle Eloqua
Field
Description
OData Access URI
Specifies the base URI for the OData feed to access your data source, for example, https://hybridpipe.operations.com/api/odata/<DataSourceName>. You can copy the URI and paste it into your application's OData configuration.
The URI contains the case-insensitive name of the data source to connect to, and the query that you want to execute. This URI is the OData Service Root URI for the OData feed. The Service Document for the data source is returned by issuing a GET request to the data source's service root.
The OData Service Document returns the names of the entities exposed by the Data Source OData service. To get details such as the properties of the entities exposed, the data types for those properties and the relationships between entities, the Service Metadata Document can be fetched by adding /$metadata to the service root URI.
Schema Map
Enables OData support. If a schema map is not defined, the OData API cannot be used to access the data store using this Data Source definition. Use the Configure Schema editor to select the tables to expose through OData.
See Using the Configure Schema editor for more information.
Data Source Caching
Specifies whether the connection to the backend data source is cached in a session associated with the data source. Caching the back end connection improves performance when multiple OData queries are submitted to the same data source because the connection does not need to be created on every query.
Caching of the back end connection can get in the way when trying to configure a data source for OData. If a change is made to any of the Hybrid Data Pipeline data source connection parameters, those changes will not be seen because the connection was established using the old data source definition, and was cached. The session that caches the backend connection is discarded if there is no activity to the data source for approximately 5 minutes.
When you configure a data source for OData, it is recommended that the OData session caching be disabled. Once you are satisfied with the OData configuration for the data source, enable the parameter to get the performance improvement provided by caching the connection to the backend data source.
Valid Values:
When set to 1, session caching is enabled. This provides better performance for production.
When set to 0, session caching is disabled. Use this value when you are configuring the data source.
Default: 1
Page Size
Determines the number of entities returned on each page for paging controlled on the server side. On the client side, requests can use the $top and $skip parameters to control paging. In most cases, server side paging works well for large data sets. Client side pagination works best with a smaller data sets where it is not as expensive to fetch subsequent pages.
Valid Values: 0 | n
where n is an integer from 1 to 10000.
When set to 0, the server default of 2000 is used.
Default: 0
Refresh Result
Controls what happens when you fetch the first page of a cached result when using Client Side Paging. Skip must be omitted or set to 0. You can use the cached copy of that first page, or you can re-execute the query to get a new result, discarding the previously cached result. Re-executing the query is useful when the data being fetched may change between two requests for the first page. Using the cached result is useful if you are paging back and forth through results that are not expected to change.
Valid Values:
When set to 0, the OData service caches the first page of results.
When set to 1, the OData service re-executes the query.
Default: 1
Inline Count Mode
Specifies how the connectivity service satisfies requests that include the $inlinecount parameter when it is set to allpages. These requests require the connectivity service to include the total number of entities that are defined by the OData query request. The count must be included in the first page in server-driven paging and must be included in every page when using client-driven paging.
The optimal setting depends on the data store and the size of results. The OData service can run a separate query using the count(*) aggregate to get the count, before running the query used to generate the entities. In very large results, this approach can often lead to the first page being returned faster. Alternatively, the OData service can fetch the entire result before returning the first page. This approach works well for small results and for data stores that cannot optimize the count(*) aggregate; however, it may have a longer initial response time for the first page if the result is large.
Valid Values:
When set to 1, the connectivity service runs a separate count(*) aggregate query to get the count of entities before executing the query to return results. In very large results, this approach can often lead to the first page being returned faster.
When set to 2, the connectivity service fetches all entities before returning the first page. For small results, this approach is always faster. However, the initial response time for the first page may be longer if the result is large.
Default: 1
Top Mode
Indicates how requests typically use $top and $skip for client side pagination, allowing the service to better anticipate how to process queries.
Valid Values:
Set to 0 when the application generally uses $top to limit the size of the result and rarely attempts to get additional entities by combining $top and $skip.
Set to 1 when the application uses $top as part of client-driven paging and generally combines $top and $skip to page through the result.
Default: 0
OData Read Only
Controls whether write operations can be performed on the OData service. Write operations generate a 405 Method Not Allowed response if this option is enabled.
Existing OData-enabled data sources are read only (write operations are disabled). To enable write operations for an existing OData enabled data source, clear the OData Read Only option on the OData tab. Then, on the Data Sources tab, regenerate the OData model for the data source by clicking on the OData model icon Synch completed successfully.
Valid Values:
true | false
When the check box is selected (set to true), OData access is restricted to read-only mode.
When the check box is not selected (set to false), write operations can be performed on the OData service.
Default: false
See the steps for:
Creating a Data Source definition