By default, using local files is disabled for Jitterbit Private Agents. This includes using a Cloud Studio local storage endpoint or a Design Studio local file source or target, as well as using trigger files or success/error folders that are configured on other endpoints or sources/targets.
You can enable local file locations if you need to work with a specific local directory or local files, or use the trigger file or success/error folder options.
Local file locations can be enabled only for Private Agents and cannot be enabled on Jitterbit Cloud Agents.
As local file locations are disabled by default on Private Agents, if you have not yet configured your Private Agents to enable local file location, then upon testing the connection to a Cloud Studio local storage endpoint or Design Studio local file source or target, this error message will be displayed:
Using local files as a source/target, trigger file, or success/error folders is disabled by default.
Set EnableLocalFileLocation=true in the [Settings] section of jitterbit.conf and restart the Jitterbit Apache service to enable it.
Local file location is disabled on the Cloud Agent Group, so the same error message will appear if you are using Cloud Agents. It is not possible to enable local file location for Cloud Agents.
To enable local files, you need to edit the Private Agent's configuration file and then restart all Jitterbit services.
There are two ways to change the configuration file: remotely or manually. Remotely is simpler (especially with multiple Agents in an Agent Group), but manually may be preferable in certain scenarios.
For the Keys row labelled
EnableLocalFileLocation, set the Value to
These abbreviated steps show how to enable local file storage by manually editing the configuration file. For further instructions, see Editing the Configuration File - jitterbit.conf.
On each machine where the Private Agent is installed, navigate to the Agent's configuration file. This will be located in its installation directory, usually in one of these locations:
C:\Program Files (x86)\Jitterbit Agent\jitterbit.conf
C:\Program Files (x86)\Jitterbit Integration Server\jitterbit.conf
For example, on a Windows OS system:
jitterbit.conffile in a text editor.
[Settings] section of the file, find the entry
Change the line shown above in yellow to read:
All Jitterbit services must be restarted in order for the config change to take place. On each machine where the Private Agent is installed, first stop the services, then restart them, using the appropriate procedure for the operating system:
|OS||Procedure||Menu Items or Commands|
Run the applications
|"Stop Jitterbit Services"|
"Start Jitterbit Services"
Use the commands
$ sudo jitterbit stop $ sudo jitterbit start
To check that the Private Agent has restarted successfully, go to the Management Console and view the Agent. The status of the Private Agent should be "Running." The new configuration will now be in effect. For example:
These steps show how to confirm that local file locations are enabled. Even if you do not intend to use a local storage endpoint or local file source/target, you can use this procedure to confirm that a trigger file or a success/error folder will now be accessible on a certain Agent or Agent Group.
Confirm that you can now use local file locations in Cloud Studio or Design Studio:
Design Studio: Create a new local file source or target, specifying a local folder path and files. After your specific parameters are listed, click Test Connection. A message should be displayed indicating the connection was successful and display the local files.
|NOTE: If you are using a Cloud Agent (or a different Private Agent), you will receive the same error message as before, either because enabling local files is not possible using a Cloud Agent or because you have the wrong Agent (Group).|