Skip to Content

Local Storage Connector

Summary

The Local Storage connector for Jitterbit Harmony Cloud Studio provides an interface for entering user-provided input such as the Private Agent directory path to create a Local Storage connection. That connection provides the foundation to configure associated Local Storage connector activities that interact with the connection. Together, a specific Local Storage connection and its activities are referred to as a Local Storage endpoint.

Caution

Local Storage endpoints cannot be used with Cloud Agents.

Connector Overview

This connector is used to first configure a Local Storage connection, establishing access to storage on the Private Agent machine, and then used to configure one or more Local Storage activities associated with that connection as a source or target within an operation or script:

  • Read: Reads data from a Local Storage endpoint and is intended to be used as a source in an operation or called in a script.
  • Write: Writes data to a Local Storage endpoint and is intended to be used as a target in an operation or called in a script.

Accessing the Connector

The Local Storage connector is accessed from the design component palette's Connections tab (see Design Component Palette).

local storage activities

Enabling Local Storage

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

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 Enable Local File Location to change the default setting in the Private Agent configuration file to enable Local Storage connections.

Troubleshooting

If you experience issues with the Local Storage connector, these troubleshooting steps are recommended:

  1. Ensure the Local Storage connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

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

  3. Enable operation debug logging for Private Agents to generate additional log files and data.

  4. Check the agent logs for more information.