The Jitterbit Harmony OData Connector establishes access to OData endpoints.
The OData connector provides an interface for creating an OData connection, the foundation used for generating instances of OData activities. These activities, once configured, interact with an OData endpoint through the connection.
This connector is used to first configure an OData connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
Together, a specific OData connection and its activities are referred to as an OData endpoint:
Query: Queries object data from an OData endpoint and is intended to be used as a source in an operation.
Update: Updates object data in an OData endpoint and is intended to be used as a target in an operation.
Insert: Inserts object data into an OData endpoint and is intended to be used as a target in an operation.
Delete: Deletes object data from an OData endpoint and is intended to be used as a target in an operation.
Verbose logging can be enabled for this connector when it is used with a Private Agent. See Verbose Logging for Connectors for details.
Invoke verbose logging for this connector using this configuration entry:
<logger name="org.jitterbit.connector.verbose.logging.odata" level="DEBUG"/>
Prerequisites and Supported API Versions¶
The OData connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
The OData connector uses the Apache Olingo OData 4.0 Java library. Refer to the library documentation for additional information on how the OData protocol is supported.