Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Eloqua Bulk API Connector

Eloqua Bulk API Connector

Troubleshooting Synchronization task and mapping task

Troubleshooting
Synchronization
task and
mapping task

When you run an Eloqua Bulk API
synchronization
task or
mapping
task, the Secure Agent does not convert the
$LastRunTime
variable based on the UTC time zone you specify in the
Time Zone Offset
field in the connection properties.
To solve this issue, you must add the
filterWithGivenUTCTimeZone
property and set the value as true in the
pmrdtm.cfg
and
tomcat.cfg
files.
To set the value of the
filterWithGivenUTCTimeZone
property, perform the following steps:
  1. In
    Administrator
    , select
    Runtime Environments
    .
    The
    Runtime Environments
    page appears.
  2. Select the Secure Agent for which you want to set the
    filterWithGivenUTCTimeZone
    property from the list of available Secure Agents.
  3. In the upper-right corner, click
    Edit
    .
  4. Select
    System Configuration Details
    in the
    Custom Configuration Details
    section.
  5. Select the
    Service
    as
    Data Integration Server
    and
    Type
    as
    DTM
    .
  6. Add
    filterWithGivenUTCTimeZone
    in the
    Name
    field and set the
    Value
    as true.
  7. Click
    +
    icon to add another custom configuration property.
  8. Select the
    Service
    as
    Data Integration Server
    and
    Type
    as
    Tomcat
    .
  9. Add
    filterWithGivenUTCTimeZone
    in the
    Name
    field and set the
    Value
    as true.
    The following image shows the
    Custom Configuration Details
    section:
  10. Restart the Secure Agent.
  11. In the Eloqua Bulk API connection, set the
    Time Zone Offset
    property to Eloqua supported time zone.
  12. Click
    Save
    to save the connection.
When you set the
filterWithGivenUTCTimeZone
property to true and run a task, the Secure Agent considers the UTC time zone you specify in the
Time Zone Offset
field regardless of whether you use a normal filter or filter with
$LastRuntime
variable.
When you set the
filterWithGivenUTCTimeZone
property to false and use normal filter in a
synchronization
task, the Secure Agent does not consider the UTC time zone you specify in the
Time Zone Offset
field. The Secure Agent considers the UTC time zone only if you use a filter with
$LastRuntime
variable.
When you set the
filterWithGivenUTCTimeZone
property to false and run a
mapping
task, the Secure Agent does not consider the UTC time zone you specify in the
Time Zone Offset
field regardless of whether you use a normal filter or filter with
$LastRuntime
variable.

0 COMMENTS

We’d like to hear from you!