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.
The OData connector is accessed from the design component palette's Connections tab (see Design Component Palette).
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.
This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.
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.
If you experience issues with the OData connector, these troubleshooting steps are recommended:
Ensure the OData connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:
<logger name="org.jitterbit.connector.verbose.logging.odata" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.