This page covers system requirements and instructions on downloading, installing, configuring, restarting, upgrading, rolling back, and uninstalling the Harmony Private Agent on a Windows system. Prior to installation, we recommend reviewing Agent Groups High Availability and Load Balancing and Private Agents Best Practices Tech Talk.
The Windows version of the Jitterbit Harmony Private Agent requires a 64-bit OS and is supported for these versions:
The Windows version of the Jitterbit Harmony Private Agent requires:
The Jitterbit Harmony Agent package is bundled with a 64-bit version of the Java 8 Runtime Environment (JRE) and does not require a separate Java runtime. Jitterbit automatically installs the required Java Runtime Environment 8.x specifically for Jitterbit to use so that it does not conflict with other Java installations that may already be installed.
These instructions on downloading a Windows Private Agent assume you have already created an Agent Group and Private Agent(s) for your organization within the Management Console. Refer to Agents > Agent Groups and Agents > Agents for more information.
Installing more than one agent in an Agent Group automatically allows for high availability. Installing multiple agents in an Agent Group also automatically allows for load balancing. See Agent Groups High Availability and Load Balancing for additional information. Before installing, check that all software requirements and notices have been met.
On each agent within the Agent Group:
At the Login Credentials prompt, enter your Jitterbit Harmony credentials (the email address and password you use to log on to https://login.jitterbit.com).
|CAUTION: If your organization and account use single sign-on (SSO), your normal SSO credentials will not work. You must use Harmony credentials to install Private Agent(s). See Install Private Agent with Harmony Credentials in Setting Up SSO in Jitterbit for more information.|
Follow the prompts to select your organization, agent, etc. The available options are those you have already configured from the Management Console.
|NOTE: You must be either an Administrator in the organization or have Agent Install permissions. See Organizations and the section on Managing Roles and Permissions for more information.|
At the Select Install Mode prompt, choose the mode depending on whether you are installing PostgreSQL or have an existing installation of PostgreSQL that you would like to use:
Quick Install (Recommended): Installs all components needed to run the Jitterbit Agent including a PostgreSQL agent database and driver. Use this option if you have never installed PostgreSQL or the Jitterbit Agent on this computer before, or if you have properly uninstalled all components following the instructions in Uninstall Agent.
|NOTE: When you are prompted to set up your PostgreSQL password, note that the password must conform to your system's password policies regarding length and complexity.|
Advanced: Installs the Jitterbit Agent and configures the Jitterbit Agent database to use an existing installation of PostgreSQL. You will need to provide your PostgreSQL credentials. You may wish to use this option if you want to manage passwords separately within each application.
After installation, the agent should start automatically. You can check the status of the agent in the Management Console (Menu > Agents), which should be "Running."
|NOTE: It can take more than a minute for the Jitterbit Harmony Agent to start up and register with Jitterbit Harmony.|
|WARNING: If you experience errors related to PostgreSQL, see Troubleshoot PostgreSQL Errors. If you experience an Error 1722 message, see Troubleshoot Error 1722. If you are still experiencing any problems during installation, please contact support.|
Restarting agent services is required whenever you have made changes to your agent configuration. Restarting the agent can also be a good troubleshooting step if you are experiencing issues, which may be resolved upon restarting.
Though the agent can be stopped and then restarted directly from the machine where the Private Agent is installed, it is best if it is first stopped from the Management Console using the "Drain Stop" command, and then restarted using the commands on the Private Agent machine itself.
The "Drain Stop" command will wait for a period of time to complete existing operations and refuse to accept new ones. Long-running operations may be canceled instead of completing.
NOTE: When an agent drain stop is initiated, the agent will now wait 180 seconds for any APIs to finish running before the drain stop is completed. For Private Agents, the wait time can be configured within the
Once stopped, the agent can only be restarted manually from the Private Agent machine directly.
StartServices.batto restart the service.
Once the Private Agent is started successfully, the status of the agent in the Jitterbit Harmony Management Console (Menu > Agents) will be "Running." You can also use Windows Services to check that the Jitterbit Services are all up and running:
If—after restarting the agent—you see that not all Jitterbit services have restarted, you should try stopping and restarting the Private Agent. If a second attempt does not resolve the situation, you should contact support.
WARNING: 64-bit Windows Private Agents
NOTE: If you are upgrading an existing 32-bit version agent to a higher 32-bit version agent, you do not need to uninstall the existing agent before upgrading. The same applies to 64-bit versions; an upgrade of a 64-bit agent does not need to be uninstalled as long as it is upgraded to another 64-bit version.
Upgrading the Private Agent on Windows can be done using similar instructions as for Install Agent. Follow the prompts to upgrade your Private Agent installation. You do not need to uninstall an existing agent prior to upgrading.
A Private Agent takes a very short time to upgrade—on the order of three minutes—depending on the server. If having any outage is a concern, you can use high availability (two or more agents) and have no downtime. If your current subscription does not have additional agents available for this, contact your Customer Success Manager (CSM) for assistance.
|WARNING: If you experience an error related to PostgreSQL, see Troubleshoot PostgreSQL Errors. If you experience an Error 1722 message, see Troubleshoot Error 1722. If you are still experiencing any problems during the upgrade, please contact support.|
It is not expected to need to revert to a previous version of a Private Agent. However, should it be required, these are the steps:
Before uninstalling, it is recommended to copy the config files and security certificates for your current installation in case you want to reinstall with the same configuration in the future. These are typically located at:
C:\Program Files (x86)\Jitterbit Agent\jitterbit.conf C:\Program Files (x86)\Jitterbit Agent\apache\conf\httpd.conf C:\Program Files (x86)\Jitterbit Agent\JdbcDrivers.conf
C:\Program Files (x86)\Jitterbit Agent\apache\conf\extra\ C:\Program Files (x86)\Jitterbit Agent\apache\conf\ssl.crt\ C:\Program Files (x86)\Jitterbit Agent\apache\conf\ssl.key\
|CAUTION: To be able to use your backup files in a future installation, you must stop services while you move the files over, then restart services once completed (see Restart Agent).|
To uninstall a Private Agent, these steps are recommended to remove both the Private Agent and the PostgreSQL installation:
Delete the Jitterbit PostgreSQL user. The management panel is accessible from the Control Panel under User Accounts > Edit local users and groups. (This also can be accessed using the
lusrmgr.msc commands.) Open the Users folder and delete the jitterbitpostgres user:
Delete the Windows user folder for the jitterbitpostgres user from the Users folder of the file system:
Delete the PostgreSQL folder from the Program Files folder of the file system:
Delete the PostgreSQL folder from the Program Files (x86) folder of the file system:
There are multiple reasons the Private Agent installation could fail with this error message:
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. ...
The most common reason for this failure is a conflict with an existing version of Microsoft Visual C++ Redistributable.
Private Agents require Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019 to be installed before installing a Private Agent. Microsoft now includes the same redistributable files for Visual Studio C++ 2015, 2017, and 2019. Install the appropriate version to match your Windows version:
NOTE: If installing a Private Agent that is prior to version 10.3, and Visual Studio libraries such as the earlier versions of Visual Studio C++ Redistributable for Visual Studio 2017 or higher are already installed, the installation will fail. A workaround is to download and install the appropriate files available at Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019 and then install the Private Agent.
As of Jitterbit Harmony version 10.3, this has been fixed. Installation on a machine that already has a version of Visual C++ Redistributable for Visual Studio higher than 2015 is now successful. If you are still experiencing issues, please contact support.
In certain cases, after uninstalling a Windows Private Agent and then attempting to reinstall the agent, users may receive an error related to the PostgreSQL database.
This error has been known to occur on systems where the PostgreSQL installation associated with the Private Agent has not been completely removed.
To resolve the error, users should follow the steps above in Uninstall Agent to completely remove the Jitterbit PostgreSQL user account. The instructions for manually removing all PostgreSQL files are in steps 2 through 5.
Once this is done, you should be able to complete a new agent installation. If you are still experiencing issues, please contact support.