Cloud Datastore (Beta) connection

Introduction

A Cloud Datastore (Beta) connection, created using the Cloud Datastore (Beta) connector, establishes access to Cloud Datastore (Beta). Once a connection is configured, you can create instances of Cloud Datastore (Beta) activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Create or edit a Cloud Datastore (Beta) connection

A new Cloud Datastore (Beta) connection is created using the Cloud Datastore (Beta) connector from one of these locations:

• The design component palette's Project endpoints and connectors tab (see Design component palette).
• The Global Endpoints page (see Create a global endpoint in Global Endpoints).

An existing Cloud Datastore (Beta) connection can be edited from these locations:

• The design component palette's Project endpoints and connectors tab (see Design component palette).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).
• The Global Endpoints page (see Edit a global endpoint in Global Endpoints).

Configure a Cloud Datastore (Beta) connection

Each user interface element of the Cloud Datastore (Beta) connection configuration screen is described below.

• Connection name: Enter a name to use to identify the connection. The name must be unique for each Cloud Datastore (Beta) connection and must not contain forward slashes / or colons :. This name is also used to identify the Cloud Datastore (Beta) endpoint, which refers to both a specific connection and its activities.

• Access token: Enter an access token, generated in the Management Console Access tokens page. The token you provide here should be associated with the same environment and organization that the project resides in.

  Note

  You must request access to the Jitterbit Cloud Datastore (Beta) feature to generate an access token. To request access or provide feedback on this beta feature, contact the Jitterbit Product Team.

• Optional settings: Click to expand additional optional settings:

  • Use Proxy Settings (Private Agent Only): When using a private agent, this setting can be selected to use private agent proxy settings.

• Test: Click to verify the connection using the configuration. When the connection is tested, the latest version of the connector is downloaded by the agent(s) in the agent group associated with the current environment. This connector supports suspending the download of the latest connector version by using the Disable Auto Connector Update organization policy.

• Save Changes: Click to save and close the connection configuration.

• Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

• Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component dependencies, deletion, and removal). A message asks you to confirm that you want to delete the connection.

Next steps

After a Cloud Datastore (Beta) connection has been created, you place an activity type on the design canvas to create activity instances to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions menus in Connector basics.

These activity types are available:

• Get Metrics: Retrieves usage data for a status storage or key storage in Cloud Datastore and is intended to be used as a source in an operation.

• Create Storage: Creates a new status storage or key storage in Cloud Datastore and is intended to be used as a target in an operation.

• Delete Storage: Deletes a status storage or key storage from Cloud Datastore and is intended to be used as a target in an operation.

• Query Items: Reads data from a status storage or key storage within Cloud Datastore and is intended to be used as a source in an operation.

• Insert Items: Inserts new data into a status storage or key storage in Cloud Datastore and is intended to be used as a target in an operation.

• Update Items: Updates existing data in a status storage or key storage within Cloud Datastore and is intended to be used as a target in an operation.

• Delete Items: Deletes data from a status storage or key storage in Cloud Datastore and is intended to be used as a target in an operation.