EDI for Cloud v2 Connector¶
The Jitterbit Harmony EDI for Cloud v2 Connector establishes access to Harmony EDI.
The EDI for Cloud v2 connector provides an interface for creating an EDI for Cloud v2 connection, the foundation used for generating instances of EDI for Cloud v2 activities. These activities, once configured, interact with Harmony EDI through the connection.
The EDI for Cloud v2 connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector is used to first configure an EDI for Cloud v2 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 EDI for Cloud v2 connection and its activities are referred to as an EDI for Cloud v2 endpoint:
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 EDI for Cloud v2 connector requires access to Harmony EDI, which is currently released only to selected organizations. To gain access prior to general availability, contact your account executive.
The EDI for Cloud v2 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 EDI for Cloud v2 connector uses a custom Jitterbit API.
If you experience issues with the EDI for Cloud v2 connector, these troubleshooting steps are recommended:
Ensure the EDI for Cloud v2 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.
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.ediv2" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.