Skip to Content

Cloud Datastore (Beta) connector

Summary

The Cloud Datastore (Beta) connector establishes access to Jitterbit Cloud Datastore (Beta).

The Cloud Datastore (Beta) connector provides an interface for creating a Cloud Datastore (Beta) connection, the foundation used for generating instances of Cloud Datastore (Beta) activities. These activities, once configured, interact with Cloud Datastore through the connection.

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

Note

For beta access and to provide feedback, contact the Jitterbit Product Team.

Connector overview

This connector is used to first configure a Cloud Datastore (Beta) 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 Cloud Datastore (Beta) connection and its activities are referred to as a Cloud Datastore (Beta) endpoint:

Cloud Datastore (Beta) 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 Cloud Datastore (Beta) 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.

For a successful connection, you must have an access token for your project's environment, generated in the Management Console Access Tokens page. Its Scope must be set to Cloud Datastore.

Note

If using a private agent that is behind a firewall within your network, Jitterbit Cloud Datastore (Beta) must be allowlisted.

Troubleshooting

If you experience issues with the Cloud Datastore (Beta) 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 by adding this logger configuration entry to your private agent's logback.xml file:

    <logger name="org.jitterbit.connector.clouddatastore" level="DEBUG"/>
    

    For more information on connector verbose logging, see Verbose logging for connectors using Jitterbit private agents.

  5. If using private agents, you can check the agent logs for more information.

  6. For additional troubleshooting considerations, see Operation troubleshooting.