Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Cloud Agent Group


A Jitterbit Cloud Agent Group consists of a set of Jitterbit Harmony Agents maintained and managed by Jitterbit. This option allows you to run all of your integrations in the cloud with a scalable, multi-tenant, fault-tolerant clustered Agent Group.

Two Cloud Agent Groups are available:

  • Production Cloud Agent Group: This group is available with a version of the Jitterbit Harmony Agent that is fully tested and ready for production.

  • Sandbox Cloud Agent Group: This group is always the next version of the Jitterbit Harmony Agent, to which the Production Cloud Agent Group will next be upgraded. (Typically, it is the version of the Private Agent included in the latest Harmony Platform release at time of the Sandbox Cloud Agent Group update.)

The Sandbox Cloud Agent Group is available for testing your projects with a new version of Jitterbit Harmony to ensure that you are ready for the next upgrade of the Production Cloud Agent Group. It is not intended as a test environment for your projects prior to “go-live”—that's what a Harmony environment is for—as projects in the Sandbox Cloud Agent, if they use a new feature introduced in that specific version, cannot be moved to the Production Agent Group until the Production Cloud Agent is upgraded to the same version.

Configuration of Cloud Agent Groups

Cloud Agents are configured using the default settings for a Jitterbit Private Agent with these differences:

  • Windows OS authentication for databases is not allowed

  • Key-based SSH login is not allowed

  • ODBC driver access is not allowed

  • Debug logging is not allowed
  • For security, logs from Agents in a Cloud Agent Group are removed as soon as they are no longer required for an operation to execute properly. Though a download link may show in the Management Console, you will receive an error message if you attempt to download using that link.
  • All temp files are cleaned up very quickly; you cannot rely that they are present after an operation runs

  • By default, local files as sources or targets is disabled and they cannot be used on Cloud Agents

  • A project is limited to 8 running operations per agent at any time

  • The maximum time an operation can run (MaxOperationRuntimeSeconds) is set at 21600 seconds (6 hours)

  • A limited group of Jitterbit plugins are available for use on Cloud Agents

If this configuration does not meet your project requirements, you should use a Private Agent.

Upgrade Schedule

The approximate schedule for upgrading of the Jitterbit Cloud Agent Groups is:

  • A new version of the Jitterbit Private Agent is released approximately every 30 days

  • Approximately once each quarter, the Sandbox Cloud Agent Group is updated to the latest available Jitterbit Harmony Agent

  • Approximately 60 days after the Sandbox Cloud Agent Group is updated to a new version, the Production Cloud Agent Group is updated to that same version, allowing time for testing in the Sandbox of Production projects against the upcoming new version

  • For both Cloud Agent Groups, we will apply updates for known critical defects as we deem necessary. Though we will give advance notice as possible, there can be circumstances where a fix is of such urgency that advance notice is not possible. In all cases, notices will be posted on our status site at

On This Page

Last updated:  Feb 13, 2019

  • No labels