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 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.
• Private: You can also provision and manage your own Private Agent(s) and Agent Groups, such as 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, an option 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 and information are relevant to this topic:

• System Requirements
  Review the System Requirements for Private Agents to ensure you meet prerequisites and requirements for the operating system, PostgreSQL database, and hardware.
• 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:

• • Linux: Installing a Jitterbit Harmony Linux Agent

  • Windows: Installing a Jitterbit Harmony Windows Agent
  • Docker: Installing a Jitterbit Harmony Docker Agent

• 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.

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 Jitterbit Design Studio and Private Agents and are cleaned up automatically.

• Jitterbit 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.
• Jitterbit Private Agents: The default location of temporary files on Linux is /tmp and on Windows is c:\windows\temp. The schedule to clean temporary files is controlled by the file CleanupRules.xml.

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 the Jitterbit Design Studio can be rolled back to a previous version following directions in Restoring from Cloud Backup.