Skip to Content

EDI for Cloud v2 connector for Jitterbit Integration Studio

Summary

The EDI for Cloud v2 connector establishes access to Jitterbit 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 Jitterbit EDI through the connection.

The EDI for Cloud v2 connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Important

This connector requires a subscription to Jitterbit EDI. Contact your Customer Success Manager (CSM) for more information.

Connector overview

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:

EDI for Cloud v2 activity types

Note

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 Jitterbit 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.

Troubleshooting

If you experience issues with the EDI for Cloud v2 connector, these troubleshooting steps are recommended:

  1. 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).

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. 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"/>
    
  5. If using private agents, you can check the agent logs for more information.

  6. For additional troubleshooting considerations, see Operation troubleshooting.