When you run an integration, connectivity to your data is enabled through the agent or agents you have configured. Agents (even if only one) are grouped into an Agent Group. You choose the Agent Group you want to use from within the Management Console, as described on Agents > Agent Groups.
There are two types of Jitterbit Harmony Agent Groups: Cloud and Private.
A Jitterbit Cloud Agent Group consists of a set of 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. The most common use case is a cloud-to-cloud integration.
For details, see Cloud Agent Group.
You can also provision and manage your own Private Agent(s) and Agent Groups,. These can use your own servers, be within a corporate firewall, or be located on virtual private clouds. This option allows you to choose where your integration runtime environment operates and control which network your data travels and resides in. Private Agents allow you to use local files as a source or target, add custom plugins, or use ODBC drivers. These are options unavailable with Cloud Agents.
|NOTE: Private Agents were formerly known as Local Agents.|
See these pages under Private Agents for information:
Administration and Troubleshooting
Using a Private Agent provides the opportunity for additional configurations that are not available with the Cloud Agent Groups. For example, you can control the agent configuration, use local files as a source or target, and define your own Jitterbit variables. This section includes configuration and troubleshooting documents for Private Agent administrators, security certificates, proxy configuration, and debug logging.
Q: Does Jitterbit Harmony provide clustering and job distribution capability?
A: Yes. By using Agent Groups, Harmony supports clustering and job distribution.
Q: How is high availability or redundancy achieved?
A: Having multiple agents clustered in an Agent Group provides high availability with active/active. There are several options with the current version of Jitterbit. The backend database can also be local or on a remote cluster. See Agent Groups High Availability and Load Balancing for additional information.
Q: How are temporary files handled? Are they cleaned up automatically? If so, how often?
A: Temporary files are handled for Design Studio and Private Agents and are cleaned up automatically from the locations listed below. With Cloud Studio, any temporary files are managed through your browser.
C:\Windows\Temp\jitterbit. These files do not take up much space and are removed automatically, unless the application is terminated using the Windows Task Manager.
/tmpand on Windows is
C:\Windows\Temp. The schedule to clean temporary files is controlled by the file
Additional log file locations are detailed in Jitterbit Log File Locations.
Q: What mechanisms are available for monitoring execution and sending alerts if there are problems?
A: Email, Management Console, database, and file entries are available. You can also set up Agent Down notifications through the Management Console to notify specified recipients when your agent is down for an amount of time that you specify. See the section on Notifications.
Q: Are version control and rollbacks available?