Skip to end of metadata
Go to start of metadata

Introduction

Temporary storage is a built-in location, either as a target or source type, that can be used as a temporary repository of files. A temporary storage location is referenced by a path which points to a folder in a temporary directory on the Private Agent or Cloud Agent. By default, a directory under the operating system's temporary folder will be used.

Any appropriate file type can be used as storage. Commonly used are text (.txt), CSV (.csv), XML (.xml), and JSON (.json).

A temporary storage location is referred to as either a temporary storage target or source, depending on how it was created.

Default Location for Temporary Storage 

For Private Agents, this default location can be specified in the Private Agent configuration file jitterbit.conf by a setting in the [OperationEngine] section:

    TemporaryStorageRootDirectory=<absolute-path-to-existing-directory>

Substitute for <absolute-path-to-existing-directory>. For example:

    TemporaryStorageRootDirectory=/tmp/tmpstore

If a file has been written to temporary storage using a Temporary Storage target with a particular path, the same file can be retrieved by a Temporary Storage source using the same path. However, if multiple agents or operations are used, the agent could change and the file no longer be available.

Temporary Storage is typically located:

  • Windows Agents: C:\Windows\Temp\jitterbit\TemporaryStorage
  • Linux Agents: /tmp/jitterbit/TemporaryStorage

See Editing the Configuration File - jitterbit.conf for details.

Private Agents

For Private Agents, when using temporary storage be aware that:

  • Temporary Storage is written to the operating system's default temp directory (or the directory specified in Agent configuration) on the Agent that is performing the work. In the case of a single Private Agent, then it is that Agent's server host's default temp directory. If the Agent Group is running more than one Private Agent, then it is the temp directory on the server host for the particular Agent that is doing the work. 
  • A temporary storage location needs to be used very soon after it is created in order for additional processing to take place on the same Private Agent where the temporary storage is located.
  • Temporary files should only be read by the operation chain that writes them. If multiple Private Agents are assigned to an Agent Group, operations will run on any one of the agents in the group, so temporary files cannot be written by one operation chain and then read by a different chain unless the chains are linked. In a clustered agent environment (Private or Cloud Agents), as long as the operations using the temporary storage are linked (chained) together, then all the temp file reads and writes will happen on the same server host. See Persisting Data for Later Processing Using Temporary Storage for examples and details.
  • By default, temporary storage on a Private Agent is deleted after 24 hours by the Jitterbit file cleanup service.This can be changed for the Jitterbit cleanup service in the configuration file jitterbit.conf in the [FileCleanup] section by the setting FrequencyInHours.

Cloud Agents

For Cloud Agents, when using temporary storage, be aware of these restrictions:

  • Cloud Agents that are version 10.10 or higher 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 an operation writes to a temporary file, by default it is written to disk storage of the individual server within the cloud agent group that is assigned the work. 
  • A temporary storage location needs to be used very soon after it is created in order for additional processing to take place on the same cloud agent where the temporary storage is located.
  • Temporary files should only be read by the operation chain that writes them. Since multiple cloud agents are assigned to a cloud agent group, operations will run on any one of several agents in the group, so temporary files cannot be written by one operation chain and then read by a different chain unless the chains are linked. In a clustered agent environment (Private or Cloud Agents), as long as the operations using the temporary storage are linked (chained) together, then all the temp file reads and writes will happen on the same server host. See Persisting Data for Later Processing Using Temporary Storage for examples and details.
  • Unlike Private Agents, the Jitterbit clean-up service runs continuously on Cloud Agents and may delete temporary storage immediately after the operation chain finishes processing.
On This Page

Related Topics

Last updated:  Nov 25, 2019


  • No labels