Skip to Content

Turn your connections into holiday cash with our new Customer Referral Program! Learn more

✕

Temporary Storage connector for Jitterbit Integration Studio

Summary

The Temporary Storage connector establishes access to temporary storage in an agent machine.

The Temporary Storage connector provides an interface for creating a Temporary Storage connection, the foundation used for generating instances of Temporary Storage activities. These activities, once configured, interact with the stored items through the connection.

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

Connector overview

This connector is used to first configure a Temporary Storage connection. Activity types asssociated 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 Temporary Storage connection and its activities are referred to as a Temporary Storage endpoint:

Temporary Storage activities

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

  • Write: Writes data to a Temporary Storage endpoint and is intended to be used as a target in an operation or called in a script.

Note

This connector is a native Integration Studio connector, which may be referred to by Jitterbit when communicating changes made to connectors. The release schedule for native Integration Studio connectors is based on the cadence of Harmony portal web applications.

Important notes

Cloud agents have a temporary storage file size limit of 50 GB per file. Those who need to create temporary files larger than 50 GB are encouraged to use private agents.

When using temporary storage in an environment associated with an agent group that contains multiple agents, it is important to be aware that a Temporary Storage endpoint connects to the particular agent machine that is running the operation with the associated Temporary Storage Read or Write activity.

However, all linked operations in an operation chain are run on the same agent. So as long as temporary storage is written to and read from within the same operation chain, use of the Temporary Storage connector is consistent and reliable.

Caution

If using more than one agent in an agent group, and an operation that is not in the same operation chain looks for a file in temporary storage, there is no way to determine whether the same agent and temporary storage location will be used.

Temporary Storage versus Variable

Two of the most common out-of-the-box temporary storage types in Harmony are Temporary Storage endpoints and Variable endpoints. There are several considerations to take into account when choosing one over the other.

For additional details, see Temporary storage considerations.

Troubleshooting

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

  1. Ensure the Temporary 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 cloud agents or for private agents) to generate additional log files and data.

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

  5. For additional troubleshooting considerations, see Operation troubleshooting.