When you run an integration, connectivity to your data is enabled through the agent(s) you have configured. There are two types of Jitterbit Agent Groups: Cloud and Private.
- Cloud: The Jitterbit Cloud Agent Group consists of a set of Jitterbit Agents that are 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.
- Private: You can also provision and manage your own Agents as Private Agent(s) and Private Agent Groups, such as on your own servers, within a corporate firewall, or 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 sources or targets, add custom plugins, or use ODBC drivers. These are options unavailable with Cloud Agents.
These pages describe Private Agents, their system requirements, installation, and administration:
- System Requirements
Review the System Requirements for Private Agents to ensure you meet prerequisites and requirements for the operating system, PostgreSQL database, and hardware.
- MultiExcerpt named '32-bit-Private Agents' was not found
Prior to installing a Private Agent, see Agent Groups High Availability and Load Balancing for recommendations that allow for high availability and load balancing. In addition, see Private Agents Best Practices Tech Talk.
- Installation Instructions
After reviewing these system requirements and recommendations, see the installation instructions for your operating system:
- Administration and Troubleshooting
Using a Private Agent provides the opportunity for additional configurations that are not available with the Cloud Agent Group. For example, you can control the agent configuration, use local files as a source or target, and define your own Jitterbit variables. The remaining pages in this section describe configuration and troubleshooting documents for Private Agent administrators, security certificates, proxy configuration, and debug logging.
If you are administering groups of Private Agents, see these specific pages:
The time zone used for schedules is that of the agent running the operation, unless the Override Schedule Agent Time Zone setting is enabled in your organization's policies. Private Agent time zones are determined by the time zone of the operating system of the Private Agent. It is highly recommended for all agents in a Private Agent Group to be running on the same time zone, or the times at which a configured schedule initiates the operation may be unpredictable depending on the specific agent being used.