EDI for Cloud Connector¶
The Jitterbit Harmony EDI for Cloud Connector establishes access to eiCloud.
The EDI for Cloud connector provides an interface for creating an EDI for Cloud connection, the foundation used for generating instances of EDI for Cloud activities. These activities, once configured, interact with eiCloud through the connection.
The EDI for Cloud connector is accessed from the design component palette's Connections tab (see Design Component Palette).
Though deprecated, the EDI for Cloud connector remains available and supported in projects where it is already being used. For new projects, the EDI for Cloud v2 connector, which connects to Harmony EDI, is recommended.
This connector is used to first configure an EDI for Cloud 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 connection and its activities are referred to as an EDI for Cloud endpoint:
Get Document V2: Retrieves all documents (from a specified partner) from eiCloud and is intended to be used as a source in an operation.
Get Document: Retrieves all documents (from a specified partner) from eiCloud and is intended to be used as a source in an operation.
Set Status: Updates the status of a document in eiCloud and is intended to be used as a target in an operation.
Send Document: Sends documents to eiCloud and is intended to be used as a target in an operation.
Get Status: Retrieves the status of documents from eiCloud and is intended to be used as a source 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 EDI for Cloud 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 connector uses a custom Jitterbit API. Contact Jitterbit Support for information on the schema fields.
If you experience issues with the EDI for Cloud connector, these troubleshooting steps are recommended:
Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).
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.verbose.logging.edi" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.