You are viewing an old version of this page. View the current version.
When you run an integration, connectivity to your data is enabled through the agent(s) you have configured. There are two types of Agent Groups: Cloud and Local.
- Cloud: The 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 cloud-to-cloud integration.
- Local: You can also provision and manage your own Local Agent(s) and Agent Groups within a corporate firewall or 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.
These pages and information are relevant to this topic:
- System Requirements
Review the System Requirements for Local Agents to ensure you meet prerequisites and requirements for the operating system, PostgreSQL database, and hardware.
- Installation Instructions
After reviewing these system requirements and recommendations, see the installation instructions for your operating system:
Administration and Troubleshooting
Using a Local Agent provides the opportunity for additional configurations that are not available with the Cloud Agent Group. You have more control over the agent configuration, use of local files, the option to define your own Jitterbit variables, and more. The remaining pages in this section include configuration and troubleshooting documents for Local Agent administrators, including resources on certificates, proxy configuration, and debug logging.
Frequently Asked Questions
Q: Does Jitterbit provide clustering and job distribution capability?
A: Yes. Jitterbit 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 Local Agents / Integration Server and are cleaned up automatically.
- Design Studio: The location of temporary files on Windows is
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.
- Server/Local Agents: The default location of temporary files on Linux is
/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 the amount of time you specify. Learn more under Notifications.
Q: Are version control and rollbacks available?
A: Integrations created in Design Studio can be rolled back to a previous version following directions in Restoring from Cloud Backup.
Last updated: Jul 18, 2018
- No labels