Skip to end of metadata
Go to start of metadata

Introduction

A local storage connection is configured using the local storage connector to establish access with storage on a machine running a Jitterbit Harmony Private Agent. Once a connection is established, you can configure one or more local storage activities associated with that connection to use as a source or target within an operation or script.

Prerequisites

To use local storage, you must be using a Jitterbit Harmony Private Agent, and the local storage must reside on the machine where the Private Agent is installed.

CAUTION: Local storage endpoints cannot be used with Cloud Agents.

In addition, you must have the Private Agent configured to allow local storage connections. By default, Private Agents are configured to prevent use of local storage. See Enabling Local File Location to change the default setting in the Private Agent configuration file to enable local storage connections.

Creating or Editing a Local Storage Connection

From the design canvas, open the Connectivity tab of the design component palette:

To configure a new local storage connection, within the Connectors filter, click the local storage connector block:

To configure an existing local storage connection, within the Endpoints filter, double-click the local storage connection block:

This will open a configuration screen for the local storage connection, covered next.

Configuring a Local Storage Connection

Configuration of a local storage connection includes these fields:

TIP: Fields with a variable icon support using global variablesproject variables, and Jitterbit variables. Begin typing an open square bracket [ into the field or click the variable icon to display existing variables to choose from.

  • Endpoint Name: Enter a name to use to identify the local storage connection. The name must be unique for each local storage connection and must not contain forward slashes (/) or colons (:). As a specific connection and its activities are referred to as an endpoint, this name is also used to identify the local storage endpoint.
  • Path: Enter the directory location(s) that contain the files you want to read from or write to. The location(s) must be on the machine where the Private Agent is installed, and the path separators (forward slash / or backslash \) must be appropriate for the operating system of the machine where the Private Agent is installed. For example, /home/user/Documents/ on Linux or C:\projects\My Project\ on Windows. If the connection will be used for a target activity, you may enter multiple paths separated by a comma to write to multiple destinations. For example, C:\tmp, D:\tmp.

  • Test: Click this button to verify the connection. If you receive an error, make sure that the specified folder path(s) exist and that you have enabled local files as described in Enabling Local File Location.
  • Save Changes: Click this button to save and close the connection configuration.
  • Discard Changes: After making changes to a new or existing configuration, click Discard Changes to close the configuration without saving. A message will ask you to confirm that you want to discard changes.
  • Delete: After opening an existing connection configuration, click Delete to permanently delete the connection from the project and close the configuration (see Component Dependencies, Deletion, and Removal).

Next Steps

After configuring a local storage connection, you can configure one or more local storage read or write activities associated with that connection to use as a source or target within an operation or script. For more information, see these activities:

  • Read: Reads data from a local storage connection and is used as a source in an operation or called in a script.
  • Write: Writes data to a local storage connection and is used as a target in an operation or called in a script.
On This Page

Last updated:  Sep 23, 2019

  • No labels