Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Multiexcerpt include
MultiExcerptNamelocal-agents-banner
PageWithExcerptAgent

Private Agents

Overview

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.

You choose which Agent Group you want to use from within the Management Console, as described on Agents > Agent Groups.

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 include
    MultiExcerptName32-bit-Private Agents
    PageWithExcerptInstalling a Jitterbit Harmony Linux Agent
  • Recommendations
    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:
Info
NOTE: Private Agents were formerly known as Local Agents.

Time Zone

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.

Panel
borderColor#FF7C4C
titleColor#FFFFFF
titleBGColor#FF7C4C
titlePages in This Topic

Children Display

Panel
borderColor#8C9CB4
titleColor#FFFFFF
titleBGColor#8C9CB4
titleSearch in This Topic
Page Tree Search
Panel
borderColor#00B886
titleColor#FFFFFF
titleBGColor#00B886
titleRelated Topics

HideElements
metastrue
titletrue