Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »


Jitterbit's platform uses on-premise local agents and cloud-based agents as appropriate to enable connectivity to your data.

This section provides reference information and best practices concerning local agent administration to help you with troubleshooting any issues you may have.

Frequently Asked Questions


Q: What Clustering and Job Distribution capability does Jitterbit provide?

A: Yes. We do support clustering and job distribution.   

Q: How are high availability / 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 back end database can also be local or on a remote cluster.

Q: How are temporary files handled? Are they cleaned automatically? If so, how often? 

A:  Jitterbit Design Studio Client: Yes. The location of temporary files will be C:\Windows\Temp\jitterbit_client. These files will never take up much space and they are cleaned automatically. The only exception is if the application is terminated from the task manager.

Server/Local Agents: Yes. The default location of the temporary files is \tmp, or on Windows it is c:\windows\temp. There is also a folder used for debugging located …\Jitterbit Integration Server\DataInterchange\Temp. The schedule to clean temporary files is controlled by CleanupRules.xml.

Q: What logfiles can I look at? 

A:  Jitterbit logs

 “C:\Program Files (x86)\Jitterbit Integration Server\log”

This is where the Jitterbit back-end processes write logs: ProcessEngine, OperationEngine, Scheduler, CleanupService and our services implemented in Java (running in Tomcat). These logs are available in the Studio Admin console.

Apache Logs

“C:\Program Files (x86)\Jitterbit Integration Server\apache\logs”

This is the standard Apache Httpd log. It shows when somebody accessed Jitterbit from the client (login, log polling or whatever). It is also where to look if Jitterbit Apache doesn't start up or something crashed inside of our apache modules.


Transformation logs

“C:\Program Files (x86)\Jitterbit Integration Server\DataInterchange\Temp\LOG”

This is logs from the operation (WriteToOperationLog or warnings from function calls (such as DbExecute failing). They are written to the operation log when the operation finishes. If an operation crashes before that you can find any logs that were written from the operation here.


Tomcat logs

“C:\Program Files (x86)\Jitterbit Integration Server\tomcat\logs”

Logs from Tomcat. Useful for diagnosing problems with Tomcat start-up.


Postgres log

“C:\Program Files (x86)\PostgreSQL\9.0\data\pg_log”

Log directory for PostgreSQL.


Debug logs are written to

“C:\Program Files (x86)\Jitterbit Integration Server\DataInterchange\Temp\Debug”

This is the default location

-         (can be modified in jitterbit.conf [TransformationEngine]/WriteLogDir)

Q: What mechanisms are available for monitoring execution and sending alerts if there are problems?

A: Email, Web Management Console, database, etc.

Q: Are Version Control and Rollbacks available?

A: Any Jitterbit Integration can be rolled back to a previous version with a few simple clicks of the mouse.


Pages in this Category

  • No labels