Versions Compared

Key

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

Image Removed

Overview

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut malesuada ultrices purus, vel dapibus metus efficitur et. Donec felis elit, dapibus et aliquam eget, finibus a libero. Nunc condimentum nibh ac dui fringilla, et euismod nisl sagittis. Proin scelerisque facilisis ex et commodo. Curabitur interdum tincidunt bibendum. Nulla tincidunt, diam nec tempus blandit, arcu nisi convallis mauris, non facilisis lorem dolor ac eros. Fusce et ornare lorem, in varius orci.

Proin eleifend porttitor libero. Cras at quam mi. Interdum et malesuada fames ac ante ipsum primis in faucibus. Quisque eget leo tellus. Integer ultricies sem sit amet massa consectetur, vel blandit lorem varius. Donec at mauris lacus.

Morbi molestie lectus non sem aliquet, vel tristique erat feugiat. Nam sollicitudin leo a leo aliquet posuere. Cras sagittis odio quis neque blandit ornare. Curabitur pellentesque tellus urna, quis maximus tellus ullamcorper ut. Maecenas non leo ac orci faucibus dignissim.

Frequently Asked Questions

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

Children Display

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:

Info
NOTE: Private Agents were formerly known as Local Agents.
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

Last updated: 

Lastmodifieddate